My Character, Weapon & Class Compass

Cai gets a Wooden Sword about half an hour in. I equipped it without thinking, the way you do — the game hands you a weapon, the weapon goes in the slot, and some part of your brain quietly files it under this is who he is now.

Then I opened the class screen to see what he could actually become, and spent the next hour discovering that I had confidently answered a question nobody asked.

The question I had been asking was can Cai use this weapon? The equipment screen answers that one for free, and the answer is yes, obviously, it is in his hand. The question that decides anything is what job am I trying to make Cai good at, and which proficiencies actually lead there? Those produce completely different plans, and only one of them survives contact with the class requirements.

So the sword is not a mistake. It is a perfectly good stick that happens to be in his hands. It is just not worth the twenty hours of Sword training I would have cheerfully poured into it because the game was polite enough to hand me one in the tutorial.

Give every character a job. Train the things that support the job. Let the team cover what the individual cannot.

The army answers the map, not the unit

The mistake I was one evening away from making is, I think, the standard one: trying to build six characters who can each handle anything. It feels responsible. It feels like insurance. What it actually produces is six units who are mediocre at five things, while the early training that could have made one of them genuinely frightening gets spread so thin it does nothing at all.

What I want instead is a roster where the map asks a question and I already know whose turn it is. Something dangerous and far away is the bow specialist. Something armoured is a job for magic. A tile that would kill a fragile unit is where the heavy defender stands, because standing there is his entire contribution and he is good at it. Terrain in the way means a flier. Distance means a mounted unit.

None of those characters can do each other's jobs. That is the point. Between them they cover the board, and I stop spending the first two minutes of every turn wondering who to move.

It is also just easier to hold in my head than "make everyone well-rounded", which sounds like a plan right up until you try to write it down.

How I decide what job a character gets

Three questions, in this order, and I try very hard not to add a fourth.

What is this character already good at? The game hands everyone natural proficiencies and a starting class for a reason, and fighting that on a first run usually means spending scarce development to arrive somewhere the game was taking me anyway.

What does the party actually lack? A sixth competent melee unit is worth almost nothing. The first flier changes which maps are difficult.

What is the cleanest lane that gets there? One class family, one direction, no hedging — because hedging is how I end up with four proficiencies at rank two and nothing at rank five.

Then I write it down and stop re-opening it. Every character's job, lane and reasoning lives on the characters page, not in my memory, which is the entire reason this site exists.

What I am deliberately not doing

I am not spreading early training across every proficiency the menus make visible. The interface shows me Spear, Sword, Axe and Rider for Cai because it shows everybody everything — visibility is not a recommendation, it is just a list.

I am not inventing an exotic build to prove it works. Some of them certainly do, and one or two are probably better than what I have chosen. I would rather finish a run understanding why my ordinary choices worked than spend it demonstrating that an unusual one technically functions.

And I am not treating any of this as final. A first run is where you find out what you enjoy playing. The decisions here are decisions for this save, and writing them down is what stops me re-litigating them at eleven at night.

Recruiting for a gap, not a collection

Recruitment is where the completionist in me does the most damage, because every recruit looks like progress. A recruit who duplicates a job I already have is not progress. She is another unit competing for the same experience, the same deployment slot and the same attention.

So the test is one sentence: does this person change what the army can do, or only how many people are in it?

Noctula goes first on Cai's route because Brawling is a close-range role the early core genuinely does not cover. Io is the answer on both Leda's and Dietrich's routes for the same reason, one step sideways — mounted reach is a different tool, not a seventh variety of infantry. Alexandra is the one I want on Theodora, where flying adds movement the native party has no version of at all, and where the requirements are far friendlier than grinding Support on Cai to get her early.

The actual numbers are on the recruits page, along with how much I trust them. Most of those routes are ones I have not reached, so the requirements are recorded rather than confirmed, and the page says so.

The parts I am least sure about

Three of these are genuinely open, and I would rather leave them labelled than let a first-run guess quietly harden into a rule.

Leda I can understand immediately as a bow unit, but her route unlocks Dancer-related progression, and an extra action is a fundamentally different kind of power from an extra attack. I want to feel the difference rather than decide it from a menu.

Guzran I am leaving flexible on purpose, which is a decision and not an absence of one. Cai, Peter and Tialla already have obvious jobs. I want one physical unit I can point at whichever hole the active team keeps showing.

Lysander is the one I am holding most loosely. Spear and Rider is a sensible first idea, but it comes from launch-week information rather than from playing him, and when I actually reach him I intend to look at his real ranks before committing to anything.

The rule I want visible on every character page

The character does not need to cover every weakness. The army does.

That is the sentence I expect to save me the most wasted training on a first Fire Emblem run. It is also the one I want to find again in six months, when I have forgotten why Cai is carrying a spear he did not start with and some part of my brain has gone back to filing the sword under this is who he is now.