Thousands of Kingshot kingdoms, thousands of separate Discord servers, and no way to tell whether the person offering you a kingdom is even in it. This is the layer that answers that one question — and the reason people bother answering it.
Nobody links a player ID for a badge. They link it because they are tired of pasting every gift code into alliance chat and then chasing eighty people for two days.
/redeem register id: kingdom: once, with your player ID and the kingdom number you are in./redeem status shows what happened to the last five. /redeem stop ends it immediately.That first attempt is also the check: it is sent with the kingdom you declared, so the reply tells us whether you are in it. Registering for automatic codes is the verification — there is no second step and no form.
Five rungs, and the badge text is the product. A badge that overstates is worse than no badge, because the whole point is that somebody can stake a hundred accounts on it.
| 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 and is the work of a later build; 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.