The kingdom council

Pact registry

A pact reads as live only when every alliance in it that has a linked Discord server pressed Confirm in that server. Every other alliance is shown as declared by the kingdom server — a record of what the council wrote down, not a claim that the alliance agreed. Nothing on this page implies a confirmation that did not happen. These are player agreements: the game enforces none of them.

Rotation

What is next

Times are shown in your own device's clock. Transfer-window dates come from the transfer almanac and are true for every kingdom in the group, not just this one; the rotation and any dated announcement come from this kingdom's own council server.

What a kingdom council is, and what this page is not

04 of the hub's design calls a kingdom's own Discord the home layer: it is theirs, and nothing here replaces it. The alliances of a kingdom meet in one server to negotiate truces, plan castle fights, run KvK and argue about hive space. That server is where the kingdom is actually run.

What it does badly is keeping the record. The NAP list is a pinned message from four months ago that nobody can find. The castle rotation is in a spreadsheet one officer owns. A kingdom-wide announcement is typed six times into six alliance servers by hand, and two of them miss it. So the bot writes down three things and delivers one:

• Who is at peace with whom, with each alliance confirming for itself, in its own room.
• Whose turn it is, with the reminder arriving on its own, rendered in each member's own clock.
• What was announced, delivered once into every alliance server that opted in.

What it deliberately never does

• Score attendance. A rotation knows whose turn it was, and recording who turned up would be trivial. It is not recorded, and there is no column for it. A bot that can be used to justify a purge becomes the villain in somebody's alliance drama, and that is a worse outcome than a missing statistic.
• Reach a server that did not opt in. An announcement goes to alliance servers that subscribe to their kingdom's circle. Leaving is one command — /council circle hear:False — and it takes effect on the next message, because the circle is read at the moment something is sent and never cached.
• Carry a price. Century Games prohibits private and third-party account trading. Every free-text field here — a pact's terms, an announcement — is screened before it is stored, so a mention of money, a payment method or an account sale is refused rather than stored and hidden later.
• Name an individual player. No Discord account, no player ID, no roster. Alliance tags and kingdom numbers only.

Running it in your kingdom's server

1. Say what the server is. /passport server kind:kingdom — the one shared server where your alliances meet, not one alliance's own room.
2. Say which kingdom. /config set kingdom:652, then /embassy setup channel:#kingdom-hall.
3. Get verified. Eight members whose player IDs the publisher's own backend confirms are in your kingdom. /redeem register is the fastest route — every member who registers for automatic gift codes is verified by the act of registering.
4. Record a pact. /council nap add parties:TNP, ABC kind:nap terms:no hive attacks until:2026-10-01. Each named alliance whose own server is linked and verified gets a Confirm button in that server.
5. Set the rotation. /council rotation set opens a box: the turn order, the schedule (weekly sat 20:00, or a list of dates), and what comes round.
6. Publish, if you want to. public:True on either puts it on this page. A public NAP registry is a recruiting asset — it tells an alliance shopping for a kingdom that this one is run rather than fought over.

Rung 3 means an administrator of a group-verified server, vouched by two verified members, for at least fourteen days. Speaking for a whole kingdom in six other servers is not something one unverified account should be able to do, so it is the same bar the Special Invite market and the King's Desk use.

Where to go next