/Jbrules does (or did this) it may have been removed, and I expect the link to be invalid or old now. Pester Ben.
This helps. Thanks. Can you also have the site open up in MOTD by using the /rules menu that appears when you first join the server? Not everyone will know that /jbrules exists.
Admins can mic check whenever they want at their own discretion. You muting them and/or not hearing especially after being frozen is your own fault.
It's still counterintuitive to do a mic check while the warden is trying to give commands. You have two people, who need to speak, talking at the same time. The warden can't just remain quiet or else the prisoners won't be controllable. It's entirely avoidable. The client-side mute thing I can understand, but admins should have a better sense of when it's appropriate to check for mics without adding to any chaos. I wouldn't complain about this if this hadn't happened on numerous occasions.
Freekilling is not allowed. Freedays may not be killed unless they rebel. Last guard kills all applies when warden is locked and there is one guard remaining which also removes the freeday given to any reds at the start of the round.
Why even have freedays be removed automatically when an lr has been selected? They die within 30 seconds anyways. Why not have them keep their freeday status until they actually rebel? It looks silly even of paper. If it's a problem with the Jailbreak plugin, then correct it.
As for the last guard kills all part, have the message only show up when the warden is locked so it notifies the last guard and remaining prisoners that the last guard can now start killing reds. If you're worried about people using /uw to activate it, then don't allow them to be able to /uw when 1 guard is alive. While we're on the subject about /uw, I should ask this. If 99.99% of the time you can't use it, why even have it? It just enables abuse.
Suggested numerous times and declined because it's just a flood of spam to the server for no good reason as warden is obliged to repeat his orders if asked anyway.
What are you talking about with flood of spam? Have a timer for how long the system can be used again so that it can't be spammed. The warden can't repeat their orders if they're being talked over which happens more frequently than you think. Sending reports wouldn't do jack shit if the same events keep happening over and over again. If a system isn't implemented to prevent the human factor, then the scenario will continue to repeat itself. You can't stop people from talking over the warden whenever able because of psychology. Hell, that's why the reds are muted for the first 30 seconds at the start of the round.
So what's the point of admin if preventing the problem doesn't help it :/ ???
I saved this one for the end because it's probably the most important response.
I understand that all of this overhaul would require work, but that's the whole point of preventing an idiotproof system. It won't be infallible, but it would be more sufficient if there were automated protections in place. This should have been said at the very begin of my first post.
Sending admins to enforce the rules should be the LAST line of defense. Admins exist to act as an alternative if automated systems break down or are bypassed. Automated systems include guardbans, random warden selector, reds muted for 30 seconds at the start of the round, LR menu, etc. With Jailbreak, no effective automated system seems to be in effect with the subjects I've mentioned earlier. Meanwhile, rules like no unwardening can easily be made less frequent if /uw never existed. Admins should look into
why and how these instances happened in the first place and find efficient ways to make them happen less often. Instead, you merely double down on all suggestions while other admins like will are scratching their heads asking "how do we fix this" and making threads like this.