Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

Double Punishment Confirmation #946

Open
4 tasks done
tarna opened this issue Mar 17, 2022 · 2 comments
Open
4 tasks done

Double Punishment Confirmation #946

tarna opened this issue Mar 17, 2022 · 2 comments
Labels
feature request New feature or idea suggestion

Comments

@tarna
Copy link

tarna commented Mar 17, 2022

Feature request

Checklist

  • I have read and agree to the README (found on https://github.com/Minehut/Meta)
  • This is not a bug report, support request or plugin request
  • I have searched the Issue Tracker to make sure this is not a duplicate issue
  • This issue does not contain any sensitive information

Platform

In-game

Describe the feature

When trying to double punish someone, instead of just preventing it from happening and showing an error message, a confirmation GUI should come up saying like "This player has already been punished in the last 5 seconds, would you like to punish them again?" and 2 options, one for yes, and one for no.

How the feature is useful

Right now if someone has 0 punishments and they start spamming out of nowhere, punishing them for spam will just warn them. But if they continue doing it and aren't stopping so you go straight to the 2nd mute punishment, it won't let you because they were already punished in the last 5 seconds. So now the moderator has to wait 5 full seconds of their spam to actually mute them. I've seen a lot of players complain about how the mods take forever to mute someone and this could help them punish spammers faster.


Use 👍 and 👎 reactions to indicate you agree or disagree with this suggestion! Feel free to discuss the idea in the comments.

@tarna tarna added the feature request New feature or idea suggestion label Mar 17, 2022
@CoreyShupe
Copy link

CoreyShupe commented Mar 17, 2022

This exists. Does this happen often enough to where we need to extend the cooldown?

Misunderstood, yeah potentially could be helpful. Is it a recurring problem?

@tarna
Copy link
Author

tarna commented Mar 17, 2022

This exists. Does this happen often enough to where we need to extend the cooldown?

Misunderstood, yeah potentially could be helpful. Is it a recurring problem?

Ya, it was a recurring issue when I was staff and I see it happen with the current staff team too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature request New feature or idea suggestion
Projects
None yet
Development

No branches or pull requests

2 participants