Log a world test
Name your world, say what system you're modelling, what you tested, and what happened. Setup guide
Your first world/system test
A system model is a world with rules that connect to each other — resources to population, water quality to fish, wetlands to settlement health. Testing it means finding out what those rules actually produce, not just what you designed them to do.
Name your world
Give it an identity — even a working title helps you track versions.
Pick a system type
Navigation, ecosystem, trade, settlement, survival — or describe your own.
Decide what you're testing
One question: what happens if this resource runs out? What if this route is blocked?
Run it
Play it through on paper, with friends, or as a simple digital model.
Record what happened
Not what you expected — what actually occurred, including surprises.
Write your version
Version 1, 2, 3 — so you can trace what changed between tests.
Tips & safety
- Nothing surprising happened?: That's still useful — it tells you the system is stable under that test.
- Keep it playable: A world only a few people understand is hard to test — simpler rules are often stronger.
- Cost: Paper, dice, and counters — under $10, or free if you already have them.
Show, don't just tell
Example world test
- World
- Flooded Valley v3
- System
- Ecosystem / restoration model
- Outcome
- Trading route removed — players cooperated more
What actually happened when tested, not just what was designed.
Borrowed from MaramaTrap's example-photo pattern — works for every platform.
Pick your quest
Choose a mission, or design freely with no constraint.