Advanced Modules Configuration

Tickets setup playbook

Goal

Create a production-ready ticket system with panel, categories, questions, and logging.

Prerequisites

• Bot has required permissions in target channels.
• Admin has role/channel IDs or mentions available.

Step-by-step setup

1. Enable ticket module.
2. Configure base mode and channels.
3. Create panel.
4. Create categories.
5. Add modal questions.
6. Post panel message.
7. Test open/close transcript flow.

!tickets setup
!tickets config mode channel
!tickets config logChannelId <#log_channel_id>
!tickets config transcriptChannelId <#transcript_channel_id>
!tickets config staffRoleIds <@&support_role_id> <@&admin_role_id>
!tickets panel create Main
!tickets panel set 1 title Support Center
!tickets panel set 1 description Choose the right category below
!tickets category add 1 support Support emoji::speech_balloon: support:<@&support_role_id> mention:<@&support_role_id> modal:on
!tickets category add 1 billing Billing emoji::credit_card: support:<@&billing_role_id> mention:<@&billing_role_id> modal:on
!tickets question add 1 "Describe your issue" style:paragraph required:on
!tickets question add 1 "Order ID (if applicable)" style:short required:off
!tickets panel post 1 <#ticket_panel_channel_id>

Verification checklist

• User can open ticket from panel.
• Correct support role is pinged.
• Ticket appears in correct parent/thread location.
• Close action works and transcript goes to transcript channel.
• Logs appear in log channel.

Common failure cases

• Panel posted but buttons inactive due to missing channel permissions.
• Wrong role pinged due to category role mismatch.
• Transcript not generated because close action is disabled or restricted.

Rollback steps

• Disable panel.
• Remove problematic category/question.
• Switch mode back to safe default.

Security setup playbook

Goal

Enable anti-spam, anti-nuke, and baseline raid protection without excessive false positives.

Step-by-step setup

1. Enable security core.
2. Enable anti-spam with moderate defaults.
3. Enable anti-nuke and set punish mode.
4. Configure thresholds.
5. Configure whitelist.
6. Validate using test actions.

!security power on
!security antispam on 6 10 timeout 15 <#mod_log_channel_id>
!security antinuke on
!security antinukepunish timeout 30
!security antinukethreshold ch-create 4 30
!security antinukethreshold ch-delete 3 60
!security antinukethreshold role-create 4 60
!security antinukethreshold perms 2 60
!security raid 6 20 alert
!security whitelist role add <@&trusted_staff_role_id>
!security show

Verification checklist

• Spam burst triggers expected anti-spam action.
• Simulated dangerous changes trigger anti-nuke checks.
• Whitelisted staff are excluded.
• Logs are written to moderation log channel.

Common failure cases

• False positives from strict thresholds on small servers.
• No alerts because log channel is missing or hidden.
• Trusted users punished because whitelist not applied.

Rollback steps

• Lower strictness or temporarily disable specific submodule.
• Revert punish mode from timeout to alert-only when needed.

Leveling setup playbook

Goal

Configure progression that rewards activity without encouraging spam.

Step-by-step setup

1. Enable leveling.
2. Configure xp range and cooldown.
3. Set level-up announcement channel/message.
4. Configure multipliers.
5. Add ignore channels/roles.
6. Add level rewards and achievements.

!leveling enable on
!leveling config xpMin 15
!leveling config xpMax 25
!leveling config cooldownSec 60
!leveling config multiplier 1.0
!leveling config announceLevelUp on
!leveling config levelUpChannelId <#levelup_channel_id>
!leveling multiplier channel <#general_channel_id> 1.2
!leveling multiplier role <@&vip_role_id> 1.5
!leveling ignore channel add <#offtopic_channel_id>
!leveling ignore role add <@&muted_role_id>
!leveling levelrole add 10 <@&level10_role_id>
!leveling levelrole add 20 <@&level20_role_id>
!leveling achievement add first10 level 10 First Steps desc:Reached level 10
!leveling status

Verification checklist

• XP increases at expected pace in allowed channels.
• Ignored channels/roles do not gain XP.
• Level rewards are granted correctly.
• Announcement message appears in the configured channel.

Common failure cases

• XP gains too quickly because cooldown is too low.
• No level role rewards due to role hierarchy ordering.
• Announcements missing from channel permissions.

Rollback steps

• Remove or lower multipliers.
• Remove specific level rewards.
• Disable announcements temporarily.

Module rollout playbook

Goal

Safely launch multiple advanced modules in one server.

Step-by-step setup

1. Security first.
2. Tickets second.
3. Leveling third.
4. Optional advanced modules last.

Verification checklist

• Each stage has a named owner and target date.
• Each module passes verification before next stage starts.
• Rollback commands are documented in mod channel notes.

Common failure cases

• Launching all modules same day without staged verification.
• No dedicated owner per stage.
• Missing rollback notes during incidents.

Rollback steps

Roll back the newest stage first, then reassess logs and thresholds before retrying.