← Home

About this guide

What this site is

Warlord: Awaji Guide & Wiki is an independent player reference. It is not operated by, affiliated with, or endorsed by Darkmatter Games. The purpose is practical: help a reader reach a current release answer, understand the demo, or find a focused explanation of combat terrain, army progression, campaign systems, and reported issues.

How information is selected

Store availability, platform support, requirements, languages, and release state are checked against the Steam listing and app response. Descriptions of unfinished campaign systems are attributed to dated developer posts or replies. A community discussion can document that a symptom was reported, but one report is never presented as proof that every player is affected.

When a source gives only a qualitative statement, the guide preserves that boundary. For example, a developer statement that water slows movement does not establish an exact slowdown percentage. A tentative Steam Cloud suggestion does not become a guaranteed repair. Unknown controls, formulas, prices, and final progression limits are left unknown until they can be verified.

Release updates

The current edition was prepared before the planned September 9, 2026 release. Time-sensitive pages show review dates and distinguish the playable demo from the described full campaign. When Steam changes from Coming Soon to released, the site will recheck the homepage, release, demo, combat, army, and campaign pages together. Formal-release behavior will replace pre-release descriptions only after it is observed or published by a reliable source.

Corrections and source labels

Major pages link directly to the Steam listing, developer announcements, or the discussion being summarized. If a later patch, store change, or developer clarification contradicts an older statement, the dated newer information takes priority and the affected page receives a new review date. Historical demo facts remain labeled as historical rather than silently becoming campaign rules.

Readers should confirm purchases and live availability on Steam. For technical support, use a support or community route published by the developer and include the current build, exact symptom, and screenshots when relevant.