![]() Author has written 2 stories for Legend of Zelda, and Horizon Forbidden West. "When you've got a good story, sleep is for the weak!" -Me Heyo! I'm just an addicted fanfiction reader and hobby writer who spends WAY too much time on this site. I also have a second account on AO3 under the name "St0ryt3113r" with the same stories cross-posted, if you prefer that format. I know both have their ups and downs. I'm currently in the middle of world-building my own original universe, so I'm not likely to put a lot up here for you to read, but if you're looking for your next big fanfic series, you can check my Favorites! I tend to be very picky about what I read, and while having all of these prerequisites filled isn't a necessity, it does become harder to read a story when one or more of them are noticed in the writing: Good summary: If the summary is well written, has few to no grammatical errors, and provides a decent enough hook to get the reader's interest, I'll consider it. This tells me the author is conscious of what they are writing and is putting in at least some effort to make the intro look good. Spelling/proper word usage is on point:WARNING! Rant ahead! WARNING! Okay, so one of the biggest things I've seen is people accidentally using words that don't belong where they are typed. The biggest offenders I've seen are "defiantly" used for "definitely", "ultraviolent" instead of "ultraviolet", and the usual misspelling of "psychic", "psychically", and its associated forms. I understand why they get messed up (believe me, I find plenty of screwups in my own writing notes), but that is no reason why you can't go over your work and check it over again or, if you aren't grammar savvy in the first place, find a beta reader to check for you. There are lots of them on this site. Language Consistency: One of the aspects of writing that adds texture and depth to a story is having characters who are bilingual or multilingual. However, it's incredibly important how you do it as not every reader will understand the little nuances that come with a different language. Take anime fanfics for example: because most anime is originally done in Japanese before being dubbed in English, a lot of stories will use the honorifics or Romanji names from the Japanese version when writing their dialogue or inner monologues. Please remember that some of us only know one version of the names and don't always know the difference between "-san", "-chan", "-kun", and the others; "-sensei" is more widely known outside of typical conversations due to the martial arts, but if you are going to use honorifics, or another language, in your writing, please keep that in mind, especially if you are writing the story in English and write the character's attacks in the original Japanese language. A few ideas I've seen would be to put the meanings for honorifics at the beginning or end of the chapter for the reader's reference, or if you are writing a full string of dialogue put the translation in brackets or parenthesis with/without italics to differentiate between the two, though this is usually done to indicate a character in the story who is speaking a different language from the rest of the characters. Or, if you're already writing the story in English, just put the attacks in their English translations. Writing dialogue: I have a saying I tell myself when I am trying to write my own stories that goes "Don't write dialogue as if you're writing. Write dialogue as if you're talking." Writers, remember than even though you're still writing your story, dialogue has a different feel and structure than the narrative portion. If it's not something that could be said in casual conversation or quickly in a high stress scenario, rework it and try again. Use ME Max from Hawaii Five-O as an example. As much as I love the character, his speech patterns are very formal and feel somewhat awkward at times due to his character's nature. High word count, few chapters: This one might not make sense at first, so I'll explain. If the story has a word count of around 50k words, and a chapter count of 45-55, that can mean to me that the author(s) either isn't commiting a lot of time and thought into describing each scene and moment of the chapter clearly (usually filled with no-caps, sentence fragments, misspellings, and random punctuation), or they write short scenes and break up the action. Chapters like these often are usually about one moment in time or they stick to a single person's POV before switching to someone else in the next chapter without changing the scene. Fanfiction writers need to be very careful of this; breaking up action scenes, especially without a dire cliffhanger at the end, risks losing your momentum and suspense and can lose the readers when your next chapter uploads. Conversely, if a fic has ~150k words, and less than 30 chapters, that tells me the author has most likely done their research or spent a lot of time building their plan for the story and that it'll most likely be an enjoyable read. However, it can also mean their chapters are very wordy and overly descriptive. Take pride in your work and be sure to review your chapters before uploading. Clear pairings: Not the biggest concern. Building the suspense is a basic part of storytelling. But when the site gives you the ability to tell your readers whom is going with whom, I like to know. Most fanfics are based off of established characters, and the readers are usually people who are familiar with them. But, again, not a huge deal. Romance isn't the biggest focus in an adventure: I am an avid shipper; I won't deny it, and most of the stories I read are because of a specific ship, but when the author gives more focus to the romance than the progress of the story and the development of the characters, it becomes annoying. For example, in Pokemon fics where they pair Ash with Serena, called Amourshipping; maybe because Kalos was based on France and Serena had an all too obvious crush on Ash, but everyone makes them all lovey-dovey at the cost of the story. They focus less on Ash and everyone training their Pokemon and travelling and more on Serena and Ash falling even deeper in love. You sickos, unless you change their ages, THEY ARE 10 YEARS OLD! That aside, if you have multiple characters in your main cast, be aware if you're spending too much time focussing on one or two characters versus the others. Unless you're into that stuff, no one wants to constantly read about how "so-and-so" is sucking face with "so-and-so" every third paragraph. Believable love connection: I know what I just said above, but I also said that I do enjoy romance when it's done correctly. And it's one of the hardest things to do. Most of the stuff we do on this site is because we think Character A should be with Character B because we think they belong together, and they either aren't together in canon or they are but we don't like how they got together. And there's nothing wrong with wanting to see them couple up, but you have to flesh it out and show it through the story and their experiences why they belong together. You can't just say "I think they should be together because I said so." That's a childish and frankly lazy argument for putting them together. You have to describe why "A" fell for "B". Did they find them charming? Funny? Cute? Cool? Did they save them from something and immediately fall for them, or was it a slow and gradual attraction? Did someone deny their feelings for their love interest's sake? Was somebody too dense to notice the feelings so the second person had to practically spell it out for them? These are just a few of the ways to describe a romantic partnership. You also should try and avoid making the two characters seem OOC as much as possible. If it's hinted that Character B likes Character A, but isn't explicitly stated, then don't have them show up years later being completely head over heels for A. While it can happen, it's not common for that to occur in real life. Story flow: This is something that you feel when you're reading; it's where the progress of the story seems to just roll like a boat on the sea. Sometimes it's calm, other times it's a little rocky, and the climax can be either a lasting storm or a devastating hurricane, where it's crazy for a while, then it hits the eye where it's still for a bit before throwing you right back into the fray. Stories that read with a smooth flow often have few to no grammar errors, are descriptive without being overly so, are spaced well so that it doesn't feel like one big paragraph, and should make you want to keep going so much that you lose track of time. Bad flows have poor spelling, choppy writing, and seem to run on forever. You can almost feel it when you're reading a story with a bad flow. It's like driving from a freshly paved road to a gravel driveway; it disrupts the flow of the story. If you have to stop and go back to look something over to make sure that you read it correctly multiple times, it might have a bad flow. A trick to see how your story flows and sounds is to put the passage in Google Translate and have it read it aloud. You can usually hear it when something isn't right. Descriptive, but not repetitive: A common pitfall of writers is to overly describe a scene. We want to make sure our readers don't miss anything, so we describe things down to the last fingernail... clipping. This can often lead to skimming, where the reader becomes accustomed to jumping over large passages of text until they find one of these because they think it means that now the action is back, but instead they just jumped over a week in the story! When it's time to edit your work, either have a friend who you know is good at it look it over, a beta who can look it over, or read it aloud. If you hear yourself repeatedly describing the same scene, consider using a synonym for one of the repeated words, or even try restructuring the sentence. Sometimes what you've written so far is less of a finished product and more of an idea or prompt you that you want to try. And always remember: Show the scene, tell the dialogue. The readers don't need to know the tree was exactly thirty-eight inches from the swimming hole the character was in; instead, show them how the willow tree branches tickled her back as she floated across the pond. Well then if you've made it this far in my profile, I commend your endurance and patience to go through my tips, tricks, and rants and I offer you this imaginary cookie! Seriously, though, I started this with the intention of putting down my methods for picking what I read, but I quickly deviated into a rant and opinion barf. Still, if any of this helps you guys become better and more conscious writers, then I look forward to your future works. "Love is patient, love is kind. It does not envy, it does not boast, it is not proud. It is not rude, it is not self-seeking, it is not easily angered, it keeps no record of wrongs. Love does not delight in evil but rejoices with the truth. It always protects, always trusts, always hopes, always perseveres. Love never fails." -1 Corinthians 13:4-8 If you believe in Jesus Christ put this in your profile and don't just ignore this, because in the Bible it says "If you deny me, I will deny you in front of my Father in the gates of Heaven!" A hero is someone who doesn't ask for change; a hero makes change. A hero doesn't broadcast by choice; a hero is a hidden hand. A hero doesn't die; a hero, once born, lives on forever in the hearts of men. A hero doesn't judge; a hero forgives. A hero doesn't chose who to save; he saves anyone, even those that can't or don't think to ask for help. -NoSignalBlueScreen [Check out their stories. They rock!] |