Incremental Pacing
Pacing is a game mechanic of its own. Every level gets a pacing doc under a pacing folder in the docs that mirrors the level's configuration: the currency, the goal and its size, the unlock gates, the tiers of producers with cost, output and what opens and reveals them, the upgrade lines with cost and effect, the hints per progress, the odds of encounters. The doc and the configuration change together.
Why
The director tunes a level's pacing from the doc, without reading code.
How To Apply
- A table per level makes the curve visible at a glance, the tiers comparable and the gaps findable.
- Names of producers, upgrades, tiers, hints and units are content, filled in as Game Work Workflow says and recorded in the pacing doc. Level names never travel between projects.
- A new level's pacing goes into the doc together with its build, the agent's numbers under the ticket's Veto. The build mirrors the doc.
- An unlock gate is written as a rule the player can feel, such as the next producer after the second upgrade, with the reason next to it.
- A getting-used period sits between a new mechanic and the next: the new one is used by hand for a while, such as a few dozen clicks, before anything runs on its own.
- Names within one family never contain each other.