Skip to main content

⚠️ Warns

The warning system gives admins a graduated response between "ignore it" and "ban them". Admins issue warnings with /warn; when a member collects enough of them, the agent automatically applies the action you've configured — a timeout, kick, or ban.

Overview​

  • Admins warn members with the /warn command in Discord
  • Every warn is delivered to the member as a DM, so nothing happens silently
  • After a configurable number of warns, the agent mutes, kicks, or bans automatically
  • A Recent Warns list in the webapp shows the latest warnings at a glance

Configuration​

To configure warnings:

  1. Open your project in the Fren One webapp.
  2. Select the Discord server you want to configure.
  3. In the sidebar under Agent Configuration, select Moderation, then the Warns tab.
  4. Toggle "Allow admins to warn members with "/warn"" on.

Warn limit and action​

OptionDescription
Warn LimitAction is taken after this many warns. Minimum 1; default 3.
Action on LimitWhat happens at the limit: Mute (timeout) (default), Kick, or Ban.
Mute durationShown when the action is Mute. How long the timeout lasts — Discord allows up to 28 days. Default: 5 days. Required.

Recent Warns​

Below the settings, a read-only Recent Warns list shows the latest warnings (up to 50). When there are none, it reads "No warns".

How it works in Discord​

Admins issue and manage warnings entirely in Discord:

CommandWhat it does
/warnIssues a warning to a member.
/unwarnRemoves a warning.
/warnlistLists a member's warnings.
/clearwarnsClears a member's warnings.

Each warn DMs the member an embed showing the server, the admin who issued it, the reason, and their current count against the limit — so members always know where they stand. When a member reaches the Warn Limit, the agent applies the configured action and their warns are cleared, resetting the count.

Exempt roles and bots can't be warned. Warns issued elsewhere — a Delete + warn auto filter or a Warn member trigger action — flow through the same system.

Saving your changes​

This page uses a batched save — edits stay local until you select Save in the bar that appears at the bottom of the page. Leaving the page with unsaved changes shows a warning first.

Best practices​

A warn system members trust
  • Keep the default limit of 3 — one warning to inform, one to confirm, one to act.
  • Start with Mute (timeout) as the limit action; escalate the setting to Kick or Ban only if repeat offenders shrug off timeouts.
  • Because warns clear after the action fires, a returning member starts fresh — pair Warns with Reports & Vote Ban for community-driven escalation on repeat offenders.
  • Route the Warning event to your Mod Log so the team sees who warned whom.
Troubleshooting

/warn isn't doing anything?

  • Check that "Allow admins to warn members with "/warn"" is toggled on and saved.
  • Exempt roles and bots can't be warned.

The limit action didn't apply?

  • If you've customized the agent's permissions, the action needs the matching Discord permission (Moderate Members for timeouts, Kick/Ban Members), and the agent's role must sit above the member's roles.
  • Timeouts cap at Discord's 28-day maximum.

A member says they never saw their warning?

  • Warns are delivered by DM — members who have DMs disabled for the server won't receive the embed.

On this page