How to automate warning escalation with GuildPilot

The /warn command adds active points to a member, and the dashboard can map point thresholds to automated moderation. You control the default points, warning lifetime and whether a threshold produces a temporary mute, temporary ban or permanent ban.

Moderation - Warning actionsReal dashboard

Before you start

• Configure /warn and /warnclear in Moderation.
• Staff need Manage Messages to use the warning commands.
• GuildPilot needs the Discord permissions required by every automated action you configure.

Warning: A threshold can automatically timeout or ban a real member as soon as their active points reach it. Test thresholds with a designated account and keep the bot below no role it needs to moderate.

Automate warning escalation

1. Open the warn settings

Open Moderation and select /warn.

2. Set the point and lifetime defaults

Under Warning points, set Default warn points. Configure Warn lifetime months and Warn lifetime days so old warning points stop being active after the intended period.

3. Add an automated action

Under Automated actions, select New action. Choose the point threshold under On warning points, then choose the Action.

4. Configure a temporary duration

For a temporary mute or temporary ban, enter Duration amount and Duration unit. A permanent ban does not need a duration; the editor marks that field as optional for permanent bans.

5. Save and order the policy

Save /warn. Review all thresholds as one policy so increasing point totals lead to intentional outcomes rather than duplicate or contradictory actions.

Recommended configuration

Start with a low-severity reversible action and reserve permanent bans for a clearly higher threshold. Align warning lifetime with your written moderation policy so staff and members understand when points expire.

Test the setup

1. Use a designated test member and a moderator with Manage Messages.
2. Run /warn user:@TestMember reason:Escalation test points:1 enough times to reach a low reversible threshold.
3. Confirm the automated timeout or other expected action and the private moderation log.
4. Run /warnclear user:@TestMember reason:Test complete, then undo any remaining timeout or ban.

What a successful setup looks like

Active points increase after /warn, expired points no longer count, and reaching a saved threshold produces the configured action once the bot can apply it.

Common problems

The automated action does not run

Cause: The active point total did not reach the saved threshold or the bot lacks the action's Discord permission.

Fix: Check the points supplied to /warn, the warning lifetime and the bot's timeout or ban permission.

A temporary action has no usable duration

Cause: Duration amount or Duration unit is missing for an action that requires both.

Fix: Edit the automated action and provide a positive duration with its unit.

Old points still affect the member

Cause: They have not passed the configured warning lifetime.

Fix: Review the saved month and day values, or use /warnclear when your moderation policy authorises an immediate reset.