Bring the wiki up to date with the server log (#83)
Server Configuration gains a server log step and /logging status in the
checks; Admin Alerts and Moderation say how they relate to the log;
Verification explains the captcha's button without the outdated intent
claim; Host and Container Installation list the message text question and
the intent reminder; Troubleshooting gains 'The server log posts nothing';
Server Log covers setting message text from the setup script; Home,
Configuration and Admin Dashboard mention it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document the server log (#81), and the Server Members intent every install now needs
New Server Log page. Bot Setup: switching on Server Members Intent, and the
Required invite now includes View Audit Log (1099797982390). Permissions:
the intents table with the two privileged ones, View Audit Log in the
Required set (14), and the server log in By feature and the admin row.
Commands, Configuration (SERVER_LOG_MESSAGE_CONTENT), Feature Switches, Admin
Dashboard (Logging tab), Home, Troubleshooting (Discord refusing the
connection) and both install pages updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Explain setting up the auto-update job that syncs with main
Host Installation's auto-update section now covers what the job does and
doesn't touch, turning it on (including later, by rerunning setup.sh),
what it installs, checking it works and previewing what the next sync
brings, changing the schedule, tracking another branch, and turning it off.
It also corrects the old claim that the branch is set in the crontab entry
too: it's only BRANCH= in the sync script, which Troubleshooting now greps
for. Home and the AWS and Azure pages point at it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add Container Installation, AWS Hosting and Azure Hosting
Covers the container install (deploy/container-setup.sh) and creating an
EC2 instance or Azure VM for either install, for issue 77. Home, Host
Installation, Configuration, Admin Dashboard and Troubleshooting now cover
both installs, and Troubleshooting explains commands showing up without the
bot (an Install Link with only applications.commands).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document the per-server feature switches (/setup feature)
Document the Admin and Mod staff levels
Bring the voice docs up to date across the wiki (#56)
Server Configuration's voice step covers /voice edit, owner controls
and the dashboard's Voice tab. Temporary Voice Channels' troubleshooting
covers controls switched off by admins, the default-limit error, and
hub changes applying to new channels only. Troubleshooting gains a
voice section, and Home's feature row mentions per-hub names and limits.
Permissions page checked (CodeStandards.md § 12): no change needed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document the admin dashboard (#13)
New Admin Dashboard page: what it shows and changes per tab, what stays
in Discord, turning it on with setup.sh or by hand, registering the
OAuth2 redirect URL, opening it locally or over an SSH tunnel, who can
sign in, the four settings, its security model, and troubleshooting.
Configuration lists DASHBOARD_PORT, DISCORD_CLIENT_SECRET,
DASHBOARD_HOST and DASHBOARD_PUBLIC_URL; Host Installation describes
setup.sh's new dashboard step; Home and Troubleshooting link it.
Permissions page checked (CodeStandards.md § 12): the dashboard needs
no bot permission of its own and is open only to the bot's owner, noted
alongside who can run each command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document /mod history, warnings and automatic timeouts (#44)
The Moderation page gains History, Warnings and automatic timeouts, and
Appeal note sections, and its command table and reporting section cover
warn, history, remove-case and config. Commands, Admin Alerts, Server
Configuration and Home match.
Permissions page checked (CodeStandards.md § 12): no change. Warnings
need no permission, and automatic timeouts use Timeout Members, which
/mod already requires.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document RSS feeds (#46)
New RSS Feeds page: adding a feed and its options, finding a site's
feed address, custom messages, what a post looks like and the flood
guard, managing feeds, how checking works, why addresses on private or
local networks are refused, and troubleshooting. Home, Commands (now
16 slash commands), Server Configuration and Troubleshooting cover it.
Permissions page checked (CodeStandards.md § 12): no new permission;
/rss joins the by-feature table, the admin row and the Mention Everyone
footnote.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document /mod moderation (#12)
New Moderation page: every /mod subcommand and option, the right-click
Kick/Ban/Timeout member actions, the safety checks, DMs, temporary bans
and what gets reported. Home, Commands, Server Configuration, Admin
Alerts and Troubleshooting link or describe it, and the Honeypot page no
longer calls itself the only thing that removes anyone.
Permissions page checked (CodeStandards.md § 12): Kick Members and
Timeout Members move into the Required set (now 13), with their
features, and /mod joins the by-feature and who-can-use tables. Bot
Setup's Required invite number is recalculated to 1099797982262; the
Recommended set already held both, so its number is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Give every feature its own page (#40)
Add pages for the features that only had a short Server Configuration
section: Verification, Role Menus, Temporary Voice Channels, Honeypot,
Auto-Delete, Admin Alerts (with the command audit log), Server Roles,
Giveaways and Activity Levels. Each is written from the code: how it
works, setup, every option, limits, and a troubleshooting table, with
the permissions it needs linked to the Permissions page.
Home gains a Features table linking every feature page. Commands and
Server Configuration link each section to its page, and Commands now
counts 14 commands, not 12.
Permissions page checked (CodeStandards.md § 12): it now notes that
the deleted-hub alert's Prune and Restore buttons need Manage Channels.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add a Permissions page, and explain banned words' lists and needs
New Permissions page: the four gateway intents, each required
permission with the features that use it and why, the recommended
extras, what's deliberately left out, a by-feature table, the role
hierarchy, and who can run each command. It was audited against the
code and adds the Auto Moderation Execution intent Bot Setup was
missing.
Bot Setup now summarises the two sets and links there, with a note that
bots invited before /bannedwords need Manage Server added. Banned Words
gains how the lists combine into AutoMod rules and a table of what the
feature needs. Home links the new page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document banned words (#14)
Add a Banned Words page: how it works through Discord AutoMod, setup,
every list (with the shipped lists' contents), custom words and
wildcards, exempting channels and roles, turning it off, and limits.
Bot Setup adds Manage Server to the Required and Recommended sets,
since AutoMod rules need it, and recalculates both invite numbers
(286354484 and 7672240169807095). Also add /bannedwords to Home,
Commands, Server Configuration and Troubleshooting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document Instagram post alerts (#37)
Add an Instagram Alerts page covering the whole host setup: the
professional account and Page link, the Meta app and its permissions,
the business portfolio and System User, generating a token that never
needs renewing, finding the Instagram account ID, and checking it all
works. It records the steps that failed without them during setup
(linking from the Page side, assigning assets before generating the
token, the PowerShell blank-line trap) and why a System User token is
used instead of a Page token.
Also add /instagram to Commands, Server Configuration, Configuration
and Troubleshooting, link it from Home and Streamer Alerts, and note
that /instagram also uses Mention Everyone for unmentionable roles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document Twitch and YouTube streamer alerts (#17)
New Streamer-Alerts page covering the whole feature from PR #28:
- host credentials: registering a Confidential Twitch app; creating a
YouTube Data API v3 key restricted to that API (console or gcloud)
- hom.env values, and that a restart is needed for them to take effect
- server setup: the alert channel and ping role, self-linking through
the streamer role, and admins adding channels directly
- what gets announced and what doesn't (back catalogue, scheduled
streams, finished-stream recordings, lost streamer role)
- managing the list, and how self-links and admin adds interact
- API limits and cost: Twitch effectively unlimited; the YouTube
10,000-unit daily quota with rough usage by channel count
- known gaps: long-running YouTube streams can be missed, Shorts are
announced, and live and upload alerts share one channel
- testing with high-volume news channels and a public stream on your own
channel
Also:
- Home: description and page table
- Configuration: the three new variables, and the note that hom.env is
only read at startup
- Commands: now 12 commands, the /streamers reference, and
streamer-role's new purpose
- Server-Configuration: a new step 7 for streamer alerts, and
/streamers list in the verification checklist
- Troubleshooting: "Stream or upload alerts don't post", most common
cause first
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add setup wiki: bot setup, host install, configuration, server config, commands, troubleshooting