GUIDE · MODERATION

Discord Moderation Bot Setup: Warnings, Timeouts and Staff Permissions

Consistent moderation needs an agreed escalation path: when a warning is enough, when to time out, and when to ban — plus roles and filters that make the right action easy. Below is a setup your whole team can follow, using ARK Bot commands configured from /settings.

By ArkFlame · Published 2026-10-13 · 3 min read

Warn vs timeout vs ban

Use /warn with a clear reason for first or minor issues — it records history without removing the member. Use /timeout to pause an actively disruptive member for minutes or hours. Use /banfor serious or repeated harm. Review a member's record with /warnings before escalating, and use /clear to remove bursts of unwanted messages after acting.

Position the bot role correctly

Discord blocks moderation actions against members whose highest role sits above the bot's highest role. Place the ARK Bot role above the moderator and member roles (but below owner-held admin roles) in Server Settings → Roles. After moving it, run /setup-check to confirm what the bot can currently see and do.

Set up moderator roles

Create one moderator staff role with Timeout Members, Kick Members, Ban Members, and Manage Messages. Assign it in /settings as the staff role so only holders can run moderation commands. Keep a separate senior staff role for appeals and reports about moderators, mirroring the ticket setup.

Scope the link filter

Enable anti-link rules in /settings for channels where newcomers post, and leave them off (or exempt trusted roles) in resource and announcement channels where legitimate links belong. Pair it with the honeypot channel so automated posters reveal themselves without punishing real members.

Review recent warnings

Run /warnings on a member before deciding. Two recent warnings for the same behavior should escalate to a timeout; warnings older than your policy window (for example 30–90 days) should weigh less. Write reasons your future self can audit: what rule, what evidence, what next step.

Avoid accidental punishments

Confirm the target handle — similar names cause most wrong-user bans.
Check hierarchy first: timeouts fail silently against higher roles.
Prefer timeout over ban when unsure; bans are harder to undo socially.
Never moderate a report about yourself; hand it to senior staff.

Test with a limited-permission account

Keep a second account holding only the member role. Warn it, time it out, and confirm the messages and permissions look right from the receiving side. Also confirm the test account cannot run /warn or /ban — unauthorized use should be rejected.

FAQs

Why did a timeout fail on one member but work on another?

Role hierarchy. Discord blocks moderation against anyone whose highest role sits above the bot's highest role. Move the ARK Bot role higher in Server Settings → Roles and run /setup-check to confirm.

Should link filters apply server-wide?

No. Scope anti-link rules to channels where newcomers post and exempt trusted roles and resource channels. A filter that blocks legitimate guides trains members to work around it.

How long should warnings count against a member?

Set a policy window (30–90 days is common) and document it. Recent repeats escalate to timeout; stale warnings stay visible for context but should weigh less in the decision.

Conclusion

Agree the warn → timeout → ban path, set the staff role and hierarchy in /settings, scope link rules, and test as a member. Consistency is what members experience as fairness.