Choose your testing route
Recommended order, prerequisites and result labels for runtime 0.4.3.
This is a manual acceptance guide for the current development build. These instructions are recommended tests, not claims that people have already completed them. Automated results are described separately.
The three documentation sites are reading resources. Play happens in Discord or the account browser provided by the operator. Do not enter a Discord bot token, account password or link code into a documentation page.
Player routes use earned items and the authoritative real clock. A listed work duration is a mechanical timer, not a claim about active human playtime. Wait for the displayed boundary and refresh; refreshing does not advance time. Weather, site stock, facilities and existing shared progress can change availability or duration.
Step by step
Tick a step after observing the expected result. Saved on this device only.
01Begin with one fresh tester
Run Command visibility, then First session, then Food and tools. Choose Browser linking before your first Discord play if you want one shared browser/Discord character.
The tester can identify their character, current place, possessions and next action.
02Add one production branch
Run Routine and active work, then Expert timber, then Measured manufacture. Keep the resulting batch IDs and quantities in your private notes.
Output is earned and its ancestry is traceable.
03Bring a second consenting tester
Have both players complete the Earned multiplayer preparation route, then run Barter, Funded buy order, Commission, Delivery and Rental.
Two independent characters exchange real goods and funded fees.
04Test encounters and social systems
Run the Brush Hare encounter, a shared Sentinel formation, earned AFK farming, and Guild treasury. Continue to advanced paths only when their displayed prerequisites are earned.
Report unavailable prerequisites as blocked instead of bypassing them.
05Close with reliability and longer journeys
Repeat the mobile/desktop sweep. Operators run isolated restart and restore drills; longer player groups take the professional, solo and raider release paths.
Keep human observations distinct from simulator or fixture results.
Reference
| Result | Use it when |
|---|---|
| Pass | Every expected result was observed on the stated build and account state. |
| Fail | An observed result contradicts the expected behavior; include a reproducible step and receipt. |
| Blocked | A prerequisite, client, second player or operator environment is unavailable. |
| Not run | The path has not been attempted. |
| Design feedback | The rules work as written, but clarity, pacing or enjoyment needs review. |