Kingshot Discord setup

Five server templates, and why each one is small

Layouts for a Kingshot alliance, a small alliance, a kingdom, a KvK war room and a transfer window. The bot builds one into your server after showing you exactly what it would create. Every one is six to ten channels — and we can tell you precisely what it cost us to learn that.

The argument, before the templates

In September 2026 our own Discord server had 26 channels. Eleven of them had never received a single message. Not quiet — never used, not once, since the day they were created.

We had diagnosed the server's biggest problem as low activity and had been trying to fix it by giving people more places to be active in. That is backwards. An empty channel is evidence to a new member that nobody is here, and twenty-six of them is overwhelming evidence. The rooms were not waiting to be filled; they were the reason the server read as dead.

We cut to eight visible channels. Nothing was deleted — the other eighteen were hidden, so every message in them still exists and any one can be brought back with a single change. Seven of the eighteen had real history in them, and that is exactly why hiding beat deleting.

So every template on this page is small on purpose. Six to ten channels, and the one for a brand-new alliance is four. A template that creates twenty-five channels is not being generous with you. It is handing you the problem we just spent a week undoing, and it is the easiest thing in the world for a bot to do.

If your alliance outgrows eight channels, you will split one yourself — and you will split the right one, which nobody could have guessed from here. Starting small and splitting when a room is genuinely too busy to read is the same move made in the right order.

Alliance

40 to 100 members

8 channels · roles: R5, R4 · alliance

START HERE
#welcome read-only
#announcements read-only
THE ALLIANCE
#general
#events
#rally-calls
#help
JOINING
#recruitment
LEADERSHIP private
#officers private

The common case. Everything an alliance actually does has a room, and nothing else does. #rally-calls earns its own channel because a rally call buried under chat is a rally that fails. #help earns one because an alliance's retention problem is usually a first-week problem.

Why there are not more. The obvious next additions — off-topic, memes, hero builds, screenshots, a voice channel per squad — are the eleven rooms in our own server that never received a single message. An alliance that outgrows eight channels will split one itself, and it will split the right one.

/template preview name:alliance shows exactly what this would create in your server, and changes nothing.

Small or new alliance

under about 30

4 channels · roles: R5 · small-alliance

THE ALLIANCE
#start-here read-only
#general
#events
LEADERSHIP private
#officers private

Deliberately the smallest thing in the set. At twelve members, a rules channel and a welcome channel and an announcements channel are three empty rooms saying the same thing.

Why there are not more. A new alliance with twelve channels looks abandoned on its first day. The failure here is never “we ran out of rooms”, it is “nobody talked because nobody knew where to”. Splitting later is the good problem to have.

/template preview name:small-alliance shows exactly what this would create in your server, and changes nothing.

Kingdom server

several alliances sharing one room

9 channels · roles: King, R5, Diplomat · kingdom

THE KINGDOM
#welcome read-only
#kingdom-announcements read-only
#kingdom-hall
RUNNING THE KINGDOM
#diplomacy
#castle-rotation
#kvk
#transfers
#alliance-desks
LEADERS private
#leaders private

A kingdom server is not a big alliance server. #diplomacy is the room that makes it different: alliances negotiating with each other. #leaders is private from the moment it exists, so members never watch it appear.

Why there are not more. A kingdom has six to twelve alliances, so a channel each is a channel count that grows with the kingdom — the same disease with a respectable reason attached. #alliance-desks gives every alliance a thread instead: same space, one room, and an outsider can read all of it in one place.

/template preview name:kingdom shows exactly what this would create in your server, and changes nothing.

KvK war room

one matchup, start to finish

7 channels · roles: War Council · kvk-war-room

THIS MATCHUP
#matchup-brief read-only
#prep
#rally-calls
#intel
#timers
VOICE
●battle-voice voice
WAR COUNCIL private
#war-council private

Built to be archived when the matchup ends, not to live forever. #matchup-brief is one pinned message so anyone arriving mid-KvK reads one thing. #intel is separate from #prep because it keeps arriving after prep is over.

Why there are not more. There is no #general on purpose. A war room with a general chat becomes a second alliance server, and then it sits empty between KvKs — the same problem, now attached to the room people were most excited about.

/template preview name:kvk-war-room shows exactly what this would create in your server, and changes nothing.

Transfer window room

a window, and the people moving in it

7 channels · roles: Recruiter, Moderator · transfer-window

THE WINDOW
#how-this-works read-only
#kingdom-showcases
#recruiting-posts
#transfer-questions
#moving-together
AFTER
#landed
MODERATION private
#moderators private

Showcases and recruiting posts are two rooms because they are two different acts: one is offering, one is asking. Merged, the asks bury the offers, and a governor shopping for a kingdom is reading for offers. #landed is where people say how it actually went.

Why there are not more. The tempting additions are a channel per transfer group and a channel per destination kingdom. Both scale with something nobody controls, and both are empty until the window opens.

/template preview name:transfer-window shows exactly what this would create in your server, and changes nothing.

How to put one in your server

  1. Add the bot to your server, if it is not there already — the bot page has the link and lists everything it can and cannot do.
  2. Look first. /template list describes the five. /template preview name:alliance shows the exact tree it would build in your server, including everything it would skip. Preview changes nothing at all.
  3. Apply. /template apply name:alliance shows the same tree again with a confirmation you have to press. Nothing is created until you press it.
  4. Changed your mind? /template undo shows what it would remove, what it would hide instead, and what it refuses to touch — then asks you to confirm that too.
  5. /template status tells you at any time what was applied here, what it created, and what it skipped.

What the bot needs, and what it does not have yet

/template list, /template preview and /template status work today. Creating channels needs two permissions the bot was not installed with — Manage Channels and Manage Roles — and Discord does not grant new permissions to an app that is already in a server. If you run apply and the bot does not have them, it says so plainly and tells you what to do rather than failing halfway through.

The bot has never asked for those permissions before, and this is the first feature worth asking for. It does not ask for Administrator, and it does not ask to read your members’ messages — it cannot read what people say to each other, and that does not change.

What it will and will not do to a server that already has people in it

This is the part that matters, because most alliances asking for this already have a server with history in it. Here is exactly what happens, in the same words the bot shows you before it does anything:

This will create channels and roles in this server. It never deletes or renames anything that is already here, and anything with a name we already find is skipped. Undo removes only what this command created, and any channel that has messages in it is hidden rather than deleted. Discord changes made by other people while this runs may not be undoable. Review the preview before you confirm.

  • A name you already have is skipped, not taken over. If you have a #general, the template does not touch it — not renamed, not moved, not re-permissioned, and not counted as something the undo could later remove. The preview names every skip before you confirm, and so does the report afterwards.
  • Undo works from a list of IDs, never from names. Every channel and role the bot creates is recorded by its Discord ID at the moment it is created. Undo reads that list and nothing else. If you delete our #events and make your own with the same name, undo will not touch yours — it is a different ID and it is not on the list.
  • A channel with anything in it is hidden, not deleted. If even one message was posted in a channel the template created, undo hides it from everyone instead of removing it. Every message stays. An admin brings it back in one step: channel settings, Permissions, @everyone, View Channel.
  • If we cannot check whether a channel is empty, we hide it. Not being able to read a channel is not proof that it is empty, so it is treated exactly like a channel with history in it.
  • A channel you renamed is left alone. Renaming a room is the clearest possible sign it stopped being ours and started being yours, so undo refuses it and says so.
  • No role is deleted. The bot cannot see who has which role — it does not have permission to read your member list and we are not asking for it — so it cannot prove a role is unused, and it will not remove one it cannot prove is unused. Roles it created are reported and left for you.
  • Both directions preview first, and neither has a destructive default. Apply and undo each show you the full list and wait for a button. Running the command on its own never changes anything.
  • One template per server at a time. Applying a second one over the first is how a server ends up with twenty-six channels, so it is refused until the first is undone.

Two things we will not tell you

We will not tell you this is safe. It is a tool that creates and removes channels in a live community, and the honest description is what it does and does not do, which is written above rather than summarised into a word.

We will not promise a clean undo. If other people change your server while the command is running — moving a channel, renaming one, deleting one — those changes may not be undoable, and the report will tell you what it could not do rather than quietly skipping it.

Where to go next

Add the botWhat it does, the three permissions it currently asks for, and what it deliberately cannot see. Kingdom councilOnce a kingdom server exists: the pact registry, the castle rotation, and one announcement into every alliance server at once. Transfer almanacWhen the next window runs and its phases in your own clock — what a transfer-window room is built around.
The transfer hubWhat the hub stores about you, and how to delete all of it with one command. Kingdom transfer guideEligibility, cooldown, what you lose, and how Kings actually decide. Alliance move calculatorWhether your alliance fits through the door this window.