Reputation penalties

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

In short#

Penalties connect moderation events to reputation so repeated violations affect trust automatically.

How it works#

1. A supported moderation violation is recorded for a member.
2. If automatic penalties and that violation's control are available and enabled, Defendy selects its negative value.
3. The value is subtracted from reputation, after which rank and sanctions may be recalculated.

Set it up step by step#

1. Open Defendy in Telegram and choose the group you want to configure.
2. Compare the current values with the defaults explained below.
3. Change one option at a time; use the least disruptive value that meets your goal.
4. Check the result in the group after saving.

Every setting explained#

Enable auto penalties#

Default: On.

Applies reputation penalties for moderation violations.

Profanity#

Default: -3.

Reputation change applied when profanity is detected. Options: 0, −1, −2, −3, −5, −10; zero disables this penalty.

Flood (coming soon)#

Default: -2.

The value exists in the settings contract with options 0, −1, −2, −3, −5, but the current WebApp control is disabled and marked coming soon.

Caps (coming soon)#

Default: -1.

The value exists in the settings contract with options 0, −1, −2, −3, but the current WebApp control is disabled and marked coming soon.

Stop words#

Default: -2.

Reputation change applied when stop words is detected. Options: 0, −1, −2, −3, −5; zero disables this penalty.

Spam#

Default: -5.

Reputation change applied when spam is detected. Options: 0, −1, −2, −3, −5, −10; zero disables this penalty.

Warning (coming soon)#

Default: -5.

The value exists in the settings contract with options 0, −1, −3, −5, −10, −20, but the current WebApp control is disabled and marked coming soon.

Practical example#

Start with −1 for profanity and stop words and −2 for confirmed spam. Leave unavailable flood, caps and warning controls untouched until they become active in the WebApp.

Recommendations#

• Penalty values are negative. Zero disables a specific penalty.
• Keep penalty sizes proportional to the warning weight of the same violation.

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 you are not sure what happened, open the moderation log.