->''"And you will stand there, wondering how we did it..."''\\
'''Linkara:''' Ooh! I know how! ''[Points up toward the ceiling]''\\
'''Text:''' ''Inhumanly Awful Writing''
-->-- '''Linkara''', ''WebVideo/AtopTheFourthWall'', "ComicBook/AmazonsAttack Issues 5 and 6"

This is an index of tropes that are often indicative of plain bad writing.

When done unintentionally, these tropes are usually bad signs. When done intentionally, they're often signs of {{parody}}, comedy, or just the writer being ironic or [[TrueArtIsIncomprehensible stylized]]. Hopefully.

Please note that TropesAreTools, and many highly acclaimed works have used these tropes successfully.

See also:
* DiscreditedTrope - A trope which is no longer taken seriously by audiences.
* PetPeeveTrope - A trope that is disliked by certain audiences.
* UnexpectedReactionsToThisIndex - A trope causes a reaction... but not the one you want.
* ThePlotDemandedThisIndex - Something happens to push the story because logic can't.
* IndExMachina - No explanation, no foreshadowing, no problem, apparently.
* EightDeadlyWords - When the reader utters "I don't care what happens to these people," due to a lack of empathy.
* ScrappyIndex - Tropes in a particular work that have a {{hatedom}} such as TheScrappy, MarySue, and CharacterDerailment.
* CreatorsApathy - When the creators admit they weren't even making an effort.

* NecessaryWeasel - An unrealistic trope which the audience expects to be there.
* StylisticSuck - Making a work/art style etc. bad on purpose.
* WhoWritesThisCrap - When a work's writing is criticized {{in-universe}}.
* IntendedAudienceReaction - An attempt to intentionally evoke a reaction from the audience.

Not to be mistaken for WritersSuck, which has more to do with {{Butt Monkey}}s than bad writing.


[[folder:Crazy Characterization]]
* AesopAmnesia: The more times a character is taught a lesson without learning it, the lower the viewer's opinion of him/her and you.
* AngstWhatAngst: Make your characters react realistically to setbacks or tragic events. Too little {{angst}} makes them unrealistic and [[TheSociopath callous]].
* CharacterDerailment: Characters can grow, but don't suddenly mutate them into something else.
* CharacterShilling: Having characters suddenly talk up another character for no real reason doesn't make a whole lot of sense.
* {{Chickification}}: Stripping the action from an ActionGirl does not work, and will piss off some of the audience.
* ConflictBall: Don't have a character cause conflict just because the plot says so.
* CreatorsPet: Treating a certain character with tons of love [[TheScrappy when they really don't deserve it]] is never a good idea.
* DarknessInducedAudienceApathy: Making the story excessively bleak and giving absolutely no hope will only tire out the audience until they lose interest in the story.
* DerailingLoveInterests: Breaking up a promising relationship just to get the official couple together is not going to sit well with the viewers who care more about the characters than the concept.
* DesignatedHero: Having your hero KickTheDog and still expecting your audience to accept him as an IdealHero because you say he is doesn't usually work, and makes your protagonist unlikable.
* DesignatedLoveInterest: If you say that two characters are in love, don't make them hate or be apathetic to each other, actually go out of your way to make them love each other. Otherwise it just feels contrived.
* DesignatedVillain: Having your villain come off as [[HarmlessVillain harmless]] and still expecting your audience to see him as a monster just because you say he is doesn't usually work, and makes your antagonist petty.
* DieForOurShip: Attacking a rival of your [[OneTruePairing pairing of choice]] doesn't necessarily make that character a bad person and makes you look petty.
* DistressBall: Don't have a character get kidnapped for no good reason.
* DracoInLeatherPants: Have an acceptable reason for making a truly evil character suddenly be nice. "He or she is hot!" will not do.
* DullSurprise: Have your characters emote during events that would make a real person do so.
* FailureHero: While having the hero lose from time to time adds some realism to the hero and drama to the story, if they lose every single fight or mission, not only will it destroy any and all tension, but the reader will feel bad for relating with the hero.
* FauxActionGirl: If you ''say'' that a girl is strong, then ''make'' her strong. If said ActionGirl comes off as too weak, [[TheScrappy the audience will begin to hate her.]]
* HeroBall: Heroes are expected to make bad decisions every now and then, but when they directly aid the villains, it becomes this trope.
* IdiotBall: When the character is suddenly acting like an idiot.
* InformedWrongness: If a character is actually in the wrong, prove it.
* InvincibleHero: A hero who can't lose is boring.
* InvincibleVillain: A villain who can't lose is even ''more'' boring.
* JerkSue: Having a character be a complete {{Jerkass}} who [[KarmaHoudini gets away with it]] just because the author designates them as such and says you should support them does not make for a strong character, and is more likely going to turn out be a case of CreatorsPet, and often TheScrappy. Also, it tends to look like a half-assed effort when the author just throws in some secondary throw-away detail in an attempt to make you feel sorry for the character and expect you to not get upset when they behave like a jerk for no other reason than they feel like it at the time.
* MarySue: A flawless, invincible character who never loses at anything makes for a boring story. MarySueTropes and CommonMarySueTraits contain lots of information on different types of Sue.
* MoralDissonance: Don't have the hero behave contrary to their usual morality and be completely oblivious to it.
* MostWritersAreAdults: Unless it's suppose to be [[TroublingUnchildlikeBehavior unsettling]], don't write children with {{un|cannyValley}}settlingly adult personalities projected onto them.
* MostWritersAreMale: Don't write women from ignorance, stereotypes, and/or in unsympathetic ways (either in the form of misogyny or [[{{Fanservice}} over-sexualization]]).
* NeverASelfMadeWoman: When creating a female character, completely having their roles and personality being defined by their superior males is just going to make women look inferior in the face of a men.
* NewPowersAsThePlotDemands: Don't give a character a new ability out of thin air depending on the situation.
* OutOfCharacter: Moments when the character does something that he wouldn't normally do without any justification.
* PositiveDiscrimination: Don't make the female or minority characters better than the others simply because they are minorities, and don't make the male characters incompetent simply because they are males.
* ProtagonistCenteredMorality: A character's moral standing should be based on their actions as a whole, ''not'' solely on their actions toward the main character. A sure sign of a MarySue or a DesignatedHero.
* RaceTropes: Tread carefully with these. Having a minority character act like a walking stereotype screams lazy writing and will upset people.
* RomanticizedAbuse: Make sure that your romance is actually romantic. Don't portray abuse, either physical or emotional, as sexy or sweet.
* RonTheDeathEater: Have an acceptable reason for making a truly good character suddenly be mean. "I hate him or her!" will not do.
* SatelliteLoveInterest: Define your characters by something ''other'' than being the lover or crush for TheProtagonist, or the archetypal "perfect" boyfriend/girlfriend.
* StrangledByTheRedString: People going directly from being strangers to being genuinely in love is not very realistic or satisfying to watch. If you're going to make two characters fall in love with each other, try to take it slow.
* StrongAsTheyNeedToBe: Don't have characters suddenly gain or lose power without any explanation.
* StupidSacrifice: Characters shouldn't give up their lives for nothing (if the character is not a MartyrWithoutACause).
* VillainBall: See HeroBall, only swap "heroes" and "villains".
* VillainDecay: Don't have your antagonist lose their power and competence without a good reason.
* VillainSue: A flawless, invincible ''villain'' who never loses at anything makes for a boring story just as much as an ordinary MarySue.
* {{Wangst}}: Make your characters react realistically to setbacks or tragic events. Too much {{angst}} makes them unrealistic and annoying.
* WhatAnIdiot: Characters should not make unrealistically bad decisions to drive the plot.
* {{Wimpification}}: Stripping the action, common sense, and characterization from a male character to add {{Wangst}} and gender stereotypes applied to females is a good way to piss off many of the audience, including but not limited to feminists and actual gay or bisexual men.

See also ContrivedStupidityTropes.

[[folder:Mishandled Morals]]
All of the below only count if they aren't being PlayedForLaughs or {{spoof|Aesop}}ed:

* {{Anvilicious}}: Morals should be shoved subtly, not thrown at your face. Unless it's [[SomeAnvilsNeedToBeDropped an important or underrated moral]].
* BrokenAesop: The lesson you teach should match what the story shows.
* CaptainObviousAesop: Don't try teaching your audience something that they already know.
* CluelessAesop: Don't try to put a moral in a story where it doesn't belong.
* LostAesop: If you're going to present some "truth", make sure you do it.

[[folder:Poor Plotting]]
Bad Plotting can make for a bad story:
* AbortedArc: Plot points should go somewhere eventually.
* ArcFatigue: The longer a storyline goes while making no progress, the less the audience will care about it.
* AssPull: Don't introduce major changes and/or important elements at critical moments in the plot without some foreshadowing or justification.
* CliffhangerCopout: This is what happens when a {{Cliffhanger}}'s resolution comes in the form of tweaking the continuity between back-to-back installments (usually creating {{Plot Hole}}s), a refusal/failure to follow through with delivering a big [[TheReveal Reveal]] after setting an audience up for one, or outright [[AbortedArc aborting a story arc]].
* TheChrisCarterEffect: It's a good idea to actually finish things. Sooner or later, the audience will get bored with you screwing around and not getting to the point.
* CoitusEnsues: Don't write a sex scene if there's no reason for the involved characters to ''have'' sex.
* ContinuitySnarl: Plotlines can snag if you aren't careful.
* DeusAngstMachina: Too much misfortune makes too little WillingSuspensionOfDisbelief.
* DeusExMachina: Do not save your characters with an AssPull.
* DiabolusExMachina: A victory for the bad guys pulled out of thin air might be amusing for [[BlackComedy shock value]], but it doesn't make for great storytelling.
* EndingFatigue: The viewer should probably not be yelling "END ALREADY!"
* EsotericHappyEnding: If you want to write an uplifting ending, make sure that the audience can agree with you that you wrote one.
* FridgeLogic: Though much more forgivable than a PlotHole, this can be bad if it doesn't have enough FridgeHorror or FridgeBrilliance to go along with it. If you have a complicated universe, don't gloss over the minor details.
* GratuitousRape: Rape is an incredibly grave subject matter. Don't shoehorn in a rape scene just for shock value, or have so much it loses impact.
* IdiotPlot: Unless the characters are supposed to be idiots, the plot should not be forced to move forward solely by people making stupid decisions.
* JustEatGilligan: If there's an obvious solution to the problem(s) that drives the story, you would think the characters would go for it rather than ignoring it.
* KudzuPlot: It's fine to have a dozen different story threads at once, but you have to be able to tie them together. If they go off into infinity without ever being tied, who's going to care about any of them? The pieces of your JigsawPuzzlePlot have to ''fit''.
* LostInMediasRes: If there's not enough exposition when starting out InMediasRes, the viewers will feel completely lost and lose interest in the story.
* OnlyTheAuthorCanSaveThemNow: Do not put your characters in a situation where only a DeusExMachina can save them.
* PlotHole: Don't think the audience won't see when you forget to cover something.
* RelationshipRevolvingDoor: See YoYoPlotPoint
* RomanticPlotTumor: Unless the plot is romance, don't let it take over.
* SeriesContinuityError: When you set something in stone, you can't chisel it out without leaving marks.
* ShockingSwerve: Don't have a TwistEnding just to have a TwistEnding.
* SlowPacedBeginning: Just as the viewer shouldn't demand the work to end already as with EndingFatigue, they shouldn't be forced to sit through hours of exposition or padding to get to the actual plot.
* StrangerBehindTheMask: If you're going to have a [[TheReveal Reveal]], make sure that the revealed character has been met before.
* TheStationsOfTheCanon: When important events in a DivergenceFic are treated more as checkmarks than plot points.
* TheyWastedAPerfectlyGoodPlot: If the premise is interesting, DO something interesting with it.
* TrappedByMountainLions: If someone's in a story, they should be part of the plot, too.
* UnfortunateImplications: Be careful with the way you portray certain characters and the situations you put them through; viewers could get the wrong idea.
* VoodooShark: When patching over a PlotHole creates a different, possibly more troublesome, problem.
* WritersCannotDoMath: If simple arithmetic in a story doesn't add up, fans will notice and be left scratching their heads.
* YoYoPlotPoint: It's okay if a few plot points repeat themselves throughout the series, but if it's the same story every other episode, your audience is bound to get bored.

[[folder:Senseless Styles]]
In amateur writing (or stuff that just simply [[ProtectionFromEditors didn't get the proper proofreading]]), bad writing is sometimes inherent in the form and presentation of the work itself:
* AndThatsTerrible: Telling the reader how evil the villain is, instead of showing it (or even doing both). [[HypocriticalHumor That's a bad thing]].
* AuthorFilibuster: The reader/viewer/player/etc is (theoretically) interested in the plot. Stopping it so that you can talk about something that's important to you will only make them less interested in what you're writing.
* BlindIdiotTranslation: When you translate the works transformed appropriately.[[labelnote:Translation]]When translating a work, translate it properly.[[/labelnote]]
* CharacterFilibuster: Putting those words in someone else's mouth doesn't help.
* ConceptsAreCheap: Using concepts and buzz words to pad out a thin script.
* CriticalResearchFailure: Unless it is meant to be [[ArtisticLicense intentional]] or InUniverse, make sure that anything treated as real world fact isn't so obviously incorrect that most of your target audience will realize you have very little knowledge about the subject you're dealing with.
* DepartmentOfRedundancyDepartment: Repeating statements is irritating. Repeating statements is asinine. Repeating statements is annoying.
* DudeNotFunny: Think carefully before joking about issues that are controversial in real life.
* EmphasizeEverything: If '''everything''' is '''emphasized''', then '''nothing''' is, and you've done '''nothing''' of '''value''' except '''annoy your audience'''.
* FeaturelessPlaneOfDisembodiedDialogue: Conversation doesn't happen in a vacuum, so label what is said by who said it.
* GratuitousEnglish: Randomly popping in meaningless English words that you ''don't know the meaning of'' is a bad idea. If you want to write in English, ''know the meaning of your English'' and make sure it's grammatically correct.
* GratuitousForeignLanguage: Don't put foreign words if you don't understand the meaning or grammar. It can make you seem illiterate to actual speakers of the language.
* GratuitousJapanese: It's generally ''not'' a good idea to use random bits of Japanese unless you're a fluent speaker, lest you come across as pandering to OccidentalOtaku. Either write in ''idiomatic'' Japanese and learn how to properly pronounce it if you need to, or just write in your native language.
* [[UsefulNotes/{{Tenses}} How Do I Used Tense]]: Unintentional shifts in tense are highly distracted and confusing.
* InformedAttribute: Saying something is so is not the same as making it so.
* LikeIsLikeAComma: Like, constantly using the word "like" in, like, every other sentence gets incredibly, like, annoying to read through.
* MeaninglessMeaningfulWords: Don't add eloquent-sounding words unless you know whether they actually go there or not.
* NoPunctuationPeriod: Run-on sentences make a story much harder to read especially when there should be pauses yet there is no possible way of defining when they would appear and can usually be avoided.
* RougeAnglesOfSatin: Jest beak oars hits spilled car wrecked lay docent main hits than write ward. [[labelnote:Translation]]Just because it's spelled correctly doesn't mean it's the right word.[[/labelnote]]
* SaidBookism: A form of PurpleProse. Using fancy substitutes for the word "said" in the fear that the dialogue doesn't speak for itself will cause people to focus less on your work and more on the words used.
* ShallowParody: Do not spoof what you're spoofing unless you know well about what you're spoofing.
* StrawmanHasAPoint: If you can't even attack [[TheWarOnStraw strawmen]] without being defeated, you may need a new profession.
* ThatMakesMeFeelAngry: Telling the reader what a character is feeling, instead of showing it.
* TotallyRadical: Don't put slang without understanding the meaning just to look "cool". Overuse of slang can make your work an UnintentionalPeriodPiece.
* TranslationTrainWreck: Bed telephones not particle via misunderstand through reverses all reeling meats inside dolphin non fluffy. [[labelnote:Translation]]Bad translations that are impossible to understand and removes any real meaning from the dialogue are not favorable.[[/labelnote]]
* UnintentionallySympathetic: Failure to create antipathy to a character in the audience will cause them to like [[HateSink characters you want them to hate.]]
* UnintentionallyUnsympathetic: Failure to create sympathy to a character in the audience will cause them to hate characters you want them to like.
* WallOfText: The formatting (or lack thereof) combined with a lot of redundant words makes the text seem impenetrable, and will make the reader lose the track after a few lines.
* TheWarOnStraw: Not a direct cause of bad writing, but a frequent component of it nevertheless.
* WantonCrueltyToTheCommonComma: Other bad grammar and usage.
* WereStillRelevantDammit: When trying to keep LongRunners up to date, throwing in recent pop culture references and fads won't help at all. Instead it just comes off as stupid, instantly dated, and possibly even the sign of a DorkAge.
* WriterOnBoard: This is a story, not a treatise.
* YouKeepUsingThatWord: As Creator/MarkTwain said: "Use the right word, not its second cousin."

See also StylisticSuck

[[folder:TV Tropes Troubles]]
ThisWiki is not exempt from this. Please consult the Administrivia/PermanentRedLinkClub for further details.

* AllBlueEntry: It is very annoying to read, and delays the reading of the article.
* BoldInflation: Don't bold tropes' names. Tropes need no emphasis, if something's very important, then it should be specified in the description instead.
* Administrivia/ComplainingAboutShowsYouDontLike: TV Tropes wants to keep the wiki as civil as possible. Having a trope, entry or an example that is nothing but bashing will simply invite both EditWar and FlameWar between its supporters and detractors.
* Administrivia/ConversationInTheMainPage: Remember, TV Tropes is a wiki, not a [[ThreadMode forum or chatroom]]. Conversations just clog up the articles and make them too long/tedious to read.
* Administrivia/ExamplesAreNotArguable: If you're not sure if what you're writing is an example or not, take it to the discussion page or [[http://tvtropes.org/pmwiki/posts.php?discussion=13543987200A54420100 this forum thread]] instead of coating your example with WeaselWords.
* Administrivia/ExamplesAreNotRecent: When writing an example, avoid using the word "recent." What's considered recent ''now'' won't be in a couple of years. It just makes more trouble for other {{troper}}s to edit out the word "recent" once it isn't recent anymore. Act as if every work that was ever published came out several years ago.
* FanMyopia: Don't act like everyone knows all the details about whatever work you enjoy.
* Administrivia/JustAFaceAndACaption: Images that don't convey a trope [[FanMyopia unless one is familiar with their origin]] are not helpful depictions.
* JustifyingEdit: [[TropesAreTools Tropes Are Not Bad]]. Avoid responding to examples with a "to be fair" addendum. If a trope is actually {{justified|trope}}, the justification should be [[Administrivia/RepairDontRespond added into the example itself]]. Consider phrasing things in a more neutral sense like "explained in-universe by" instead of "justified".
* Administrivia/LinkingToAnArticleWithinTheArticle: Having a link on a page that leads to the exact same page is completely pointless and [[DepartmentOfRedundancyDepartment redundant]]. It's even worse if the link is {{pothole}}d or if a redirect is used, as this can trick the reader into wasting their time clicking on it and thinking they're going somewhere when they really aren't.
* NotASubversion: [[YouKeepUsingThatWord Misuse]] of the word "{{subverted|Trope}}." A common sign of this is use of phrases such as "partially subverted" or "somewhat subverted."
* Administrivia/PermanentRedLinkClub: The worst articles in this wiki go here.
* Administrivia/SelfFulfillingSpoiler: Be sure your spoiler tag ''hides'' what you are trying to spoil. If a reader can easily guess what is behind the spoiler tag, it becomes useless, doubly so if they aren't invested into a work at all.
* Administrivia/{{Sinkhole}}: When making a {{Pothole}}, make sure that the article being linked bears relevance to the {{Pothole}}d text.
* SquarePegRoundTrope: Make sure that the example that you want to add fully fits the trope. If it's "not really an example", then it's not really an example, and it shouldn't be added.
* ThisTroper: Writing about oneself in a Main wiki article. The goal is to make Main articles sound like a single person is editing the article, [[WikiSchizophrenia not multiple people]]. Besides, personal comments just clog up the articles.
* ThreadMode: Don't clog up a trope entry just because you don't understand why it's there.
* Administrivia/TypeLabelsAreNotExamples: Any relevant context needed to explain the example should be given in the example itself. Don't simply label it "type X" and force the reader to look up what it means just so they can understand what the example means.
* Administrivia/TropeNamerSyndrome: Make sure your proposed trope name makes sense on its own, instead of just being a reference.
* WalkthroughMode: We are not Website/GameFAQs.
* Administrivia/WeblinksAreNotExamples: If one has a trope example, one should write it down, in adequate detail, where it is relevant, not rely on a URL link to some other page to explain what it is.
* WordCruft: When writing an example, just stick to writing the example and try to avoid saying useless things that don't need to be said.
* Administrivia/ZeroContextExample: If you're going to leave an example, please explain what it is. [[FanMyopia Not everyone will understand what you've written about]].

[[folder:Gruesome Game Design]]
* AllegedlyFreeGame: If you advertise your game to be free, then don't force players to spend real life money to progress through your "free" game lest the players will consider your game to be a greedy attempts for more money.
* AnnoyingVideoGameHelper: Helpful {{N|onPlayerCharacter}}PCs should be actually helpful. If your ExpositionFairy is interrupting the game to [[CaptainObvious tell you something you already know]] or if your allies [[ArtificialStupidity are dumber than bricks]], the game gets frustrating quickly.
* ArtificialStupidity: Make sure your AI actually works.
* DisappointingLastLevel: Be sure players still have interest in finishing your game by the time they reach the final level.
* FakeBalance: Make sure to have proper balance in your game, otherwise players will [[TierInducedScrappy hate something/someone for non-story reasons]].
* GameBreakingBug: Don't let a glitch cripple the playability of your game.
* GuideDangIt: While having obscure secrets and bonuses that reward players who like to TryEverything is fine, completing your game's main content shouldn't be near-impossible for players to figure out without a guide.
* MoonLogicPuzzle: Make sure the puzzles in your games are logical, or at least logical to an earthling.
* ObviousBeta: Clean your game up and make it look presentable before releasing it.
* PixelHunt: If the player must search for something, don't make it too hard to find.
* PowerUpLetdown: Make sure that the improvements that your character receives are actually useful and not detrimental to the players.
* TutorialFailure: [[VideoGameTutorial In-game guides]] that provide incomplete, flawed, or outright erroneous instructions are going to leave many players frustrated.
* UnwinnableByMistake: Thoroughly test your game before releasing it to ensure that it is reasonably difficult but not impossible to beat.

See also ErrorIndex

[[folder:Miserable Music/Lousy Lyrics]]
* GratuitousRape: Deserves a second special mention here. If you are going to address the topic of rape in your lyrics, address it in some meaningful way and be ready for the consequences.
* LastNoteHilarity: Unless you are a comedy/parody act, you don't want the audience to ''laugh'' at your music.
* MisogynySong and MisandrySong: The UnfortunateImplications of playing either straight are a very big and controversial issue, and unless you wish to be involved in a controversy, avoiding creating these songs is probably a very good idea.
* PainfulRhyme: ''Don't force rhymes.'' If something doesn't rhyme, you can make a non-rhyming song that can be just as good as a rhyming one, or try to find rhyming words that both describe what you want and rhyme.
* SomethingSomethingLeonardBernstein: Depending on your genre, this might actually be workable. But in anything requiring clear vocals, this is ''automatically bad,'' and even in more permissive genres overly relying on it is often a bad idea.
* VocalRangeExceeded: Don't write things your singer ''can't sing,'' and if you're the singer as well as the writer, be realistic about your range and capabilities.[[note]]A common mistake here is writing for the highest ranges such as pure soprano and alto. Especially among male singers, the capability to reach these ranges is astonishingly rare (male singers will usually fall somewhere between tenor and baritone on average), and even most female singers fall short of being capable of ''pure'' soprano or alto voice, and a singer who is incapable of such and tries anyway will likely sound falsetto and possibly damage their vocal cords. If in doubt, write for the lower ranges and modify higher.[[/note]]

* CanonDefilement: People who are reading your FanFic probably enjoy the show for what it ''is''. Not for what you would like it to be. Seeing beloved characters mangled into whatever form you desire is probably going to cut down on your audience, unless you're Creator/NeilGaiman[[note]]And even he shows a great deal of respect for Canon while mangling it[[/note]].
* DanBrowned: If you haven't done the research, don't claim you have.
* DeliberateFlawRetcon: When critics and audiences point out a significant flaw in your work, people are unlikely to believe you if you [[IMeantToDoThat claim it was intentional]].
* {{Demonization}}: Some of your potential audience may actually see where this position is coming from, if not actually agree. [[DontShootTheMessage You'll turn them off by your exaggerated portrayal.]] It also makes it seem like the position you hold isn't nearly as solid as you think, since it can only stand up to strawmen.
* FetishRetardant: If you write something intended to turn on your audience, make sure it doesn't suffer from {{Squick}}, UnfortunateImplications or {{Narm}}.
* {{Glurge}}: If you're trying to write a heartwarming story, make sure people won't find [[UnfortunateImplications questionable things]] underneath your message before you do.
%% HandWave is not a case of Bad Writing; it can be used to paper over a detail that would take too long to explain properly. For example, most of the audience doesn't really care how the FTL drive works, so explaining it takes up time that could be used for actual plot. %%
* IKEAErotica: Sex should only be as boring as it is to the participants.
* ISuckAtSummaries: If you can't be bothered to summarise your fic properly, then why should people be bothered to read it?
* {{Marysuetopia}}: MarySue in society form is still MarySue.
* {{Narm}} (when caused by the writing): Make your dramatic/climactic scenes convincing, not cheesy. Don't go over-the-top. Make it realistic. Think about how a person in RealLife would behave in the situation.
* NightmareRetardant (when caused by the writing): If something is supposed to be scary, either [[NothingIsScarier don't show it]] or actually make it scary.
* ParodyRetcon: If you're setting out to make a parody or a satire, announce that from the outset. People are unlikely to believe you if you only claim that your work was intended as such after the fact.
* RelationshipWritingFumble: Viewers can latch onto romantic {{subtext}}, even in places where it's not supposed to be.
* ShippingBedDeath: When not handled properly, a pairing becoming canon can kill the audience's interest in the story and/or characters.
* ViewersAreMorons: Treat your audience as if they know the basics, because we do. [[FanDumb Most of the time, anyway.]]
* WriterCopOut: Have the strength to follow through, or don't take the shot at all.