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 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
Cooperative, not competitive β you don't win against other players, you survive with them (or despite them).
Hidden tension β 4 of every 31 players has a secret "special function" they didn't ask for. Some of them kill for fun.
Real-time turns β 60-second windows, SSE-driven, no page refreshes. What everyone does gets resolved at once.
No stats or numbers β all hidden information is hidden. You never see another player's gold, items, or secret role.
Drop-in / drop-out β anyone can take over an AI slot mid-game. Game sessions are 10β15 minutes each.
Quick navigation
For developers
If you're reading this from the repo, the canonical source-of-truth docs are:
GAME_DESIGN.md β the full living design document (every mechanic, balance number, and rationale)
game_config.yaml β the single source of truth for every game number (dragon hunger, turn length, action yields, role countsβ¦)
CLAUDE.md β engineering rules of the road for this project
server/turn_resolver.py β the pure game-logic core. Read this to understand any mechanic at the code level.
Each wiki page ends with an Implementation notes section pointing at the specific files and functions that own that mechanic.