Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strikes don't automatically timeout members #154

Open
Frostbyte0x70 opened this issue Jun 17, 2023 · 3 comments
Open

Strikes don't automatically timeout members #154

Frostbyte0x70 opened this issue Jun 17, 2023 · 3 comments
Labels

Comments

@Frostbyte0x70
Copy link

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:

if(muted==null || mem==null || !moderator.getGuild().getSelfMember().canInteract(muted))

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.

@ALocked1
Copy link

ALocked1 commented Jun 18, 2023

Vortex hasn't been made to timeout users yet, it only recognizes if a user got timed out and logs it as a tempmute. You still have to use the Muted role until then.

@Frostbyte0x70
Copy link
Author

It doesn't? The >>muterole command says it does use timeouts when no role is set:

event.replyError("Please include the name of a role to use as the Muted role. If set to `none`, Vortex will use Timeouts instead of applying a role.");

@ALocked1
Copy link

I think jag added the text in advanced but to my knowledge Vortex is incapable of using timeouts until JDA Utils is updated

@jagrosh jagrosh added the bug label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants