v2.1.1

Hotfix release

Fixed

• Warden: fixed an issue with models default values (such as notify-staff action)

v2.1

READ BEFORE UPDATE: This release bumps pydantic's release from 1.9.1 to 2.7.2. You might need to restart your bot and manually update your requirements.

This is generally done by:

1. Uninstalling Defender (your data will not be lost) with [p]cog uninstall defender
2. Issuing a [p]pipinstall pydantic~=2.7.2
3. Restarting your bot
4. Reinstalling (through the Index or what you usually use) and loading Defender

Added

New Warden actions:

• timeout-user
• archive-thread #67
• lock-thread #67
• archive-and-lock-thread #67
• delete-thread #67

New Warden conditions:

• display-name-matches-any
• display-name-matches-regex

v2.0.2

Hotfix release

Fixed

• Do not install requirements already present in Red (#71)

v2.0.1

Hotfix release!

Fixed

• Fixed an issue with message replies being ignored (#63)

v2.0

!!! Possibly a breaking release. Read before updating !!!

This release supports Red 3.5. Any release prior to 3.5 is incompatible with this version of Defender. Do not update if you're still on 3.4
Furthermore, deprecated Warden syntax has been removed with this version. If you're unsure whether you're still using deprecated syntax (unlikely), check with [p]def wd find

This sizeable Defender major release brings compatibility with Red 3.5 and the many many new features that come with it. The index and sbansync cogs have also been updated.

Added

• Warden checks, a powerful feature that allows you to fine tune the standard modules of Defender
• Added a dropdown for Quick Actions. No more cumbersome reaction adding
• Added a big red button to stop the [p]alert's timer
• Vaporize: customizable maximum targets
• Discord Threads support: your Defender can finally monitor threads as well
• Added dropdown / buttons for a number of settings
• Warden: added WarnSystem integration

Changed

• Dropped the fuzzywuzzy library in favor of rapidfuzz

v1.12

This release includes a massive Warden refactor that allows me to (much) more easily maintain and extend it. While it's been already used in production extensively mistakes can always slip through: let me know if you notice any issue.

Added

• Voteout: punish action is now handled
• Added owner-only [p]def debuginfo to better aid when providing support
• Invite filter: Toggle for message deletion (Fixes #50)
• Warden: Added var-assign-heat action (Fixes #47)
• Warden: Added var-math action
• Warden: Added reaction events for cached messages (Fixes #21)
• Warden: Added role events

Changed

• Use markdown formatting for nicer message logs (#48)
• Warden: fixed a pagination issue within [p]def wd show
• Warden: nested blocks are now supported, allowing for more complex conditions / logic
• Bumped dependencies

v1.11

Red 3.5 is on the horizon and as some of you might know, it's going to contain a number of breaking changes for the cog ecosystem. Many cogs will not work, sometimes even just partially, unless updated to run on that version. This release (and any future release pre-3.5.0) adds a safeguard to ensure that Defender will refuse to load on Red 3.5, forcing you to update to a compatible release when the time comes

Added

• Warden: added a toggle for user regex's safety checks. Disabling it is not recommended as faulty user regex could cause performance issues.
• Warden: new condition message-contains-word for easier whole words matching. It also supports patterns.
• Warden: added the $user_display context variable that will contain the user's name or nickname, if one is set

Changed

• The punish message now supports user context variables. e.g. you'll be able to add the user's mention to the message. This is a minor breaking change in behavior, as the cog no longer adds by default a mention at the start of the message

v1.10.1

Fixed

• Warden: send-message Fixed an issue with embeds not being sent in particular instances

v1.10

!!! This release fixes a major security issue. Update ASAP !!!

More information about this vulnerability will be disclosed in ~2 weeks

Added

• Warden: activity is now a supported attribute in the action get-user-info
• Warden: an arbitrary destination channel can now be specified for issue-command
• Warden: action send-message now supports replies

Fixed

• Code blocks with capitalized 'YAML' and 'YML' are now properly handled with [p]def wd add (#46)

v1.9.1

Fixed

• User / channel heat levels in [p]def wd memory will no longer raise an error

Changed

• Warden: set-channel-slowmode will preemptively check the current slowmode delay value to avoid unneeded API calls