Help
LiveTroubleshooting
Common Defendy problems and their solutions: the bot won't ban, a command doesn't respond, a setting doesn't work, false filter triggers.
If Defendy behaves differently from what you expect, follow the steps below. Most often the cause is in the bot's permissions or the member's role.
The bot won't ban, mute or delete
- Make sure Defendy is a group administrator with the necessary permissions (ban, restrict, delete messages).
- Check the offender's role: Telegram administrators cannot be restricted like ordinary members.
- Check that the module or command in question is enabled.
- After changing administrators, run
/reload.
A command doesn't respond
- The bot must be an administrator and present in the group.
- Check that your role has access to the command — see All commands.
- Make sure the command is typed with a supported prefix (
/,!,.,,,;). - For commands that act on a message, reply to the message in question.
A setting is saved but doesn't work
- Check that Defendy is still an administrator and its Telegram permissions were not removed.
- Make sure you are editing the correct group.
- Refresh the settings panel.
- Open the action log to see whether the rule is triggering.
The filter deletes too much (false triggers)
- Find the triggered rule in the action log.
- Add an exception (a word, domain, trusted source or role).
- Lower the strictness or choose a milder action.
- Change one parameter at a time and check the result.
The captcha doesn't trigger or gets in the way of real members
See the separate page Captcha diagnostics: check the mode, the bot's permissions, the time to answer and the number of attempts.
The bot's messages arrive in the wrong topic
Check the forum topic for the module in question (/settopic and the /set…topic commands). Without a topic set, the group's general topic is used.
How to migrate or reset settings
Settings are defined for each group separately in the panel. Migrating settings between groups and import/export are planned features and are not available yet.
Where to get in touch
If the problem is not resolved, write to support at @ubotz: provide the group ID, the time of the event and the settings without personal data.