We unblocked //brush thanks to Total Freedom is a Shitty Server. and Let's work together to fix things, and it's proven that it does log in CoreProtect. However it seems like that we have taken steps backwards and blocked it again.
Regression: //brush is blocked again
-
- Official Post
I believe it was found not to reliably log and was used to create non reversible damage.
-
Yes, we blocked it because initially we blocked a problematic portion of it using some regex magic but then some fucking dickhead over at EngineHub thought it was a good idea to accept quotation marks in the fucking arguments and someone abused this fact to untracably grief. Fucking garbage plugin.
-
We unblocked //brush thanks to Total Freedom is a Shitty Server. and Let's work together to fix things, and it's proven that it does log in CoreProtect. However it seems like that we have taken steps backwards and blocked it again.
The reason it got blocked was some assholes thought it'd be "funny" to use it and grief by bypassing world permissions leading to incidents where worlds where operators cannot build, etc. were being griefed and it becomes incredibly hard to determine who did it without brushing through server logs to catch the culprit going to the world and equipping the brushes. Whoever those individuals were you can thank them for this. Video's reply gives a more technical look into why this shit happened.
-
Yes, we blocked it because initially we blocked a problematic portion of it using some regex magic but then some fucking dickhead over at EngineHub thought it was a good idea to accept quotation marks in the fucking arguments and someone abused this fact to untracably grief. Fucking garbage plugin.
Does FAWE handle this any better?
