My SRPG Studio Project

 Hey everyone! It's been a while since I last posted. Just wanted to let everyone know that I'm currently working on creating a game of my own in SRPG Studio. I wanted to not only let you guys know that this exists, but also show a little bit about what I've made so far. So far, I've been working on the gameplay. The sprites that you see below are the default sprites of SRPG Studio. Yes, I know they're bad, and I will replace them with new ones and import better sprites when the time comes.

So here are a few mechanics that I'm implementing: 

1. Berwick Saga style Counterattacking

During battle, if the defender takes damage, they cannot counterattack. The only way to counterattack an enemy is by either 

a. Dodging the hit (while also having a weapon with the same range)

b. The swing landed, but it dealt 0 damage.

c. The defender has a skill that lets them counterattack.

Like Berwick Saga, only one character in this game has the skill that gives them a traditional Fire Emblem style enemy phase. In this game, your Armor Knight Loshnor is the only character that can do that. This should go a long way toward incentivizing Player Phase oriented gameplay. 

2. Changes to the Formula

2a. Double Attacking

In order to double attack, the formula is now this: Speed - Skill. If the attacker's Speed is 4 points higher than the Enemy's Skill, the attack double attacks that enemy. Speed only causes double attacking, but it's the Skill stat that prevents a unit from being double attacked. Let's use an example.

Here are the stats of the player's starting mage, Nathanael:

Here are the stats of an enemy Light Mage.

In a traditional Fire Emblem game, Nathanael wouldn't be able to double attack the enemy Light Mage. However...

Since Nathanael's speed was 5 points higher than the enemy Light Mage's, he can double attack. This should hopefully make the Skill stat more valuable.

2b. The Con (Bld) stat now deals damage

Here's how the formula works: [(Attacker Con - Defender Con) / 2]. Using the above example, Nathanael's Build stat is 12, while the Enemy Light Mage has a Build stat of 8. So, to use our formula:

                             12 - 8 = 4 / 2 = 2.

Nathanael gets to deal 2 extra points of damage, while the Light Mage deals 2 fewer points of damage. 

2c. Luck determines Avoid, not Speed

The Avoid Formula is (Luck x 2). The Speed stat only does one thing in this game: It determines double attacking. Skill prevents double attacking, and Luck determines whether a unit can dodge or not.

2d. Thracia 776 Style Critical Hit Formula

Skill Stat + Weapon Critical Hit Rate

Critical Avoid: Luck / 2.

You can get bonuses from skills and supports, but this is basically it. This essentially means that it'll be easier to increase critical hit rates in this game. Hopefully that should make the Luck stat more valuable.

Other Fun Mechanics in this Game

a. Thracia 776 style Capturing

b. Thracia 776 style Fatigue

Just like Thracia 776, every character that participates in a round of combat, heals, and steals increases their Fatigue by a certain amount. When that fatigue becomes greater than or equal to the character's max HP, they have to sit out the next round.

One major change that this game makes is that every character has a unique rate of fatigue. For example, Nathanael has a fatigue rate of 2. That means that whenever he participates in a round of combat, his fatigue increases by 2 instead of 1. 

Will there be Stamina Drinks?

Not in Lunatic Mode. Hard Mode will only have a small handful of them. I can't decide if I just want to turn off fatigue for Normal Mode or make it so easy to get Stamina Drinks that it's not much of a thing. Hmmm....

c. FE 12 Style Lunatic Mode Bonuses

So here's something that Fire Emblem 12 did for its Lunatic Mode that I really liked:

Giving enemies an extra + 10 Accuracy made dodge tanking more difficult and helped make enemies more threatening. I took notes from that design and decided to emulate it, but with an extra twist...

I boosted the damage they'd deal by 5! This should help to make enemies more threatening.

On that note, I'm trying to take notes from Fire Emblem 12 and make enemy offenses so powerful that they should be able to 2 - 3 Hit KO the cast with relatively good accuracy.  

Other Mechanics

• No Ambush Spawns: Enemy reinforcements happen at the end of the enemy turn! You won't have to worry about any BS here.

• 2 RN system: Accurate hits will be even more accurate! With enemies having good hit rates, this system should make it more likely for them to hit the player's units. Here's a sample of some of the enemy hit rates in just the first chapter, alone:
  

Fun fact: Both of those enemies had Weapon Triangle disadvantage. Here are the Weapon Triangle Bonuses in this game:

+ 4 Damage, + 20 Hit. 

Nathanael versus an Archer Boss.

The First Three Characters of the Game

Let's take a look at the first three characters of the game that the player starts out with:

Valayan - The Main Character

Note: Valayan is not a noble, nor does he have a special lineage. He's essentially a "nobody" who rose through the ranks of the military. 

He uses Swords, Dark Magic, and can equip shields. He also starts with 7 Movement, the highest Movement a Tier 1 unit can have. Here are his skills:

I tried to get Renewal to be a percent of a unit's max HP. So far, I haven't been able to do that. As a result, Renewal's really powerful in the early game but will lose value further into the game.

Unlike Savage Blow or Poison Strike from Fates, this skill can land kills. However, he won't gain any experience from those kills.

These stat buffs activate any time he's on the map. He doesn't even need to be within a certain distance from any allies. 

Nathanael - The Game's Squishy Mage

Here's a list of his skills:

This version of Wrath is modeled after the FE 5 style of Wrath that always activated when a unit's HP was half or less. I'm hoping this should make him one of the most powerful units in the game.

So did I make him worth using?

Loshnor: The Armor Knight

I realize that Armor Knights are traditionally seen as bad units, so I've come up with a few ways to hopefully make Loshnor a good unit. 

# 1: He's the only character in the game with a traditional Fire Emblem style Enemy Phase

I already brought this up earlier, but he's the only character in the game that can counterattack an enemy even if he takes damage. Sherpa, the only character in Berwick Saga with a traditional Enemy Phase, was considered a top tier character and this was a big reason why. I'm hoping that logic works for Loshnor.

Me: Is he good yet?

LTC Players: No.

# 2: He should be able to reach consistent One Round KO Thresholds

I gave him access to a really strong Prf rank lance that can automatically double attack enemies. 

I'm planning to make a lance that automatically double attacks that only Armor Knights can use too. 

Me: Is he good yet?

LTC Players: No.

# 3: He has Good Movement

His Base Movement is 6, the same as any other infantry unit in the game, and he gets exclusive access to this:

Yes, he gets access to an item only he can use that increases his Movement by 1. This means that he'll have 7 Movement, just like mounted units and fliers. 

Me: Is he good yet?

LTC Players: No.

He also has access to Paragon:

Only one other unit in this game gets Paragon, and that's the game's Est. Increasing experience gains should play a big role in making him good.

IS HE GOOD YET?!

And here's the map objective of the first map of the game:

There's not going to be any Casual or Classic mode in this game. The player will be forced to keep everyone alive. Have fun with that additional pressure.

These are not the only mechanics and stuff that I've got in the game, but I hope that's enough to whet your appetite. I'm really excited to make this project! I'll post updates on my progress from time to time.

The Most Busted Mechanic in Fire Emblem: Infinite Range Warp

 

Out of curiosity, is anyone surprised that warp is # 1 on this list? Yeah, me neither. If you've been reading this list, you'll notice that one theme of busted mechanics boils down to: "This mechanic makes it easier to get from Point A to Point B". In that regard, nothing makes it easier to get from Point A to Point B than the Warp Staff. 

Any run that uses the warp staff is usually called a "warp skip" run. That tells you everything you need to know about how stupidly powerful the warp staff is: It lets you skip entire chapters because you can bring someone straight to the boss, or the throne. All those enemies on the map between the player and the boss / throne are pointless since warp lets the player effortlessly beat the map without needing to deal with them.

Like Awakening's Pair Up, the warp staff instantly dominates the game's design. Any character who can use warp is high tier at least, and the best unit in the game under other circumstances. In order to make warp not broken, the game has to be designed in such a way that getting from Point A to Point B isn't the main objective. Most of the time, a given map objective in Fire Emblem will require that, which means that warp will break it in half. 

 I'll finish this post with something that a Fire Emblem reddit user said 6 years ago:

"The only way warp can "work" is if you deliberately design maps that force the player to use warp in certain spots and take the warp staff out of the player's hands in other areas that would otherwise break the game. 

Can warp be designed well? Yes, but it requires a shitton of playtesting and being aware that any oversight whatsoever can break your game in half. Or, you nerf warp to the ground to the point where it's a stupid gimmick. And what benefit does it bring you? Warp in its inherent nature basically lets you skip vast swathes of a given chapter, which basically goes against the entire point of designing chapters, terrain, enemy layouts, etc. to begin with."

(Source: https://www.reddit.com/r/fireemblem/comments/9c099v/comment/e57lqbm/) 

Top 10 Most Busted Mechanics in Fire Emblem # 2: Ferrying Mechanics (Awakening Pair-Up & The Rescue Mechanic)

 

Awakening Pair-Up

      If there's one mechanic that's absurdly overpowered, it's Pair Up from Awakening. Pair Up's power comes from how massive and gargantuan the stat boosts are. If that wasn't enough, Pair-Up also provides two additional bonuses that are both really powerful: The first is Dual Strike wherein the backup character can also attack, making it significantly easier to kill enemies. The second is Dual Guard, where the backup unit has the ability to completely block an attack, thereby negating enemy damage.

      So why is Awakening's Pair Up mechanic this high on the list? Well....

It makes juggernauting extremely easy: Pair-Up grants massive stat bonuses to the point where a character can become powerful enough to steamroll the game by themselves. This is what leads to the Robin solos. 

In addition to that, being able to attack again or potentially block all damage from an enemy attack makes Pair-Up that much more powerful as a mechanic. It can help your lead unit kill faster, and it can keep them alive longer. It can do pretty much everything.

It Dominates the Game's Design

Pair Up is so powerful that the entire game has to be designed around it. If the game isn't, then there's no challenge. However, by designing the entire game around it, the player is essentially forced to use it. Though to be fair, Pair Up is so beneficial that there's no reason not to use it so the game designers might as well assume that it will be used. After all, there's no drawback to using Pair Up, which reinforces just how dominant the mechanic is.

But what about Fates? 

That game did Pair Up right, didn't it? Not really. Even if the Fates version of Pair Up is more balanced and better designed than Awakening's, it's still way too powerful. Dual Guard still makes juggernauting relatively easy since the stat boosts that can come from that can still be huge. Slow characters can become fast, characters that deal low damage can kill things, and thanks to the shields becoming consistent, a character with Dual Guard has better survivability. 

Recap: Even when it's better balanced, Pair Up makes juggernauting far too easy. It's a mechanic that's so powerful that it always dominates the game's design. There's no drawback to using it, and because the game designs itself with the use of this mechanic in mind, not using it can put the player at a disadvantage.

The Rescue Mechanic

And here we have the more balanced, but still broken, older sibling of Pair Up: Rescue. The rescue mechanic could be best defined as: 

"Rescuing allows playable units to pick up allied units – using the Rescue command – who are smaller than them, in order to protect them from harm or to carry them around the battlefield."

(Source: https://fireemblemwiki.org/wiki/Rescue_%28command%29)

Why is the mechanic this high up the list? In the hands of the right player, the rescue mechanic can do a lot! It allows players to move longer distances in shorter periods of time. Remember the # 5 spot on this list?  The spot about fliers and mounted units? This mechanic gives them an even bigger advantage over infantry units because this is valuable utility they can use, and take advantage of, that infantry units can't. Fliers can even rescue infantry units across terrain like water tiles and mountains, making fliers even better than before.

Scylla did a great job pointing out another reason why rescue is busted: "Rescue also allows you to be far more aggressive with your positioning because you can just pull a unit out of a bad spot;"

What makes the mechanic even more powerful is when players start implementing rescue chains, where multiple mounted and flying units take a rescued character and ferry them across the map. It's pretty common among faster playthroughs, and this ultimately results in the player being able to beat entire maps in quicker periods of time. It also results in the player being incentivized to use mostly mounted and flying units, which is bad for the purpose of balancing.

Quick Recap: Rescuing is busted because it allows the player to move from A to B in far faster periods of time, erases the negatives of bad positioning, and makes mounted and flying units even better by giving them additional, powerful utility. 

Moral of the Story: Ferrying mechanics are super busted, and Fire Emblem as a franchise would do well to remove them from future titles.

Top 10 Most Busted Mechanics: Movement Refreshing Shenanigans (# 3)

 

# 3 - Movement Refreshing Shenanigans

Want to make your game easier to beat? Create a way for the player to make one or more units be able to move again. Dancers first debuted in Fire Emblem 3 Book 2, and ever since then they've made a huge impact on their respective games. If you want to beat the game quickly, you're going to make effective use of them. 

Then Holy War came around and gave dancers the ability to refresh the movement of up to four different units at once. The amount of strategies that opens up is insane! 

That being said, dancers aren't really enough to make it this high up the list. That's why this entry is titled "Movement Refreshing Shenanigans". This entry encompasses all the other additional ways in which one or more units can move again. This includes stuff like:

Galeforce - A skill where a Dark Flier in Awakening will be able to move again after killing an enemy. Keep in mind, Dark Fliers are an eight movement flier class that have access to tomes. They can easily kill enemies, which means that they can move a very long distance and kill two enemies per turn. Keep in mind that this skill exists in a game where dancers also exist. 

Dance of the Goddess / Goddess Dance: A gambit / emblem where you can refresh 4 adjacent units. Keep in mind that this exists in a game where there's also a dancer. Scylla pointed out that one unit can "move 4 times in one turn". Super busted.

Raging Storm (Three Houses): "Effective against Dragon foes; If attack lands, user can move again." 

Unlike Galeforce, Edelgard doesn't even have to land a kill and she'll still get to move again. Make Edelgard a Wyvern and she'll be able to break the game efficiently. It's also possible to use this up to 5 times. It's true that this reduces the use out of Amyr, but weapons can be repaired in Three Houses, so the reduction in uses doesn't really hold Edelgard back.

The Anew Staff (Fire Emblem 3 Book 2): This version of the Anew staff refreshes the movement of all allies on the battlefield. You read that right: ALL ALLIES ON THE MAP! Sure, it has 3 uses and can't be repaired by the Hammerene, but.....there's still a lot of crazy stuff you can do when you're capable of refreshing everybody on the map, including the dancer. That's more units getting refreshed than all the other options!  There's a reason why FE 12 and Echoes had to nerf this. 

In conclusion, there are a lot of broken tools and abilities to refresh movement in this series! In the hands of the right player, they can utterly trivialize entire chapters.

Top 10 Most Busted Mechanics in Fire Emblem # 4 - Time Rewind Mechanics

 

# 4 - Time Rewind Mechanics

The next major busted mechanic on this list are "time rewind mechanics". Like bonus experience in Path of Radiance, time rewind mechanics like Mila's Turnwheel are supposed to be there to act as a safety net for the player. We've all had stories where the enemy had a super low chance to land a critical hit, or a super low chance to hit our character, and for some reason the RNG gives us a middle finger and the next thing we know, our character dies. Insert Mila's Turnwheel, a convenient way for the player to go back in time and redo the level without having to completely start from the beginning.

It's easy to see the appeal of a mechanic like this: It makes restarting less painful and time-consuming. If you're like me, you probably use this mechanic for this purpose. However, like bonus experience in Path of Radiance, there is a way for a more experienced player to use this in a way that completely breaks the game. 

Scylla pointed out the problem with time rewind mechanics like these: "this is also ridiculous for a similar reason to Rescue; you can take crazy risks and get away with it, because you can just undo undesirable outcomes. The three games that have had this mechanic have been undeniably shaped by them, not as a tool to provide a safety to beginners but instead a 'probability enhancer' to the more experienced." 

So yeah. This game essentially lets you fish for critical hits, and makes it easy to accomplish. Another issue is that Maddening mode of Three Houses seemed explicitly designed with this mechanic in mind. This led to the game implementing same turn ambush spawns, which is bad design. The next point about time rewinding is that it makes games easier, since resetting is less punitive and that so far the games where it's implemented have been really generous with how many charges the player gets. The obvious solution would be to give the player fewer rewinds on higher difficulties, but so far that hasn't happened.

Just to recap, the problems with this mechanic are:

a) Players can rush forward without any consequences.

b) This mechanic works as a way to force the probability to do what the player wants it to do.  

c) It can be used to justify bad map design. 

This is a mechanic so powerful that it will inevitably shape how the game plays, which is why it deserves to be so high up on this list.

Top 10 Most Busted Mechanics in Fire Emblem # 5: Mounted Units, Jagens / Oifayes, Fliers, & Canto

# 5: Mounted Units, Jagens, Oifayes, Fliers, & Canto

So let's start with a simple question: How many Fire Emblem games can you name that do not have a single mounted or flying unit in either the top tier or high tier? 

Go on. I'll wait. 

Yeah, me neither. I can't think of a single game. Literally every single game has a unit on horseback, or a flier, that's at least really good. And when a high movement unit isn't balanced, they tend to break the game. 

Starting off the list are mounted units, aka units that are on horseback. Why are they on the list? Simple. Movement is the best stat in Fire Emblem, and cavaliers / paladins tend to have high movement. So right off the bat they can move from Point A to Point B faster. In addition to that, these classes often have good enough stats to obliterate enemies with ease. In the most unbalanced games they make infantry classes obsolete. 

In addition to that, they usually have partial or total weapon triangle control, rescue utility in some games (we'll get to that at a later post), and powerful skills. It takes a really powerful drawback for these guys to not get used at all. Most Fire Emblem games don't have that. So as a result, pretty much every Fire Emblem game will have at least a few mounted units seeing use destroying enemy units. 

Jagens / Oifayes

One of the most notoriously powerful types of cavaliers are Jagens. They're basically the pre-promoted character that joins the player at the beginning of the game. They're typically the best character in the early game. Their stats are better than everyone else's and they have better weapon ranks, which usually translates into more damage dealing since they almost always start the game pre-equipped with Silver Weapons. 

In short, these are efficient high movement killing machines. The old school wisdom used to be that your growth units will eventually surpass these guys by the end of the game. The problem here is that this growth takes a long time, and by the time the growth units catch up, the Jagen will have already carried your team for a substantial portion of the game. Base stats are more important than growths when ranking units, and Jagens pretty much always have better bases. Also, what happens when the Jagens growths are good enough to sustain them? That's when you get these guys...

Seth and Titania, two gamebreaking characters that are notorious for starting powerful and staying powerful. The real question is this: Why do Fire Emblem games continue to hand Jagens out to the player? At this point, it seems like tradition for tradition's sake. If a Fire Emblem game wanted to be truly innovative, they'd get rid of the Jagens.

Fliers

So let's take everything that I said about cavaliers and now give them the power of flight. Meet the flying units. They can do everything a mounted cavalier can do, but better. Fliers get the additional bonus of ignoring terrain that could otherwise potentially slow down a mounted knight, or an infantry unit. If a mounted knight isn't at the top of a tier list, chances are it's because the flier beat them. Pegasus Knights and Wyvern Knights also tend to dominate the games that they're in. 

"But bows and magic can deal effective damage against fliers. They already have a drawback."

That might sound like a legitimate drawback on paper, but in practice: 

• There usually aren't enough of these enemies to make a difference.

• When they do show up, they're easy to play around.

• Some games provide items that nullify effective damage. Sometimes a flying unit can simply dismount to avoid the effective damage drawback too.

• Wyverns are typically bulky enough to survive an attack from effective damage.

So enemy archers and mages are not sufficient to hold flying units in check. Sadly, fliers have only gotten stronger with more recent titles. In Awakening, the Dark Flier has Galeforce and great stats, Wyverns and Malig Knights are really powerful in Fates, Palla's really powerful in Echoes, Three Houses is Wyvern Central, and I've heard that Engage also has a flier problem (can someone confirm or deny this?). 

In addition to all of this, mounted and flying units also have an additional skill that really makes them busted:

Canto

Say hello to Canto, the "skill that grants mounted units the ability to move again after performing certain actions, assuming the unit has not already moved their maximum allotted spaces in that turn." (Source: https://fireemblem.fandom.com/wiki/Canto)

Why is this skill busted? It's busted because a mounted unit can attack, and then can continue to move forward even after attacking. In other words, you can maintain a powerful offensive momentum throughout the entire game. This is a skill that mounted and flying units had that infantry units didn't. As a result, it gave additional utility to two types of classes that didn't need any more.

Canto could also be used after rescuing a village, rescuing an allied unit, or using an item. It just gave additional movement strategies to the classes with high movement. This made mounted and flying units even better since it meant that there were more strategies one could employ with them.  

I should point out that moving after attacking was limited to the Jugdral and Tellius games. In the GBA games, it was slightly nerfed since high movement units couldn't use it after attacking, but it was still good. 

So, to summarize everything

• Mounted and flying units have better movement, better stats, partial to full weapon triangle control, rescue utility and canto. They're classes that dominate their respective games because they can do everything that infantry combat units can do, but better. 

• If Intelligent Systems wants to improve the gameplay of future Fire Emblem titles, it should figure out a way to truly balance these classes so that infantry units are more worth using. 

The Top 10 Most Busted Mechanics in Fire Emblem: # 8, # 7, & # 6

 # 8 - Bonus Experience (Path of Radiance)

The next entry on the list of busted mechanics is bonus experience from Fire Emblem: Path of Radiance. Some of you might have read that statement and might be thinking "but bonus experience is in other games besides Path of Radiance. Why is this game being singled out?" We'll get to that.

Bonus Experience is one of those mechanics that sounds like a good safety net idea. Is there a unit who's falling behind? Give them some free experience so that they can catch up with your strongest units. It's a great idea in theory, but there's a problem: That experience can be freely given to anyone, including your best units. 

And this is why the mechanic is on this list: Your best units can be given even MORE experience so that the gap between your strongest and weakest units furthers even more. Here's one tip that the Fire Emblem wiki page for Bonus Experience mentions:

"You can first use Bonus EXP once you reach Chapter 8. You can use a little on Ike and Oscar, Kieran, or even Boyd at that time, but your best bet is to save it for two chapters and immediately pour as much as possible into Marcia. As a flier, she can make good use of it to instantly become a stronger, more mobile version of Titania."

Source: https://fireemblem.fandom.com/wiki/Bonus_Experience

I actually did this during my last playthrough of Path of Radiance. I dumped all my Bonus Experience onto Marcia as soon as I got her, and she mercilessly annihilated the game. This is why Marcia's considered the best unit in the game: She's the best candidate for a bonus experience dump, which is all she needs to destroy the game. 

Remember the # 10 entry, Paragon and Veteran? Two skills that let units rapidly accumulate experience? Bonus Experience takes the most broken aspects of those skills, and dials it up to 11. Characters like Marcia and Oscar can instantly promote and be used as a means to obliterate the game. What separates Path of Radiance from Radiant Dawn is that even on Hard Mode (can't speak for Maniac Mode) you're given a BUNCH of Bonus Experience, which allows for things like this to happen.

# 7 - Reclassing

I'm curious to see what everyone's reactions will be to this. Some people might agree while others disagree. The point of reclassing is that any character in the player's army can be whoever the player wants them to be. Ultimate customizability! Who could say no to that? 

The issue with reclassing is that it becomes very difficult to design the game because the game developers have no idea what the players will have access to at any given moment. How could they? There's a near infinite number of possibilities for any character to be at a given time!

 Another major problem is that reclassing can easily make a character really strong with virtually no effort. 

 Three Houses is probably the biggest offender here where everyone in the game can turn into a powerful Wyvern Lord, and gain the strongest Battalion abilities, gambits, and skills. As a result, it makes the game that much easier to break. 

 Wolf and Sedgar easily become really powerful when reclassed into Generals in Shadow Dragon, Jakob in Conquest can be reclassed into a Paladin, Elise can become a Wyvern, which in turn create new ways for the player to break the game. 

To recap, reclassing is a mechanic that makes balancing and designing the game that much more challenging AND it makes it too easy to make a powerful unit.

# 6 - Stride

Speaking of Three Houses and "broken", the Stride gambit makes its debut here at number 6. Stride is a gambit that gives up to 12 different units + 5 Movement. + 5 MOVEMENT?! ARE YOU KIDDING ME? As plenty of people will tell you, movement is the best stat in Fire Emblem. Being able to get from Point A to Point B faster is always a good thing, and any tool that enables that will automatically be really valuable.

Increasing movement by one is already very good. + 2 Movement is really good. + 5 is stupid. It makes it super easy to get from Point A to Point B. To make matters worse, Stride is given at an E rank authority in Three Houses! E RANK! Anyone can have Stride from a super early point in the game, and then it'll be there for you the entire time. 

The fact that this can boost the movement of up to twelve different characters also allows for even crazier shenanigans to happen. Combine that with a game where anyone can be a flier, and you get a game that's bound to get broken by a savvy player.

There's no drawback toward using it, and Stride is a big reason why Three Houses chapters can be cleared so easily once you know how to use them. Whoever thought that being able to boost the Movement of multiple units by 5 was a good idea should not be designing Fire Emblem games.