Warnings

Set up in the Mini App

Open Settings in your private chat with @defendy_bot, select the group under My groups and check its name at the top.

Open Warnings.
Choose basic, mild, moderate, strict or custom mode.
Set the warning reset period.
In basic mode, choose a warning limit and the action at that limit. In tiered mode, configure each threshold and its action.

Switches and selectors save when changed. In a separate form with a Save button, save before leaving. If a request fails, reopen the section to check its actual values.

Tip: change one option at a time and verify the result in the group so false positives are easy to spot.

In short

Warnings turn separate violations into a predictable escalation path. Use tiers when one final action is too blunt.

How it works

A manual /warn adds one point. A filter configured for Warning adds its selected weight from 1 to 5; message deletion is a separate setting.
Defendy compares the total with the limit or tiers and selects the highest eligible tier, taking account of actions already applied. A high-weight event can skip intermediate thresholds.
Further points can trigger the final action again. Applying a punishment does not itself clear the counter.
The reset window starts with the first addition to a new counter. Later additions do not extend it; the total expires together rather than one incident at a time.

Selects basic, mild, moderate, strict or custom escalation. Changing a preset replaces the current tiers and saves immediately; the WebApp retains the last custom set while the page remains open. Returning to basic mode keeps one threshold active rather than disabling warnings.

Warning limit

Default: 3.

The single threshold used in basic mode before the configured action is applied. The WebApp offers 1 through 10.

Limit action

Default: Mute.

Action used by the single-threshold mode: do nothing, mute, ban or kick.

Action duration

Default: 3600 sec.

Duration for temporary restriction actions.

Reset time

Default: 24 h.

The counter window measured from its first point addition: 1, 6, 12, 24, 48, 72, 168 or 720 hours. For example, a 24-hour window starting on Tuesday at 10:00 expires around Wednesday at 10:00; a later addition on Tuesday evening does not move expiry to Wednesday evening. This period is independent of a mute or ban duration.

Escalation tiers

Default: None.

Multiple thresholds with separate actions and durations. Each threshold can be 1–20 in the current editor; equal thresholds are automatically shifted to remain unique.

Important: Add tier from basic mode creates a second tier two points above the current limit, with an indefinite ban. Check this transition in a test group first and review every created action and duration.

Practical example

Hypothetical example: reaching three points triggers a one-hour mute; the total expires 24 hours after its first addition. Ending the mute does not clear points, and clearing points does not lift an existing restriction. Publish the rule before enabling stricter tiers.

Built-in profiles

Mild: three points trigger a one-hour mute; five trigger a one-day ban.
Moderate: two points trigger a one-hour mute, four a one-day mute, and six an indefinite ban.
Strict: one point triggers a 30-minute mute, three a one-day mute, and five an indefinite ban.

A profile name does not change filter weights. Even the mild profile contains a ban; inspect the complete policy in a test group.

Correct warning points

/warns shows the current total. /unwarn removes one point, not the entire weight of the most recent event. /resetwarns clears the counter and applied-tier state. These commands do not lift an existing mute or ban; restore access separately. See moderation commands.

Troubleshooting

Check that Defendy is still an administrator in the group.
Refresh the settings panel and make sure you are editing the correct group.
If a setting is saved but does not work, check the bot permissions in Telegram.
If logging is connected and the relevant category is enabled, check the event record. The log cannot show events that were not recorded.

Check the duration after changing an action

Changing the punishment type can reset its duration to 0. Where supported, zero means an indefinite action, not a disabled punishment. A temporary mute lasts at least 60 seconds. Recheck the duration before leaving the form.