Palim
design · chapter 10Alpha v0.1.19

The player

Levers · God mode · What the player reads · What the player never does · Where the levers stand today ·

Levers

  • Fiscal: tax rate, tariffs, treasury spending, public works, the grain reserve.

  • Legal: building codes (a fire code that bans thatch), schooling, conservation orders, whether density is allowed.

  • Martial: garrison, walls, tribute, an embassy that makes an ally.

  • Relief: grain reserve, hospital, fire brigade, poor relief.

  • The steward: the town has one mind above the job board, which weighs how far to lean on the fields, the sites, the workshops, the woods and the streets, learns month by month from what the town made of its leaning, and funds the school and the drains when the town can bear it. The player leans on the steward over any of those aims, half a point at a time, up to a full point either way. A lean is a bias in the steward’s judgement, never an order to anyone: the board’s total pull is unchanged, every person still weighs their own pay, and the steward learns around the lean. What a steward learns is kept from one valley to the next.

And one deliberately expensive lever: compulsory purchase. You can order something demolished. It costs money and legitimacy, the people in it are displaced, and the footings stay in the ground. It is the only direct edit and it is meant to feel like one.

God mode

Beside the levers stands god mode, for trying the rules out rather than playing by them, and it says so: its orders cost nothing. Settlers walk in from the valley’s own hinterland, or strangers from the friendliest city abroad, with that city’s name, look and descent; a baby boom doubles every family’s children for five years; the granary gets a year of bread and the chest a purse. Each is an order like any other, so the chronicle records it and a share link gives it again at its turn, and none of them works around the rules: newcomers need roofs, bread and work, and a boom’s children are born to the town’s own mothers, fewer where there is no room or no bread. A checkpoint keeps the whole valley in memory, and going back to it founds the valley again from it. That is not a reroll: the valley is deterministic, so it lives the same future again, flood and all, unless the player decides differently.

What the player reads

A map-first interface with a guided first session, clickable places and council decisions. Along the top, the town’s five readings (people and the roofless, bread in store and how well the town ate, the treasury, the people’s mood, what is being built) and the clock: the speed, and how long the seasons last against the people’s day. Down the left, a rail of tools, each opening a drawer beside the map: the Council, where every lever says what it does and what it is doing now; god mode; the reports, one detailed report at a time with the existing keys (the city, the works, the people, the ground, the sky, the economy, the world outside, learning, the chronicle, the peoples); the map layers; what is drawn; and help. Along the bottom, the chronicle’s newest line. Lenses over the ground for territories, cultures, water, traffic, fertility, snow, and the era that laid every voxel. A launcher that holds every starting setting and keeps what you chose.

What the player never does

Place a building. Command a citizen. Click a technology. Save-scum a flood: the world is deterministic from its seed, so the same valley under the same policy floods on the same day, a saved valley carried on floods on that day too, and the only way to a different outcome is a different decision. Tell the steward what to do: the player leans, the steward judges, and the people choose.

Where the levers stand today

The policy struct, its edicts and its friction exist and the simulation reads them. God mode’s orders are edicts in city/sandbox.rs, and the browser API takes them as settlers, foreigners, baby_boom, gift_grain and gift_treasury. The Council, native and in the WebGPU browser build alike, issues schooling, the fire code, flood works, conservation, street commissioning, density, a paid fire watch, the wall order and an embassy, and steps tax, tariff, garrison, relief, public works, the grain reserve and tribute up and down. The Council also carries the leans on the steward, one pair of buttons per aim, the garrison, the reserve and the relief among them, and the browser API takes them as lean orders; the Learning report shows what the steward is leaning on, how the player leans, and what the town’s shared experience has come to. Compulsory purchase is the inspector’s Buy it out and pull it down on a building you have clicked, and the browser API’s purchase order; the street plan’s own buy-outs, one building a year at most, are a separate rule. Every order is written with the turn it was given at, and a share link carries the orders, so the same link opens the same town. The report panels remain read-only. See open questions.


This chapter is docs/design/10-the-player.md in the repository; the site renders the file as it is.