Rule Enforcement Settings
ProRule Enforcement Settings is your guild-wide policy configuration. Set strike thresholds, warning-to-strike conversion rules, expiry windows, DM notifications, and per-category severity policies. Arkanis uses these settings to evaluate every enforcement event.
Open Rule Enforcement Settings →
Arkanis's policy brain. Strike thresholds, warning conversion, expiry windows, and DM notifications all live here. Every enforcement event runs through these settings.
What is this?
One settings page where you describe your enforcement policy once, and Arkanis applies it automatically. Set how many strikes triggers a ban, how warnings convert to strikes, when strikes expire, and which categories are Minor vs Major. Four one-click presets (Standard, Strict, Zero Tolerance, Test Mode) cover most servers without manual tuning.
Why you might want it
You describe the threshold once and the bot does the action chain. Three rules cover most servers. If you want "3 Major strikes equals a ban", you set that here and it applies forever; you don't need to remember to count strikes during a busy night. Start with the Standard preset and tune one field at a time as your policy evolves.
How Rule Enforcement Settings Work
Rule Enforcement Settings is one settings page that governs your entire guild's automated moderation behavior. Every time a strike, warning, or mute is issued, Arkanis evaluates the player against these settings and takes the configured action (alert a moderator, auto-ban, auto-convert warnings, and so on).
The page is organised into three blocks:
- Core Settings: auto-ban mode, thresholds, conversion ratios, expiry, and DM notifications.
- Strike Category Policy: default severity per category (Minor or Major).
- Policy Presets: one-click bundles (Standard, Strict, Zero Tolerance, or Test Mode).
Opening the Settings Page
Go to the Dashboard
Sign in to the dashboard and select your server.
Navigate to Rule Enforcement Settings
From the sidebar, click Rule Enforcement Settings. The page loads with your current configuration and a presets strip at the top.
Policy Presets
Presets give you a sensible starting point. Each preset pre-fills every setting on the page; you can still adjust individual fields afterwards. Arkanis ships with four presets:
Default enforcement: automatic bans at threshold with balanced expiry. Strike threshold 5, 30-day strike expiry, 14-day warning expiry, 180-day appeal cooldown. Warnings convert to strikes after 2 same-category or 3 total. A good baseline for most servers.
Automatic bans with longer memory: strikes and warnings stick around. Strike threshold 3, 90-day strike expiry, 45-day warning expiry, 90-day appeal cooldown. Warnings convert after 2 same-category or 2 total. Suits competitive or high-moderation communities where repeat behaviour needs to stay on record.
One chance: a single major strike or two minors and you're banned. Strike threshold 2, 365-day strike expiry, 30-day warning expiry, 0-day appeal cooldown. Warnings convert after 2 same-category or 2 total. Designed for communities that enforce a hard-line policy with minimal leniency.
AutoMod and Auto-Ban in log/alert mode: safe for testing rules without real enforcement. Auto-ban runs in Alert mode (no automatic bans), strike threshold 3, 30-day strike expiry, 14-day warning expiry, 180-day appeal cooldown. Ideal when piloting Arkanis on a live server before flipping to Automatic.
Pick a Preset
Click a preset card at the top of the page. Arkanis fills every field with that preset's values and shows a diff before saving.
Confirm
Review the changes and click Apply Preset. The new values save and take effect on the next enforcement event.
Core Settings
These settings control the heart of the rules engine. Each field saves independently when you blur the input, with a toast confirming the change.
Auto-Ban Mode
Choose how Arkanis handles an offender who crosses the strike threshold:
- Alert: the system posts a moderator alert and waits for staff to manually ban.
- Automatic: the system issues the ban itself (and executes it via RCON if configured).
Auto-Ban Enabled
A toggle that turns auto-ban on or off globally. When off, the threshold still tracks but nothing is triggered.
Strike Threshold
Set the points that trigger an auto-ban, from 1 to 20. Minor strikes = 1 point, Major strikes = 2 points. For example, a threshold of 4 triggers after four Minor strikes or two Major strikes.
Warning → Strike (Same Category)
Set how many same-category warnings auto-convert into one Minor strike. Range 2 to 10. Example: 3 toxicity warnings become 1 Minor toxicity strike.
Warning → Strike (Any Category)
Set how many warnings of any category auto-convert into one Minor strike. Range 2 to 20. This captures players who spread warnings across many categories.
DM Notifications
Toggle whether Arkanis DMs the player when a strike, ban, warning, or mute is issued. DMs include the reason and (for strikes/bans) the reference ID so players can appeal.
Strike Expiry
Set the number of days before strikes expire (range 1 to 365). Expiry is staggered per strike count: the more strikes a player has, the longer their oldest strikes persist before expiring.
Warning Expiry
Set the number of days before warnings expire. Range 0 to 365, where 0 = never expire.
Appeal Cooldown
Set the number of days a banned player must wait before they can submit another appeal. Range 0 to 365.
Strike Category Policy
This table sets the default severity for each category. When a moderator adds a strike, Arkanis pre-selects this severity. Moderators can override per strike, but the default shapes the typical outcome.
Locate the Category Table
Scroll to Strike Category Policy. Each row lists a category and a severity selector (Minor or Major).
Pick a Severity Per Category
Use the selector on each row to set the default. Common policy:
- Cheating, Hate Speech: Major by default.
- Harassment: Major for direct harassment, Minor for borderline cases.
- Griefing, Toxicity, Other: Minor by default.
Save
Changes save per row. A toast confirms each update. The new default applies to strikes added from this point forward; existing strikes keep their original severity.
Threshold Re-evaluation
Lowering the strike threshold, or tightening any auto-convert setting, can retroactively put existing players over the line. Arkanis handles this in two modes:
- Alert mode: Arkanis generates a moderator alert listing every player who now exceeds the threshold. Staff review the list and manually ban the offenders.
- Automatic mode: Arkanis issues bans directly for every player who now exceeds the threshold. A batch summary is posted in the audit channel.
Practical Tips
- Start with Standard. The Standard preset is the balanced default. Tighten to Strict or Zero Tolerance as you learn your community's patterns.
- Pilot with Test Mode. Test Mode runs AutoMod and Auto-Ban in alert-only mode, so you can see what would have happened without actually banning anyone. Switch to Standard (or another automatic preset) once you're confident.
- Alert before Automatic. If you're customising, run Alert mode for a few weeks before switching to Automatic. You'll see whether the threshold is calibrated correctly without risking false auto-bans.
- Stagger expiry. Short expiry encourages reform, but very short (under 30 days) can let repeat offenders slip through. 30 to 90 days works for most servers.
- Document your policy. Keep your chosen preset and any overrides in a pinned channel or shared doc so your moderation team stays consistent.