Build → Support → Record → Score
At first glance, this sequence may look like a simple set of instructions.
In reality, it defines the entire gameplay loop of Crowns & Towns.
Each word represents a distinct phase of player interaction:
Build — the act of placing structures and exploring possibilities
Support — the logic that determines which structures hold up others
Record — the moment of checking and writing down what qualifies
Score — the final tally of what your system produced
This is not just a rule sequence. It is the experience of play.
The shift to this model was a turning point in the design.
Originally, scoring could have been explained as a set of rules and calculations.
But that approach increased friction and made the system feel heavier than it was.
By reframing everything as actions instead of formulas, the game became easier to understand, easier to remember, and more natural to execute.
Players are not thinking in terms of equations.
They are simply moving through a process.
Build something.
See what supports it.
Record what counts.
Score the result.
That flow reduces cognitive load while preserving depth.
More importantly, it allows the system to teach itself.
Players learn by doing, not by decoding rules.
This reveals a broader design principle:
If a game can be reduced to a small set of clear verbs,
those verbs are likely the clearest expression of what the game truly is.
In Crowns & Towns, these four verbs are not just instructions.
They are the structure behind every decision, every outcome, and every successful kingdom built along the way.