Server setup

A blueprint is a complete server for one kind of community: categories, channels, roles, permissions, Discord’s own AutoMod rules, the welcome screen, the onboarding questions Discord asks new members, and the house messages (rules, how it works, role pickers). You pick one, the bot compares it with your server, shows exactly what would change, and applies it when you say so.

Nothing happens until you press Apply. Roles are never deleted. A channel of your own is only deleted when you choose “Remove” for it yourself; a plan with an undecided line cannot be applied.

Five blueprints: Gaming community, Crypto & Web3 project, Creator & streamer, Brand & customer community, Esports team & clan. Each is complete on its own. Switching to another type later is allowed: only the differences are applied.

Every category and channel you already have. Where the setup recognises one of yours (a channel called “rules”, “general”, “announcements”…) it proposes “Used as” the matching channel of the blueprint: the channel and its history stay, it gets the house name and permissions. A channel the setup does not recognise gets a choice: keep it as it is, remove it, or use it as one of the blueprint’s channels.

Apply waits until every line has a choice, so nothing is decided for you. A kept channel is left alone on every later run.

The result before it happens, drawn like Discord’s channel list: new channels marked “new”, the ones taken from what you have marked “adopted”, the ones you keep marked “kept”, the ones you remove struck through. It follows your choices on the left as you make them, and lists the roles and Discord’s onboarding questions too.

The bot runs with a written list of permissions, never Administrator, and gets its own permission overwrite on every channel so no @everyone rule can take away its sight or its voice. Discord does not let a bot change its own role, so one step is yours: this card tells you which one, one button at a time, in the order that keeps the bot working. It follows the server live and turns green by itself when everything matches.

Everything Apply is about to do, grouped by kind: roles to create, categories and channels to create or rename, permissions to set, AutoMod rules, the welcome screen, messages to post. “Up to date” means the server already matches. A few refreshes (the house messages, the forum posts, the category order) run with every Apply; they are routine, not work left to do.

The setup remembers what it created, names included: rename a channel it made and your name stays on every later run; the setup renames only when the blueprint’s own name for that channel changes.

Apply runs the plan and reports every action as done, failed, skipped or “by hand” (the one step Discord reserves for an admin). The page follows the server as the bot works, so you see the categories appear. Run it again any time: a second run over an applied server plans nothing but the routine refreshes.