Before it was Crowns & Towns, it had many names.
Some focused on building.
Others leaned into kingdoms.
Some emphasized strategy.
But none of them quite captured what the game was really about.
Because this isn’t just a game about crowns.
And it isn’t just a game about towns.
It’s about how everything connects.
A SYSTEM OF DEPENDENCIES
At the heart of the game is a chain of relationships:
The crown depends on the knight.
The knight depends on the town.
The town depends on the farm.
Nothing stands alone.
Every structure exists because something else supports it.
That idea—the interdependence of everything in the system—became the defining characteristic of the game.
The name needed to reflect that.
WHY “CROWNS & TOWNS”
Crowns & Towns emerged as the simplest way to express the system.
Not by naming everything…
but by naming the endpoints.
The crown represents the top of the system.
The town represents the foundation of structure and growth.
Everything else exists in between.
The knights.
The farms.
The relationships that connect them.
By naming just two parts, the entire system is implied.
BALANCE IN THE NAME
There’s also a subtle balance embedded in the pairing.
The crown is powerful, but dependent.
The town is modest, but essential.
Neither is complete without the rest of the system.
And interestingly, neither receives direct bonuses in the same way other structures do.
The crown cannot generate additional crowns.
The town cannot generate additional towns.
Meanwhile:
Crowns can create a free knight.
Farms can create additional farms.
This makes the endpoints unique.
They define the system, but don’t expand themselves.
A NAME THAT FITS THE SYSTEM
In the end, the right name wasn’t the most descriptive.
It was the most representative.
Two words.
Two ends of the system.
Everything else implied.
Clean.
Balanced.
Complete.
That’s what Crowns & Towns became.
And once it did, there was no reason to call it anything else.