Strikes don't automatically timeout members
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 600
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Description
When Vortex is configured to use timeouts instead of a muted role, triggering an automated mute punishment by giving a strike to a user does not apply any punishment, just logs the strike.
Seems like the part of the code responsible for this wasn't updated to support timeouts:
https://github.com/jagrosh/Vortex/blob/e64f73b166cdb17da73c887bd1d70360207c7923/src/main/java/com/jagrosh/vortex/automod/StrikeHandler.java#L148
This section should be changed to timeout the user if no muted role is set, as well as checking for the `MODERATE_MEMBERS` permission instead of `MANAGE_ROLES` when that's the case.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/main/java/com/jagrosh/vortex/automod/StrikeHandler.java around line 148 and trace the automated mute punishment path when a strike is given. Check the configured muted-role and timeout cases, including their required Discord permissions. Done means strikes apply the configured punishment in both modes and use the corresponding permission check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100