Server Templates

A new Discord server is an empty room and a hundred decisions. There are websites that let you click a structure together for that; what comes out is a link you can use once and that is of no use on an existing server.

Here it works differently:

/aufbau vorlagen
/aufbau vorschau vorlage:community
/aufbau starten vorlage:community bestaetigen:ja

Invite the bot, three commands, a finished server.

What comes out of it

The Community template creates:

5 roles — Admin, Moderation, Stammgast, Mitglied, Stumm. Only Admin gets administrator permissions; Moderation gets exactly what is needed for moderating, and not one bit more. Stumm has no permissions at all and is meant for the case where someone needs a break.

5 categories with 22 channels:

Category	What is in it
Information	willkommen, regeln, ankündigungen, rollen, vorstellung — all read-only
Unterhaltung (chat)	allgemein, medien, memes, offtopic, bot-befehle
Austausch (exchange)	vorschläge, fragen-und-hilfe, geburtstage, sternstunden
Sprachkanäle (voice channels)	Lounge, Nebenraum, Ruhiger Raum, AFK
Team	team-chat, logbuch, schutz-meldungen, Teambesprechung — visible to the team only

The permissions are thought through: everyone can read regeln and ankündigungen and nobody can write in them, the team area is invisible to everyone else.

Three channels are groundwork for modules you switch on afterwards: geburtstage for the birthday module, sternstunden for the Starboard, schutz-meldungen for Anti-Nuke and raid protection.

Looking at it beforehand

In the dashboard under Vorlagen (templates) the template is shown the way Discord would show it: the sidebar with categories, hashes and speakers, a padlock on the shielded channels. Next to it the roles with their colours and one sentence each on what they are allowed to do.

A table of channel names does not answer the question you have beforehand: what does my server look like afterwards? From there the template can also be applied directly — it is the same job as via the command.

Things are only added

This is nailed down and not configurable: a template creates what is missing and does not touch anything that already exists. There is no "Ersetzen" (replace) as with restoring — anyone trying out a template does not expect something to disappear in the process.

Which also means: you can apply it to a server that is already running. If a channel is already called allgemein, it stays as it is.

The plan first

/aufbau vorschau tells you beforehand how many roles and channels would be created, how many existing ones would be adjusted and how long it takes. Only bestaetigen:ja really sets it off.

The build then runs as a background job, not inside the command — creating thirty channels takes one to two minutes, because Discord sets the pace. /sicherung stand shows how far along it is.

Afterwards

/setup

The channels are there, but the modules do not know anything about them yet. The greeting, the log, the Starboard and the protection modules each want to be pointed at the new channels once.

What the bot needs for this

Kanäle verwalten (manage channels) and Rollen verwalten (manage roles). And the Fishbot role should sit at the top of the role list — Discord does not let any bot create roles that would sit above its own. The plan warns beforehand if that is going to be a problem.

The Schauraum

The Schauraum (showroom) template is built for a different purpose than the others: it creates a channel of its own for every module, and the bot posts a message in each one showing exactly that module — with a description, commands, price and a button into the wiki.

That is the server you show people. Instead of a price list nobody reads, or a half-hour demo with a shared screen, someone interested clicks through it themselves.

Three steps:

/aufbau vorschau vorlage:showroom                → what would be created
/aufbau starten vorlage:showroom bestaetigen:ja  → the channels
/showroom nachrichten bestaetigen:ja             → the messages

The build comes from the module catalogue and not from a second list. Every new module is therefore in the showroom by itself — a hand-maintained demo list would be out of date after the second new module, and nothing looks worse in a sales conversation than a showroom with half of it missing. Planned modules stay out: a channel saying "coming soon" only raises the question of what else is missing.

All channels are read-only. A showroom where visitors can write is a chat after a week, and the examples get lost between the replies. The buttons still work — nobody needs write permissions for those.

/showroom nachrichten also runs on a server that is already up: posting happens in every channel whose name matches a module. A second call posts everything a second time — in channels that are not its own the bot clears nothing up, a human does that.

Your own templates

If you have a server that is set up exactly the way you need it, it also works the other way round: create a backup and load it onto the next server. Matching is done by name, not by ID — which is why a backup also works as a template on someone else's server.

Commands

Command	What it does
/aufbau vorlagen	which templates there are and what is in them
/aufbau vorschau	what would happen on this server
/aufbau starten	actually create it (only with bestaetigen:ja)

All commands require the Server verwalten (manage server) permission.