An Ordinary kingdom takes 55 players in a transfer window and a Leading one takes 30 — and of those, 35 or 20 are Ordinary Invites the King hands out, with exactly three Special Invites in the whole kingdom for anyone over the Transfer Power Cap. Paste your roster and the destination: who lands, who is left behind, how many Special Invites you are short, and what the passes cost.
Work out your alliance's moveFree, no account, nothing stored on a server. Every figure quoted from the publisher's own help centre.
Then one command, once, in your alliance's Discord. It asks the game's own backend whether you are really in the kingdom you claim, and everything below runs on the answer:
/passport link id: kingdom:
Or /redeem register id: kingdom: — the same check, and it switches on automatic gift codes at the same time.
Your own account works alone, in a DM — no alliance server needed. Adding it to your server puts codes and alerts in a channel for everyone.
One person can use the calculator today with nobody else present. The rest of the hub is about your alliance, and it opens when eight members of one Discord server have each had a different player ID confirmed in the same kingdom — which is what an alliance is, and what one person with a spare account is not.
0 of 8 verified — eight opens your kingdom's board, your King's desk and your embassy.
This is the count for any server you open this page from. An admin can run /passport server in Discord to see their own, and /passport server list: True turns on a link they can paste into alliance chat so everyone watches the same number.
Sixty-four names in a spreadsheet, three days before Phase I, and one question: can we all go?The alliance relocation board is where an alliance that is moving and a King who wants them find each other with the arithmetic already done and the roster confirmed against the game — not a screenshot of a spreadsheet in a stranger's DMs.
I have 35 Ordinary Invites, 3 Special, two co-managers and a candidate list spread across three private conversations.The King's desk keeps that count in one place, and every invite it logs is confirmed by the Governor who received it, so the ledger is not one person's word.
We want to talk to K652, and all we have is somebody's friend who might know their R5.The embassy is the line between two kingdoms' own Discord servers: you post once in yours, it arrives in theirs, carrying the badge the game itself confirmed.
My Governor is over the Power Cap and there is no way in.The Special Invite market is the one door left — three invites per Ordinary kingdom, and the Kings who hold them.
Register once with /redeem register id: kingdom: and every new gift code found after that is redeemed for your ID within six hours. /redeem status shows what happened to the last five. /redeem stop ends it immediately. It is free, it stays free, and it only ever runs for an ID that its own Discord account registered.
We are not the first bot to do this and we do not pretend to be — other Kingshot bots redeem codes at a scale we are nowhere near, and if you already have one, keep it. It is here because registering is the kingdom check: the first attempt is sent with the kingdom you declared, so the publisher's reply tells us whether you are in it. That is how the hub learns who is where, and it is the mechanism behind everything above, not the reason to come.
Century Games' gift-code service validates a player ID and a kingdom number before it looks at the code. Sent a code that cannot exist, it answers one way when the player is in that kingdom and another way when they are not. Nothing is redeemed, no mail is sent, nothing changes on the account — it is a read-only answer to one question.
| Rung | What happened | The badge says | What a liar has to do |
|---|---|---|---|
| 0 | Somebody typed a kingdom. Recorded, unchecked. | Kingdom claimed: K652 — not checked | Nothing. |
| 1 | The player ID they linked resolves to the kingdom they claim. | Player ID in K652 · checked 2026-09-08 | Know a real player ID in that kingdom. IDs are visible in-game, so this is easy — which is why it is rung 1 and not the top. |
| 2 | Eight or more different Discord accounts in the same server each linked a different player ID that resolves to the same kingdom. | 43 members verified in K652 | Assemble eight Discord accounts and eight real in-kingdom player IDs and a server. That is an alliance. |
| 3 | An administrator of a rung-2 server, admin there for at least fourteen days, confirmed by two other verified members of it. | Admin of K652's alliance server · vouched by 2 verified members | Run a real alliance server for two weeks. |
| 4 | A promise recorded here came true: the players who said they were moving now resolve to the destination kingdom. | Delivered 2 alliance moves, 71 of 74 players landed | Actually deliver. There is no other route. |
Rungs 2 and 3 arrive as servers use the bot. Rung 4 is computed after a transfer window closes; nothing shows a rung-4 badge until there is an outcome behind it.
Stored: your Discord user ID, your player ID, the kingdoms that ID has been in with dates, whatever you typed into /passport declare, and which servers you used the bot in. Not stored: an email address, a real name, a password. There is no account to create and nothing to log into.
Public pages never carry a Discord ID or a player ID. A passport page exists only if its owner turned it on, and its address is an opaque identifier that is not derived from anything you could guess.
/passport unlink deletes all of it. The rows that do anything — the redemption opt-in, the bonds, the kingdom history, every check we made — go immediately, so redemption stops on that tick rather than the next one. What is left is a single row recording that you deleted yourself, erased within seven days.
Counts read live from the hub, including when they are zero. An empty board with an honest number beats a seeded one.
Loading.