Check the kind of battle first
Alicesoft's legacy support FAQ distinguishes army battles from individual dungeon fights; the skills available can differ. Do not assume that a unit's useful field ability will solve a dungeon encounter. Check the actual command list for the battle you are preparing to fight.
Our recommended preparation order is battle type → roles → available commands → resources → reserve. It keeps you from choosing units based only on a familiar name or one large number.
Compare jobs, not just troop totals
Use this worksheet before a difficult fight. It is an editorial planning tool, not a hidden game formula.
| Job you need | Question to ask in the unit screen |
|---|---|
| Protect the force | Which available unit can defend or reduce pressure? |
| Deal useful damage | Which attack can reach the target causing trouble? |
| Support the plan | Is a healing, control or support command useful here? |
| Handle the aftermath | What remains available if the first plan fails? |
Try to identify why each selected unit belongs in the lineup. If two choices serve the same purpose, compare what each contributes to this particular encounter rather than declaring one universally better.
Avoid a false economy
Spending everything on the next attack leaves fewer options to react. Before expanding, review what you would need to restore the army or deal with pressure elsewhere. A quiet front can still be worth checking before the turn ends.
The legacy community FAQ describes enemy troop scaling linked to army size or territory count, depending on the enemy category, and different defender advantages for fields, towns and castles. Inspect the actual opposing formation rather than assuming your previous victory proves the next battle will be easy. We do not publish an unverified Steam damage formula.
Do not use battle preparation as a free preview
Alicesoft's legacy FAQ says that canceling after reaching commander selection still spends the prepared action. Inspect what you can before starting the command, and save first if you are uncertain. This is documented original-release behavior; it has not been independently tested here on Steam.
If the battle goes badly
Record what actually failed: reaching the target, surviving an attack, having the right command, or preparing the wrong battle type. Change that part of the lineup first. Repeating the same decision without diagnosing the loss teaches little.
For dungeon skill differences, consult the Alicesoft support FAQ. For a lost turn plan, return to the beginner checklist. If your army problem is a missing role, read commander recruitment.
Sources & version scope
- Alicesoft — Sengoku Rance support — Legacy Japanese release support; not a Steam patch recommendation.
- KrossRoads / DarkMaster22 — FAQ v1.5.5 — 2012 legacy FAQ; not Steam build testing.
Sources checked 2026-10-06. This is source-based editorial guidance; no first-hand Steam playtest is claimed.
