Blueprint
editable · live▾ WELCOME
# rules
# welcome
The editable document describing your server — roles, channels, categories, onboarding.
Your workbench. The living spec you edit, share between servers, and apply to make changes go live.
About Packet
Build the Discord server you actually want.
Packet is a bot that helps anyone build and run a sophisticated Discord server — from a small friend group to a busy live community. Instead of clicking through Discord Server Settings to add roles, rename channels, or set up onboarding, Packet lets you describe your Discord server’s desired shape in a blueprint— and applies the changes in one go.
01 The big idea
Stop clicking. Start describing.
Every role, channel, category, and onboarding step lives in one editable document. You edit it; Packet builds the live server to match.
⚙Roles›
⚙Channels›
⚙Permissions›
⚙Onboarding›
⚙Emoji›
⚙Integrations›
Click through every menu, one at a time.Describe the shape once instead ↓
01~👋 WELCOME
02+# rules
03+# welcome
04+# announcements
05~💬 COMMONS
06+# general-chat
07+# off-topic
08+@Owner @Admin @Helper
apply ▶
◆ Your Server ● live
▾WELCOME
#rules
#welcome
#announcements
▾COMMONS
#general-chat
#off-topic
02 Three things to know
Blueprint, Snapshot, Template
Blueprints are what you author and apply. Snapshots are automatic backups. Templates are good starting points that don’t get edited in place.
Snapshot
read-only · frozen▾ WELCOME
# rules
# welcome
▾ COMMONS
# general-chat
08:32 PM · Jun 5
🔒
A frozen, read-only copy of how your server looked at a moment in time.
Insurance. Every apply takes one first — if something looks wrong afterwards, restore the snapshot.
Template
read-only · reusable▾ WELCOME
# rules
# welcome
▾ COMMONS
# general-chat
→ new blueprint
A frozen, saved shape meant to be reused as a starting point.
Keep one per season or event — a holiday look, a tournament setup — and reopen it as a fresh blueprint whenever that time comes around.
03 How content moves
One loop connects all three
Use a template to fill a blueprint, apply it to your live server, and Packet snapshots first. Snapshots can become blueprints again.
The whole flow in one line: Template → Blueprint → Live server → Snapshot. Blueprints are what you author and apply. Snapshots are automatic backups. Templates are good starting points that don’t get edited in place.
04 Safe by default
Nothing happens until you click Apply
Every apply shows a full diff, takes an automatic snapshot, then streams each change live. If anything looks wrong, restore the snapshot.
~$ reviewing the plan…
Packet only touches your server when you click Apply — and takes a snapshot first.
01Diff✓
preview the plan
+ add 3 channels
~ rename 1 category
− remove 1 role
Nothing has touched your server yet.
02Snapshot✓
auto-taken first
📷08:32 PM · Jun 5backup saved
Your safety net, saved automatically.
03Apply✓
streams live
[OK] create #rules
[OK] rename WELCOME
····· reorder roles
Watch every change as it runs.
04Restore↺
if it looks wrong
↺ Restore snapshot
rolls back to 02
One click back to the snapshot.
05 Getting started
From invite to first apply, in six steps
The whole on-ramp. Step two trips up most people on their first run, so it’s worth doing carefully.
1
Invite the bot
From the Servers page, add Packet to your server. The invite link grants Administrator by default — exactly what it needs.
2
⚠ most common first-time snag
Raise Packet’s role to the top
Discord won’t let a bot change any role above its own. In Server Settings → Roles, drag the Packet role above every role your blueprint touches — the very top is the safe default.
3
Open a “Ready” server
A green Ready badge means Packet can see and edit the server. Click it to drop into the blueprint editor.
4
Get a starting blueprint
Four equally good ways to begin — pick whichever fits:
✦ Generate with AI⇣ Pull current server◈ Start from a Template✎ Write from scratch
5
Diff before you apply
The Diff tab lists exactly what would change — every role, channel, and permission. Nothing has touched your server yet.
✓
Apply
Packet snapshots your server first, makes the changes, and streams progress live. If it looks wrong afterwards, restore the snapshot. That’s the whole loop.
＋ The complete reference
~$ packet · loading about…