Common Setup Mistakes
Most first-week NexaBot issues aren't bugs — they're a handful of the same few mistakes almost every new server makes. Here's what to watch for.
Inviting the bot but not moving its role
By far the most common one: NexaBot gets invited, the wizard runs, and then moderation commands quietly fail on some members. Almost always, this means NexaBot's role is sitting too low in the role list. It can only act on members whose highest role is below its own — see Permissions Troubleshooting for the full explanation.
Fix: move NexaBot's role near the top of your hierarchy right after inviting it, before configuring anything else.
Turning on strict anti-raid or anti-nuke before testing
Setting anti-raid or anti-nuke thresholds too aggressively on day one can flag totally normal activity — a partner server's welcome raid, a genuinely busy launch day. Start with conservative thresholds and tighten them based on what you actually observe, rather than guessing worst-case on day one.
Warning
If anti-nuke or anti-raid ever takes an action you didn't expect, check Moderation & Security for what each threshold actually tracks before assuming it's a false alarm.
Skipping verification, then getting raided
It's tempting to skip verification for a small, friendly server — but smaller servers are often easier targets, not harder ones. Setting up even the lightest verification style takes a minute and meaningfully cuts down on low-effort bot joins. See Verification System.
Not setting a mod-log channel
Without a mod-log channel configured, moderation actions still happen but you lose visibility into them as they occur — you'd only find out by manually checking case history later. Setting this up during the setup wizard takes seconds and saves a lot of "wait, when did that happen?" moments later.
Deleting a channel or role that's still referenced
If your mod-log channel, verification role, or a level-reward role gets deleted during a cleanup, the feature tied to it silently stops working instead of erroring loudly. See Backup & Recovery for what to check before a big restructure.
Assuming a slash command failing silently means it's broken
If a command doesn't respond, it's rarely NexaBot itself — it's almost always a missing permission or a role hierarchy issue. Before assuming something's broken, check Permissions Troubleshooting first.