History YMMV / FireEmblem

22nd Jan '17 11:19:41 AM LucaEarlgrey
Is there an issue? Send a Message


** For the newer games (''Awakening'' and beyond), playing on Casual mode instead of Classic will get you a lot of ire from a lot of players. Even if they have a sound argument for why you should play on Classic (namely in that it encourages you to value your units instead of just throwing them away in the name of victory in a game where each unit has a backstory and personality to them and the deaths of each of which are treated in a way to [[TearJerker make you feel like you just lost a loved one]]), it's still a form of telling you "don't play on this easier mode ''ever''".

to:

** For the newer games (''Awakening'' and beyond), playing on Casual or Phoenix mode instead of Classic will get you a lot of ire from a lot of players. Even if they have a sound argument for why you should play on Classic (namely in that it encourages you to value your units instead of just throwing them away in the name of victory in a game where each unit has a backstory and personality to them and the deaths of each of which are treated in a way to [[TearJerker make you feel like you just lost a loved one]]), it's still a form of telling you "don't play on this easier mode ''ever''".
22nd Jan '17 11:18:08 AM LucaEarlgrey
Is there an issue? Send a Message


** For the newer games (''Awakening'' and beyond), playing on Casual mode instead of Classic will get you a lot of ire from a lot of players. Even if they have a sound argument for why you should play on Classic (namely in that it encourages you to value your units instead of just throwing them away in the name of victory), it's still a form of telling you "don't play on this easier mode ''ever''".

to:

** For the newer games (''Awakening'' and beyond), playing on Casual mode instead of Classic will get you a lot of ire from a lot of players. Even if they have a sound argument for why you should play on Classic (namely in that it encourages you to value your units instead of just throwing them away in the name of victory), victory in a game where each unit has a backstory and personality to them and the deaths of each of which are treated in a way to [[TearJerker make you feel like you just lost a loved one]]), it's still a form of telling you "don't play on this easier mode ''ever''".
22nd Jan '17 11:17:01 AM LucaEarlgrey
Is there an issue? Send a Message


* StopHavingFunGuys: There's a very vocal portion of [[{{Speedrun}} low turncount players]] that fall into this category.

to:

* StopHavingFunGuys: StopHavingFunGuys:
**
There's a very vocal portion of [[{{Speedrun}} low turncount players]] that fall into this category.category.
** For the newer games (''Awakening'' and beyond), playing on Casual mode instead of Classic will get you a lot of ire from a lot of players. Even if they have a sound argument for why you should play on Classic (namely in that it encourages you to value your units instead of just throwing them away in the name of victory), it's still a form of telling you "don't play on this easier mode ''ever''".
19th Jan '17 1:53:26 PM bloodytears92
Is there an issue? Send a Message

Added DiffLines:

** The series as a whole is being hit with this more and more over time. Until ''Awakening'', Fire Emblem had been viewed as a niche series and a secondary IP at best. After ''Awakening'' revived the series and made it more popular than ever, the last few years have seen Fire Emblem absolutely exploding in popularity, culminating in 6 playable characters in the newest Super Smash Bros game (on par with other high profile Nintendo IP such as Mario, Zelda and Pokemon), and as of 2017, Fire Emblem got its own special Nintendo Direct where it announced ''FOUR'' games were in the works to be released by the end of 2018. Fire Emblem has become a mainline IP for Nintendo, and people in the West are either overjoyed its finally come as far as it has, or are bitter about how its success is overshadowing other IP they consider more deserving, such as Metroid, Donkey Kong, F-Zero and Star Fox.
19th Jan '17 6:47:01 AM technickal
Is there an issue? Send a Message


* HypeBacklash: ''Genealogy of the Holy War'' started to show signs of this. ''Blazing Sword'', however, averts it despite being the FE game that most people have played.

to:

* HypeBacklash: ''Genealogy of the Holy War'' and ''Blazing Sword'' have started to show signs of this. ''Blazing Sword'', however, averts it despite being the FE game that most people have played.this.
18th Jan '17 4:11:48 PM MJTrooper
Is there an issue? Send a Message


* CrackPairing: Just about every game in the franchise that has a either a lover system or a support system doesn't even need wacky fan pairings. While there are certainly plenty of those out there (such as [[ChivalrousPervert Sain]] / [[ShrinkingViolet Florina]]), some of the canon pairing possibilities are downright Crack Pairings. Some examples include [[HotBlooded Hector]] / [[ShrinkingViolet Florina]] from [[VideoGame/FireEmblemElibe the 7th game]], [[KnightInShiningArmor Kyle]] / [[InsufferableGenius Lute]] from [[VideoGame/FireEmblemTheSacredStones the 8th game]], and [[BlueBlood Astrid]] / [[JerkWithaHeartofJerk Makalov]] from the 10th game. [[VideoGame/FireEmblemAwakening The 13th game]] averts this because [[DevelopersForesight every possible pairing has a unique set of supports building up to it, and everyone seems to have a legitimate reason for falling in love with anyone else]]. (With the only exception being [[StrangledByTheRedString Chrom/Olivia]], which is [[LampshadeHanging lampshaded]] in the game itself.)

to:

* CrackPairing: CrackPairing:
**
Just about every game in the franchise that has a either a lover system or a support system doesn't even need wacky fan pairings. While there are certainly plenty of those out there (such as [[ChivalrousPervert Sain]] / [[ShrinkingViolet Florina]]), some of the canon pairing possibilities are downright Crack Pairings. Some examples include [[HotBlooded Hector]] / [[ShrinkingViolet Florina]] from [[VideoGame/FireEmblemElibe the 7th game]], [[KnightInShiningArmor Kyle]] / [[InsufferableGenius Lute]] from [[VideoGame/FireEmblemTheSacredStones the 8th game]], and [[BlueBlood Astrid]] / [[JerkWithaHeartofJerk Makalov]] from the 10th game. [[VideoGame/FireEmblemAwakening The 13th game]] averts this because [[DevelopersForesight every possible pairing has a unique set of supports building up to it, and everyone seems to have a legitimate reason for falling in love with anyone else]]. (With the only exception being [[StrangledByTheRedString Chrom/Olivia]], which is [[LampshadeHanging lampshaded]] in the game itself.))
** After the Fire Emblem Direct on January 18, 2017, some people have jokingly shipped Creator/YuriLowenthal with [[VideoGame/FireEmblemAwakening Lon'qu]] due to the narrator, who is voiced by Yuri, being quite fixated on Lon'qu.
17th Jan '17 1:25:48 PM ImperialMajestyXO
Is there an issue? Send a Message


* AlternateCharacterInterpretation: Given how many characters there are across the games, this is inevitable. Particularly obvious with shipping (especially when it comes to sexual orientation), since the games rarely define specific canon pairings, and the support system often gives one character multiple potential romances.

to:

* AlternateCharacterInterpretation: AlternativeCharacterInterpretation: Given how many characters there are across the games, this is inevitable. Particularly obvious with shipping (especially when it comes to sexual orientation), since the games rarely define specific canon pairings, and the support system often gives one character multiple potential romances.
16th Dec '16 6:47:43 PM billybobfred
Is there an issue? Send a Message


*** "Strength" (Same as above, only with strength): Favors fast units with the strength to keep all their speed. Rationale: the stronger a unit becomes, the more weight s/he could handle;
*** "No Weight" (Weapons have no weight whatsoever): Favors all fast units, especially those with issues over the two prior methods. Rationale: a properly trained warrior should never be burdened with his/her weapon.

to:

*** "Strength" (Same as above, only with strength): Favors fast units with the strength to keep all their speed. Rationale: the stronger a unit becomes, the more weight s/he they could handle;
*** "No Weight" (Weapons have no weight whatsoever): Favors all fast units, especially those with issues over the two prior methods. Rationale: a properly trained warrior should never be burdened with his/her their weapon.
3rd Dec '16 2:39:19 PM billybobfred
Is there an issue? Send a Message


* TheWoobie: Now has it's [[http://tvtropes.org/pmwiki/pmwiki.php/Woobie/FireEmblem own page]].

to:

* TheWoobie: Now has it's [[http://tvtropes.org/pmwiki/pmwiki.php/Woobie/FireEmblem [[Woobie/FireEmblem its own page]].
18th Nov '16 1:42:32 AM Monsund
Is there an issue? Send a Message


** Knights also get a fair amount of flak, though not as much as Archers. Unlike Archers, they ''do'' have a specific niche to fill as the party's tank, and tend to start with decent stats. Unfortunately, their low move severely hinders their usefulness - either the party has to move more slowly so the Knight can stay in the front and tank, or the Knight gets left behind. Their low Speed is also a problem, as most enemies later in the game will be able to double them (Ironically, this can make Knight units worse at tanking than other units as, say taking 8 hits twice deals more damage than one 12 hit). They can shine on maps where the party mostly has to stay still and defend a specific area, but there don't tend to be too many of those (and some games don't have any). Combine that with the fact that there are a number of weapons that are effective against them, that their generally low Resistance makes them vulnerable to mages, and that there tend to be many other, faster and more mobile units that can fill a frontline tanking role, and you have a class that tends to get left in the dust.

to:

** Knights also get a fair amount of flak, though not as much as Archers. Unlike Archers, they ''do'' have a specific niche to fill as the party's tank, and tend to start with decent stats. Unfortunately, their low move severely hinders their usefulness - either the party has to move more slowly so the Knight can stay in the front and tank, or the Knight gets left behind. Their low Speed is also a problem, as most enemies later in the game will be able to double them (Ironically, this can make Knight units worse at tanking than other units as, say taking 8 hits twice deals more damage than one 12 hit). They can shine on maps where the party mostly has to stay still and defend a specific area, but there don't tend to be too many of those (and some games don't have any). Combine that with the fact that there are a number of weapons that are effective against them, that their generally low Resistance makes them vulnerable to mages, and that there tend to be many other, faster and more mobile units that can fill a frontline tanking role, and you have a class that tends to get left in the dust. Both ''Fire Emblem: Radiant Dawn'', and ''Fire Emblem: Fates'' buff the class, likely in response.



* TrueArtIsAngsty: A very vocal portion of the fandom believes this, particularly about the more-tongue-in-cheek and less cynical games. ''Awakening'' is catching the brunt of this more than any other title in the franchise.
This list shows the last 10 events of 164. Show all.
http://tvtropes.org/pmwiki/article_history.php?article=YMMV.FireEmblem