Module configuration
Field-by-field reference for the moderation, logging, tickets, security and server stats configuration pages.
Each configuration page saves through the bot and fails closed when the bot is offline. Field limits below are enforced server-side; the form shows the same bounds.
Moderation#
| Field | Type | Purpose |
|---|---|---|
| Gulag role | role | The role ,gulag assigns and ,forgive removes |
| Gulag log channel | channel | Where gulag/forgive actions are logged |
The same values can be set with ,gulagrole and ,gulagchannelid (Administrator required).
Logging#
| Field | Type | Purpose |
|---|---|---|
| Log channel | text/announcement channel | Destination for every enabled event |
| Event checkboxes | 12 toggles | Which events are logged |
The twelve events: message deleted, message edited, channel created, channel deleted, role created, role deleted, member banned, member unbanned, ticket opened, ticket closed, ticket reopened, moderation action. When a channel is set, an event with no explicit toggle is treated as enabled. Full details in Logging.
Tickets#
Behaviour
| Field | Bounds | Purpose |
|---|---|---|
| Ticket category | channel category | Where ticket channels are created |
| Support roles | max 10 | Roles that can claim and manage tickets |
| Log channel | channel | Panels, transcripts and ticket events are posted here |
| Max open per user | 1–5 | Concurrent ticket limit |
| Ticket name prefix | ≤20 chars | Channel name prefix |
| Naming format | 4 options | number, username, username-number, department-number |
| Allow user close | toggle | Whether creators can close their own tickets |
| Claiming enabled | toggle | Show claim/unclaim controls |
| Transcripts enabled | toggle | Generate a transcript on delete |
Panel appearance
| Field | Bounds | Default |
|---|---|---|
| Title | ≤100 chars | 🎫 Support Ticket |
| Description | ≤2000 chars | Click the button below to open a support ticket. |
| Color | ≤10 chars | #FFFEB6 |
| Button label | ≤80 chars | Open Ticket |
| Button emoji | ≤30 chars | 🎫 |
| Button style | Primary / Secondary / Success / Danger | Primary |
| Thumbnail / Image | ≤500 chars (URL) | empty |
| Footer | ≤200 chars | empty |
Departments (optional, up to 10): each has a label (≤60), short id (≤32), optional emoji, description (≤120), its own category and up to 5 extra support roles. Panels with departments render one button per department — or a select menu when there are more than five.
See Tickets for the runtime flow.
Security#
| Field | Bounds | Default |
|---|---|---|
| Anti-invite | toggle | off |
| Anti-spam enabled | toggle | off |
| Spam threshold | 3–30 messages | 5 |
| Spam window | 2–60 seconds | 5 |
| Spam timeout | 10–86400 seconds | 60 |
| Exempt roles | max 25 | empty |
| Exempt channels | max 25 | empty |
Details and bypass rules: Security.
Server Stats#
Organised in tabs — overview, channels, activity, members, settings.
| Field | Bounds | Default |
|---|---|---|
| Statistic channels | max 20 | — |
| Statistic key | one of 9 keys | — |
| Template | ≤120 chars, must contain {value} | {emoji} {label}: {value} |
| Number format | plain / comma / compact / padded | comma |
| Prefix / suffix / emoji / label | ≤12 / ≤12 / ≤16 / ≤40 chars | empty |
| Activity rules | max 20 | — |
| Activity type | messages / voice minutes / days active | — |
| Activity threshold | 1–1,000,000 | — |
| Activity window | 1–90 days | 30 |
| Update interval | 10–1440 minutes | 10 |
| Track messages / voice | toggles | on |
| Retention | 7–365 days | 90 |
| Ignored channels / roles | id lists | empty |
The nine statistic keys: members, boosts, channels, text channels, voice channels, categories, roles, open tickets, closed tickets. Behaviour details: Server statistics.
Invite Tracker (inside the utility module)#
| Field | Purpose |
|---|---|
| Log channel | Optional join/leave/invite log |
| Fake threshold days | 0–30; joins younger than this count as "fake" (default 3) |
| Track vanity | Whether vanity-URL joins are attributed |
Settings & Permissions pages#
Both are read-only: Settings explains that global bot settings are managed on the main dashboard, and Permissions renders the access rules configured for the server (see Server permissions).