discord-server

Everything for Lorenzo's Server in one place:

1. Client theme: the Field Notebook look, matching lscaturchio.xyz. Night or paper ground, forest-green ink, Fraunces headings and IBM Plex Mono wall labels.
2. Server setup (server/): roles, channels, Onboarding and AutoMod as code.
3. Front Desk (bot/): the server's own bot, with squad-up, stats and more.

Roadmap and design: docs/superpowers/specs/2026-10-01-front-desk-bot-design.md.

1. Client theme (theme/field-notebook.theme.css)

Works with Vencord (recommended) or BetterDiscord.

• Vencord: Settings → Vencord → Themes → Open Themes Folder, drop the file in, then toggle it on.
• BetterDiscord: Settings → Themes → Open Themes Folder, drop the file in, then toggle it on.

Discord's own Appearance setting picks the variant: Dark, Darker or Midnight gives the night notebook, and Light gives the paper one.

Heads up: both mods break Discord's Terms of Service. Bans for themes alone are very rare, but it's your call. Discord renames its internal classes every few months. If a detail stops applying (for example the mono category labels), the colours and fonts still work because they're driven by CSS variables.

2. Server makeover (server/)

This is a one-shot bot run. It creates or renames roles, categories and channels, makes the front-desk channels read-only, sets the join-message and AFK channels, and posts rules and welcome embeds. It never deletes anything. Anything not in layout.py gets listed so you can clean it up by hand.

One-time setup

1. Go to https://discord.com/developers/applications → New Application → Bot → Reset Token, and copy the token.
2. Copy .env.example to .env and paste the token and your server ID into it.
3. Invite the bot with Administrator (replace APP_ID with the Application ID from the General Information page): https://discord.com/oauth2/authorize?client_id=APP_ID&scope=bot&permissions=8
4. Server Settings → Roles: drag the bot's role to the very top.

Run it

cd server
python -m venv .venv
.venv\Scripts\pip install -r requirements.txt
.venv\Scripts\python setup_server.py          # dry run: shows the plan
.venv\Scripts\python setup_server.py --apply  # do it

Edit layout.py first. GAMES at the top holds your group's actual games, and each one gets a ping role plus a channel. RETIRED_GAMES under it holds games the server used to list: their roles stay, they are no longer offered, and public_mode.py archives their channels. The script is safe to re-run: it matches existing channels and roles by plain name, so #general becomes #💬・general instead of a duplicate.

Second pass: Discord's built-in features

.venv\Scripts\python polish_server.py          # dry run
.venv\Scripts\python polish_server.py --apply

This turns on Community and Onboarding, so new members pick their own game roles on join. It also sets up AutoMod (spam, mention raids and slurs, with alerts to the mod channel), defaults notifications to @mentions only, and removes the empty channels listed in TRIM. Everything is configured at the bottom of layout.py. The bot's role must be at the top for Onboarding to assign roles.

The server icon comes from assets/make_icon.py (pip install pillow).

Hosted bots (always online, set up in their dashboards)

MEE6 was tried and dropped: its Levels and Welcome plugins now need Premium.

polish_server.py also handles the media lock: @everyone can't post images, files or link embeds until they have one of the MEDIA_ROLES (Captcha.bot's @Verified covers new members). The lock is off for now (layout.MEDIA_LOCK = False, captcha paused since 2026-10-28), so polish_server.py gives @everyone media instead; set it back to True when Captcha.bot returns. The bot roles are ordered by the keep entries in layout.ROLES, and every bot gets @Bots so they're grouped in the member list.

Afterwards

• Give yourself @Keeper and your friends @Squad.
• Take Administrator back off the bot's role. Front Desk now stays as the server's permanent bot (section 3) with only the permissions it needs.
• For later changes use public_mode.py: it never reorders or deletes, so it works with Front Desk sitting below the staff roles. It adds what is missing, with one exception: a game in RETIRED_GAMES leaves the "What do you play?" question and its channel moves into the staff-only 99 · archive category (messages and the role are kept; the dry run lists every channel it would hide).
• To give newcomers a short channel list, run focus_mode.py (--plan prints the plan from layout.py alone, no arguments is a dry run against the server, then --apply). The Onboarding default channels become the nine in ONBOARDING_DEFAULT_CHANNELS, and the other public channels become answers to one optional question, "What else do you want to see?". No permission changes and nothing is deleted: every channel stays open to @everyone and current members keep the list they have. --revert makes every channel a default again.
• Reset the bot token in the portal if you shared .env anywhere.
• Optional: set ICON_PATH in layout.py to a square image for the server icon.

Emoji & sounds

The server has its own emoji pack (20 emoji, such as :gg:, :take_w:, :clutch:, :touchgrass: and :frontdesk:) and 8 soundboard sounds. Code generates all of them from scratch: Pillow draws the emoji and numpy synthesizes the sounds. No samples or outside art are used. The emoji share the look of the server icon: a night-paper stamp with one mark in one ink (pen green for wins and hype, near-white for neutral words, muted for losses), drawn to read at 22 to 48 px on both Discord themes. assets/expressions/contact-sheet.png shows the whole set at those sizes. The lettering is set in Bahnschrift Bold, so make_emoji.py needs Windows 10 or 11; the font itself is not in this repo.

.venv\Scripts\pip install pillow numpy                     # ffmpeg must be on PATH for the MP3s
.venv\Scripts\python ..\assets\expressions\make_emoji.py   # -> assets/expressions/emoji/*.png
.venv\Scripts\python ..\assets\expressions\make_sounds.py  # -> assets/expressions/sounds/*.mp3
.venv\Scripts\python expressions.py                        # dry run: what fits in your slots
.venv\Scripts\python expressions.py --apply                # upload
.venv\Scripts\python expressions.py --replace              # dry run: which emoji have new art
.venv\Scripts\python expressions.py --replace --apply      # swap them, one at a time

The bot's role needs Create Expressions. Names that already exist are skipped, and anything over the emoji or soundboard slot limit (8 sounds unboosted) is listed rather than uploaded. Sounds are MP3 because discord.py only accepts MP3 for the soundboard.

--replace is for emoji that were redrawn. Discord cannot change an emoji's picture, so each emoji whose local art differs from the server's is uploaded again under the same name and the old one is deleted (upload first when a slot is free; --delete-first turns that round). The emoji gets a new ID: typing :name: shows the new art, but messages and reactions that already used the old one do not change. It needs Manage Expressions as well, unless the bot uploaded every emoji it deletes. A touch-up too small for the comparison to notice can be named with --force NAME. Nothing in the bot refers to these emoji, by name or by ID.

Snapshot

snapshot_server.py is read-only. It writes the live server's config to server/snapshot/ (server, roles, channels, onboarding, automod and welcome .json). It uses names, not IDs, and sorts its output, so git diff server/snapshot shows exactly what changed since the last snapshot you committed. It never records members, messages, invites or the token.

cd server
.venv/Scripts/python snapshot_server.py            # write the snapshot
.venv/Scripts/python snapshot_server.py --compare  # also list roles/channels that differ from layout.py
.venv/Scripts/python -m pytest tests               # unit tests

If the bot lacks a permission for a fetch (AutoMod rules need Manage Server), that file gets an "error" note instead and the rest is still written.

3. Front Desk bot (bot/)

Front Desk is the server's own bot. It runs on LORENZO-COMPUTE around the clock and needs no day-to-day attention. Design and history: docs/superpowers/specs/2026-10-01-front-desk-bot-design.md. Privacy: PRIVACY.md.

What it does