πŸ“œ The Codex

A living wiki of roles, rules, and ruin in the kingdom under the dragon's shadow.

Welcome, adventurer. This is the player (and developer) reference for King & Dragon β€” a 31-player browser strategy game where everyone wins or loses together, and cooperation is the only path out from under the dragon's rule.

The Short Version Fill the treasury to 10,000 gold within 32 turns, or kill the dragon. Everyone wins together. Everyone loses together. A single king sets tax rates and decides whether to bribe the dragon each turn. Thirty subjects scheme, farm, fight, betray, and occasionally try to slay the beast themselves.

Core systems

πŸͺ
Pawn Shop (Lombard)
Where fallen players' gear returns to the economy. Recycling, not rebirth.
🌲
Forest Map Minigame
33 clickable areas, 3 unique bow parts, contested discovery, no do-overs.
πŸ‰
The Dragon
Hunger, bribes, fire, and the three weapons that can end it.
βš”οΈ
Roles & Classes
Peasant, Citizen, Knight, Prince, King β€” what each one can and can't do.
πŸ’°
Turn Economy
Declarations, taxes, actions, revolts, and how gold moves every turn.
πŸ—‘οΈ
Special Functions
Thief, Assassin, Vampire, Werewolf β€” secret roles dealt at game start.
🏹
Dragon-Slay Paths
Three weapon sets, one dead dragon. Who can build what.
πŸ‘‘
How to Win (or Lose)
Victory conditions, draw states, and the ways a kingdom can collapse.

Game at a glance

A screenshot of the King & Dragon game board from a peasant's point of view
A peasant's view of a turn in progress β€” declaration form, action buttons, chat, player list, and the pawn shop below.

What makes this game different

Quick navigation

Looking for…Go to
How the dragon decides who to eatThe Dragon
What "followers" do and how to recruit themTurn Economy
The SuperElf Bow and the forest search mechanicForest Map Minigame
What happens when a player diesPawn Shop
The Thief, the Assassin, the Vampire, the WerewolfSpecial Functions
Why the king matters (and why overthrowing one matters more)Roles & Classes

For developers

If you're reading this from the repo, the canonical source-of-truth docs are:

Each wiki page ends with an Implementation notes section pointing at the specific files and functions that own that mechanic.