Everything your server needs, in one bot.

By default, commands like /antinuke, /automod setup, and /security checkup are restricted to the server owner. Co-owners let you delegate that access to trusted admins without giving them server ownership on Discord itself.

1. Make sure the person you want to add as a co-owner already has a role with the Administrator permission — Nexus requires this before they can be added.
2. Add them: /manage co-owners add @user. They will immediately gain access to all owner-level bot commands.
3. View the current co-owner list at any time: /manage co-owners view.
4. To revoke access: /manage co-owners remove @user.

Moderation commands are available immediately after adding Nexus — no setup needed. They require the matching Discord permission (e.g. Kick Members to use /kick).

1. Use /warn @user [reason] to issue a warning. Warnings are stored permanently.
2. Use /warnings @user to review a member's warning history at any time.
3. Use /clearwarnings @user to wipe a member's record if needed.
4. Use /purge [number] to bulk-delete messages (up to 100 at a time).
5. Use /timeout @user [duration] to mute a member temporarily. Duration examples: 10m, 1h, 7d.
6. Use /softban @user to clear a user's recent messages without a permanent ban.

Anti-Nuke watches for message floods and mention spam in real time and automatically times out offenders. Only the server owner can configure this.

1. Run /antinuke enable to switch on protection.
2. Set the message flood threshold: /antinuke config msg-threshold (how many messages) and /antinuke config msg-window (within how many seconds). Example: 10 messages in 5 seconds.
3. Set the mention flood threshold: /antinuke config mention-threshold and /antinuke config mention-window. Example: 5 mentions in 10 seconds.
4. Set how long offenders are timed out: /antinuke config timeout-duration (seconds). Example: 600 = 10 minutes.
5. Optional — enable bot-join protection: /antinuke config botjoin and set it to enabled. Any bot that joins without being pre-authorized will be auto-kicked.
6. Verify the configuration with /antinuke status.

Auto-Mod uses Discord's built-in AutoMod API. Nexus creates and manages the rules for you. Only the server owner can run these commands.

1. Run /automod setup to create the standard rule set: profanity filter, spam detection, and mention spam detection.
2. Add custom banned words: /automod addword [word]. Repeat for each word you want blocked.
3. Exempt a safe channel (e.g. #staff) from a rule: /automod whitelist add-channel [channel] [rule].
4. Exempt a trusted user: /automod whitelist add-user @user [rule].
5. Toggle any rule on or off without deleting it: /automod toggle [rule].
6. Check the current state at any time: /automod status.

Members automatically earn XP just by chatting. Nexus handles everything in the background once you enable the system.

1. Enable the system: /toggle-leveling.
2. Set a channel for level-up announcements: /set-level-channel #channel. If you skip this, level-ups are announced in the channel where the member was chatting.
3. Create role rewards: /create-level-role [level] @role. Members automatically receive the role when they hit that level.
4. Members can check their rank with /rank and view the leaderboard with /leaderboard.

The economy system gives your server its own virtual currency with daily rewards and gambling games. Currency has no real-world value.

1. Enable the economy: /economy enable.
2. Customize the currency name and symbol: /set-currency [name] [symbol]. Example: /set-currency Coins 🪙.
3. Members can claim free currency with /daily (once per 24 h) and /hourly (once per hour).
4. Members can gamble with /gamble — choose from dice, coinflip, slots, or blackjack.
5. Members can transfer currency to each other with /transfer @user [amount].
6. View the richest members with /leaderboard-money.

Bot Log keeps a record of every action Nexus takes — moderation commands, anti-nuke triggers, and AutoMod changes — in a dedicated channel. This is separate from Discord's built-in audit log and the server event logging system.

1. Create a private channel for the audit trail (e.g. #bot-log), visible only to server staff.
2. Set the log channel: /botlog channel #bot-log.
3. Enable logging: /botlog enabled True.
4. From now on, every kick, ban, timeout, purge, warn, AutoMod change, and anti-nuke action will be logged to that channel automatically.
5. Check the current configuration at any time: /botlog status.
6. To pause logging without losing the channel setting: /botlog enabled False.

Logging sends formatted audit messages to a dedicated channel whenever selected events happen on the server.

1. Create a private #logs channel visible only to staff, then run /log channel #logs.
2. Enable logging: /log manage setup.
3. Check available event types: /log events-list.
4. Add the events you want: /log events add [event]. Common choices: message_delete, message_edit, member_join, member_leave, ban, kick, timeout.
5. Exclude noisy channels or bots: /log ignore-channel #channel or /log ignore-user @user.
6. Verify the setup: /log test.

When a new member joins, Nexus can automatically post a welcome message in a channel of your choice.

1. Run /welcome-config and follow the prompts to set your welcome channel and message text.
2. Test how it looks without waiting for someone to join: /test-welcome.

Nexus can post a message in a channel every time someone joins the server, and track which invite link they used to get there.

1. Create a channel for join announcements (e.g. #joins), then run /set-join-channel #channel.
2. To enable or disable invite tracking (who invited whom): /invites-config enabled:True or /invites-config enabled:False.
3. To see who invited a specific member and which link they used: /inviter @user.
4. To view a leaderboard of who has invited the most members: /invites.

Members take turns counting up from 1 in a dedicated channel. If someone sends the wrong number, the count resets.

1. Create a channel (e.g. #counting) and run /counting setup #channel.
2. Optional — set custom reaction emojis for correct/incorrect counts: /counting reactions.
3. Optional — customize the counting rules with /counting config. You must set all three toggles each time: allow_chat, enable_maths, and enable_saves. Example: /counting config allow_chat:False enable_maths:True enable_saves:True.
4. allow_chat — when True, members can send regular messages in the counting channel without them being deleted.
5. enable_maths — when True, members can count using math expressions like 2+2 or 3*4 (PEMDAS rules apply).
6. enable_saves — when False, a wrong number resets the game to 1 and announces it in the channel. When True, the count is preserved after a mistake.
7. Optional — assign a role to anyone who counts wrong by adding map_fail_role:@role. Remove it later with unmap_fail_role:True.
8. Optional — players can earn saves to protect against wrong counts by running /counting earn. A random mini-game is presented (color sequence, jumbled word, or trivia). With enable_saves:False, a player who has a save will automatically use it when they count wrong — the count is preserved and the channel is notified.
9. View stats at any time: /counting stats.

Give your members a structured way to send suggestions and reports directly through Nexus.

1. Set up a private staff-only #suggestions channel, then run /set-suggestion-channel #channel.
2. Set up a private #reports channel and run /set-report-channel #channel.
3. Members can now use /suggest [idea] and /report [description] — their submissions appear in the respective channels.

Nexus can snapshot your server's roles and channels so you can restore them quickly after an accident or a nuke attack.

1. Create a backup: /backup create [name]. Give it a descriptive name like before-restructure.
2. To see all saved backups: /backup list.
3. To inspect what's inside a backup before restoring: /backup info [name].
4. To restore: /backup restore [name]. This is a destructive operation — existing roles and channels will be overwritten or removed as part of the restore process. Make sure you want to fully revert before running this.
5. To delete an old backup: /backup delete [name].

The security checkup scans your server and flags potential risks — no setup required, just run it whenever you want.

1. Run /security checkup. Nexus will scan your roles, permissions, bots, and Anti-Nuke settings.
2. Review the results — the report will flag roles with dangerous permissions (e.g. Administrator, Manage Server) and highlight any bots with elevated access.
3. Address any flagged issues — reduce role permissions where possible and enable Anti-Nuke if it isn't already.

Image commands require no setup — they're ready to use the moment Nexus joins your server.

1. Run any image command with an optional @user argument to target someone else's avatar.
2. Examples: /pet @user, /wanted @user, /achievement [text], /pixel @user, /trash @user.