Auto-kick/ban
Key features
Join and role-change screening
Nox evaluates enabled rules when a non-bot member joins and when trap roles are newly added to a non-bot member.
Risk-signal conditions
Rules can match account age, default avatar state, and configured trap roles, with any/all matching for both rule conditions and trap-role conditions.
Kick or ban actions
Each rule chooses a kick or ban action. Ban rules use Discord ban behaviour without deleting the member's prior messages.
Error-only failure reporting
Successful actions happen silently from this feature path. If Discord rejects a kick or ban, Nox records an Errors page entry for admins to investigate.
Best for
Slowing raids or disposable-account joins before they can settle in.
Enforcing trap-role onboarding patterns where selecting a role is a risk signal.
Communities that prefer named, ordered screening rules over manual join checks.
How it works
Admins define ordered rules
Staff create named rules with priority, enabled state, action, condition mode, trap-role match mode, account-age limits, default-avatar matching, and trap roles.
Nox evaluates join and role events
On member join or role update, the bot reads the saved rules and evaluates non-bot members against enabled rules.
The first matching action runs
When a rule matches, Nox sends Discord the configured kick or ban with a deterministic moderation reason.
Failures are recorded
If Discord denies the action because of permissions, role hierarchy, or a temporary Discord error, the member remains and Nox records the failure on the Errors page.
Setup checklist
Place Nox's role high enough to kick or ban the members your rules may target.
Grant Kick Members for kick rules and Ban Members for ban rules.
Keep priorities unique enough for staff to understand which rule should win.
Add trap roles only when role assignment is a deliberate screening signal.
Review the Errors page after enabling a new rule to catch permission or hierarchy failures quickly.
Important notes
Auto Kick/Ban has no slash commands, buttons, modals, select menus, DMs, or scheduled jobs. The dashboard only saves rules.
The dashboard never kicks or bans anyone directly. Actions only run from bot join and role-update events handled by the bot.
Trap-role matching on role updates only considers roles newly added in that update.
Completed kicks or bans are not rolled back by Nox cleanup paths.
Failed moderation actions are not automatically retried. Staff should handle the member manually after fixing permissions or hierarchy.
Troubleshooting
A matching member was not kicked or banned
Check the rule is enabled, the member is not a bot, the account-age/default avatar/trap-role conditions actually match, and the event was a join or a newly-added trap role.
Discord denied the action
Confirm Nox has Kick Members or Ban Members and that its role is above the target member. Failed actions are recorded on the Errors page but are not retried.
A trap-role rule did not fire
Verify the role is listed as a trap role and was newly added in that update. Existing roles from before the event are not treated as newly selected trap roles.
Permissions
Discord permissions Nox needs for this feature and what each permission is used for.
