World Edit Issue. MUST READ!

[LordDecapo]

Recently we have had a LOT... and i mean a LOT more WE fuck ups that are both more frequent and more destructive than any time i have ever seen. Just the past 2 weeks alone there has been more issues and things getting broken then the last year combined. 
THIS HAS GOT TO STOP!!!
YOU have GOT to watch out for YOUR selection positions and the stack values you use. This is getting beyond old... almost every day getting buzzed on my phone that my shit is broken cause one of you all carelessly fucked shit up... yet again.

From here on out ANY and ALL WE mistakes that require an admin to stepin will be a MINIMUM 2 week global temp ban.... no build... no school.... no survival.


we have been very nice in the past with these sort of things.. and it appears that that kindness has made you all soft in your midset causing no one to double check their stuff before hiting enter.

THIS is EVERYONES warning. I will not accept "well i didnt know" as an appeal to the 2(+) week ban you get for your WE mistakes.

[BigPigfootsie]

woof
if capo is angry
it must be serious

[PNWMan]

Whenever you have 2 points selected, the most recent selection point will have a number at the end. That number shows your selection size. Also LiteLoader+WorldEditCUI is super helpful because you can see your selection with gridlines. Also, there's //limit <amount> which will set a limit per user for the maximum amount of blocks changed. Keep in mind if your WE exceeds the limit, it doesn't completely drop the command. It just changes all the blocks until the limit is reached.

[artemasrukh]

Rember that //Undo is a thing, and a global //Limit is also somethign else. Undo doesn't always work, but I've had a few major fuckups, where I accidentally added a 0 to my stack command, and it went miles...

[embizone]

Why not just impose a WE limit on all builders... or only trust certain people...

[JeremyG]

I would also recommend doing //sel after you're done with any worldedit selection. This will clear your selection, so you can be sure that any remnant positions won't accidentally make it into your next selection.

[Iceglade]

I don't know what staff discussed, but to me it seems like revoking WE privileges (or a build-only ban) makes more sense than a global ban if there was no malicious intent.

[JeremyG]

The idea is to make the repercussions quite severe such that people will take a lot more care when doing their worldedits.

[Apuly]

Still, global banning people right away is a pretty extreme

[tokumei]

... not so extreme for an extreme, sometimes unfixable problem

[Apuly]

... pretty extreme for somebody that simply has an accident for the first time.

I'm not saying never global ban, but first time perpetrators should not get this high punishment.

[MrPixelized]

I agree, speaking from personal experience, being banned over a month seems way too extreme after having had a w/e fuckup. Two weeks isn't as long as I got banned, but it still seems a little over the top.
Or just, don't do it globally. Banned from build and no w/e on school seems like a reasonable punishment for a first-timer.

[tokumei]

There is no reason to go lighter on a first-timer if it is an explicit rule. That's the reason for this post; it is the warning that it can't be tolerated.

Also gg swift, I think we have a world record contender for how quickly a rule has been broken.

[Apuly]

I'm not saying go light on a first-timer, I'm saying go light on an accidental first timer.

Basically yea cya in 2 weeks swift

[BigPigfootsie]

who said its an accident?
check dem chat logs on school, m8

I'm not saying go light on a first-timer, I'm saying go light on an accidental first timer.

Basically yea cya in 2 weeks swift

[zSwifty]

There is no reason to go lighter on a first-timer if it is an explicit rule. That's the reason for this post; it is the warning that it can't be tolerated.

Also gg swift, I think we have a world record contender for how quickly a rule has been broken.

Thanks non xd, also any damage that would of been, would be behind the border, and thus no plots affected at all, (no w/e even proccessed after the crash so nothing happened) still, fair is fair and a ban is going to take place i presume, do what you must.

Ps. Bigpig is triggered xd

[LordDecapo]

The idea is to make the repercussions quite severe such that people will take a lot more care when doing their worldedits.

^

[EEVV]

teh grammerz is extrem on this 1.

[slugdude]

We used to have WESV 1.8->1.9 but it got removed because it didn't update. Well, it has updated and I have it working flawlessly on my 1.11.2 server. We should get it back.

[PNWMan]

Personally I prefer WECUI over WESV, but if installing WESV helps people to not mess up, I agree that we should install it and have it be on by default like last time.

[slugdude]

Personally I prefer WECUI over WESV, but if installing WESV helps people to not mess up, I agree that we should install it and have it be on by default like last time.

Personal experience: People are too lazy to do shit for themselves, myself included. Shove it down their throats then they can't complain.

[optimo]

+1 vote for adding back WESV
I like it because it seems more vanilla - redstone pixie dust

please and thanks

[optimo]

I WANT HAZ WESV PLZ NICK
until you have your own plugin finished?
I don't think it's a big ask, but maybe I'm naive.

[Chibill]

I WANT HAZ WESV PLZ NICK
until you have your own plugin finished?
I don't think it's a big ask, but maybe I'm naive.

Please don't bump.  Also we have had problems with WESV..

[slugdude]

I WANT HAZ WESV PLZ NICK
until you have your own plugin finished?
I don't think it's a big ask, but maybe I'm naive.

Please don't bump.  Also we have had problems with WESV..

Iirc it was causing issues because it wasn't updated to 1.10/11. But now it is so *shrug*