Fire Emblem, Into the Breach and XCOM Movement in Godot

The direct answer

Fire Emblem, Into the Breach, and modern XCOM can use the same Godot grid and range-search layer, but they need different movement contracts. Fire Emblem combines faction phases with profile-dependent terrain costs and sequential unit commits. Into the Breach shows enemy intents, lets player actions change the board immediately, then resolves those intents in a deterministic order. Modern Firaxis XCOM gives each soldier two action points and presents movement as one-action and two-action bands.

The grid can be shared. The movement contract can't.

Compare the three movement contracts

The path query may look similar across all three games. Turn ownership, pricing, prediction, and state commitment are where their architectures separate.

What you can share safely

All three systems can read the same stable board facts: cell adjacency, authored terrain, static blockers, and current occupancy. They can also share a range solver if the query accepts a movement profile and a budget instead of reading one global set of assumptions.

Keep pricing, state ownership, and prediction outside the shared grid. If those rules leak into one get_path() function, the second game mode usually starts by adding booleans. The third starts by making them disagree.

• How terrain is priced for the selected unit.
• Whether a destination costs movement points or action points.
• When a move becomes committed state.
• Whether future actions are visible intents or hidden decisions.
• How pushes, overwatch, and other interrupts change resolution.

Fire Emblem: terrain profiles inside faction phases

The documented baseline here is Fire Emblem: Shadow Dragon. Nintendo's official manual says that play alternates between Player and Enemy phases. It shows a selected unit's movement range in blue and says that class and terrain affect that range.

Exact costs and special movement rules vary across the series, so don't turn one game's forest table into a universal constant. Put the variation in a movement profile. The board says which terrain occupies a cell; the selected profile decides whether that terrain is blocked and what entering it costs.

The tactical movement range guide owns the budgeted reachable-cell search and path preview. Action points and terrain costs owns movement_cost_for(cell, profile) and the quote/confirm transaction. The reservation-table guide keeps pass-through, hostile blocking, and legal stopping rules explicit, while the turn-order guide supplies the faction-phase coordinator.

Weapon triangles, combat forecasts, rescue, canto, and title-specific skills sit above this movement contract.

Into the Breach: visible enemy intents and immediate player actions

Subset Games' design postmortem states the central constraints plainly: enemy attacks are shown, there is no hit/miss chance, and results are deterministic during the player turn. The official game page likewise describes every enemy attack as telegraphed.

The important state isn't a more elaborate path. It is the enemy intent and its current prediction. A useful intent records the acting unit, the attack rule, its target or direction, and a stable ordering key. When the player moves, attacks, or pushes a unit, that action updates the live board immediately. The UI then recalculates what the queued enemy intents will do from that state.

When the enemy phase resolves, the coordinator uses a declared total order and revalidates each actor against the current board. A destroyed actor can't still attack because an animation callback arrived late. A displaced actor resolves from its current cell under the game's attack rule.

The turn-order and movement-planning guide owns explicit phases, data-shaped intents, deterministic ordering, and resolution-time revalidation. When a push needs to claim a destination, the reservation layer owns that cell transition.

Damage rules, objectives, and the wider puzzle design remain outside this movement contract.

Modern XCOM: one-action and two-action movement bands

The XCOM 2 manual gives each soldier two action points. A blue outline shows where the soldier can move for one AP; a yellow outline shows the two-AP dash range. Overwatch then introduces a separate interruption rule when an enemy moves within line of sight.

This is the modern Firaxis baseline, not a statement about every XCOM game. The 1994 original used granular time units. Jake Solomon has explained that the newer move-action model made squad plans more direct than the old accounting system.

For a Godot implementation, query the reachable set at the one-action budget and again at the two-action budget. Don't assume the second query must literally be 2 * first_budget; abilities, traversal links, and the game's own movement data may define those allowances differently.

The range-search guide owns those reachable sets. The AP transaction can represent a move priced at one or two actions, but its Fire Emblem-style entered-terrain ledger is not the XCOM payment model. Sequential soldier activations belong to the turn coordinator.

An exact XCOM-like game also needs elevation, cover, visibility, traversal links, concealment, and interrupts. Those systems affect movement decisions, but they aren't squeezed into this comparison as unfinished code.

Which contract should you prototype first?

Pick the row that contains the project's actual uncertainty. If the risk is terrain pricing, a telegraph prototype won't answer it. If the risk is whether three visible enemy attacks remain readable after two pushes, a larger movement map won't answer that either.

Proof for the shared Godot layers

These are correctness receipts for the individual layers, not evidence that the named games were reproduced. This comparison ships no combined source project and makes no benchmark claim.