Warlord: Awaji field note
Warlord: Awaji Terrain & Positioning Guide
Use the developer's published terrain information: slope and water slowdown, nighttime concealment, and elevation-based ranged reach.
Quick answer
The public developer guidance supports three qualitative terrain observations: slopes and water slow movement, higher ranged troops gain reach, and nighttime—not foliage—is the documented concealment condition.
These are qualitative statements from a May 22, 2026 developer reply. No exact slowdown percentage, range formula, detection radius, control input, or timing window was published there.
Plan movement around slopes and water
The developer said both slopes and water slow movement, but did not publish a slowdown value.
Conservative implications to test in your own battle:
- Compare a direct approach with one that avoids a slope or stream.
- Expect either terrain type to affect arrival time.
- Do not assume water has zero movement cost.
- Reassess the route if reaching useful high ground requires a slow climb.
This does not prove flat ground is always better. It gives you a documented time-cost direction, not an optimal route formula.
Use elevation for ranged reach
The developer said troops higher than the enemy gain longer ranged reach.
A conservative positioning check to test in play is:
- Compare your ranged group's elevation with its target.
- Prefer a position above the target when reach is the goal.
- Account for the slower movement required to climb there.
- Test the actual engagement rather than assuming every hill produces the same benefit.
The source does not publish a height-to-range table or say that elevation changes damage.
Night concealment is not foliage hiding
The same reply distinguishes nighttime visibility from foliage. Troops were described as less visible at night, while foliage did not provide the proposed hiding behavior.
That creates a clear tactical boundary:
- Do not build an ambush around trees or bushes hiding a formation.
- Treat night as the documented concealment condition.
- “Less visible” does not mean completely invisible.
- Do not invent a detection distance or duration.
What official sources do not specify
The public material used here does not support exact instructions for these topics:
| Topic | What is not published |
|---|---|
| Unit spacing | No spacing values, formation spacing rule, or control input |
| Blocking and stamina | No block button, timing window, or stamina formula |
| Slash versus stab | No verified input sequence, damage table, or universal “best” choice |
| Friend-or-foe identification | No documented control or interface rule suitable for a reliable instruction |
Use the game's own prompts for these controls. This guide will not assign buttons or values that the developer source does not provide.
Terrain decision checklist
- Will this route cross a slope or stream and delay contact?
- Can ranged troops take elevation above the target?
- Is the concealment plan based on night rather than foliage?
- Does the plan depend on an exact number that has not been published?
For the playable sample and its cavalry/ranged update, see the demo guide. For the continuous world and camp, see Campaign, Camps & Factions.
Questions to ask after a failed engagement
Use the documented terrain effects as diagnostic questions, not as a claim that one formation or route is universally best.
Did the approach cross water or climb a slope? If so, compare it with a route that stays on flatter ground. The public reply supports a movement slowdown, but it does not say whether every slope or depth of water has the same cost.
Were the ranged troops above or below their target? Elevation is the one published directional advantage for reach. It does not establish a damage bonus, accuracy bonus, or immunity from return fire.
Was the plan relying on vegetation? The developer specifically distinguished night concealment from foliage. A formation standing among trees should not be assumed hidden on the basis of that reply.
Did the result depend on an exact timing window? No block timing, stamina recovery rate, or attack-frame table is available in the cited material. Treat values learned from the current build as observations that may change, and avoid presenting them as permanent rules.
This approach keeps the useful part of the developer's answer—the direction of each terrain effect—without turning a qualitative reply into a formula it never published.