On PT an hour or so ago, there was a mishap with the RC.

It had been deconned and the builder switched teams without constructing a new one. The RC was build in a new spot, but while it was building, an admin used !revert on the old one causing there to be two RCs at once.



I managed to capture that before it was deconned and Medic said to post here.

Yeah... that kind of stuff happens with !revert. It's not a bug, just a misuse of the !revert command, and it was fixed shortly after.

No, it is a bug. Revert shouldn't behave this way. Thanks.

Its a bug in that it shouldn't happen, however its not a bug in so far as revert never clams to try to stop that.

Covering for every possibility would cause an insane amount of code, and therefore bugs.
Its assumed that admins will check and fix problems that arise etc.

Yeah.. Decon RC, build new one, revert the decon.  The only "fix" that makes sense for this is to do away with selective reverting, meaning you just go backwards like it used to (meaning when someone decons the RC and three grangers build trappers before the admin gets to it, the trappers go away but the RC is back.. and oh yea now it's SD).

Not a bug.

Isn't there a selective revert feature already? Revert per player & per team I believe.

Well, perhaps revert should work more like a revision control system in that it's able to revert back to a "state" for one team or another, but not specific buildings and things. Furthermore, this could be time based. I suppose a more accurate term for what I'm talking about here would be !rewind... pretty much go back in time.

Actually, this lack of a level of control might be better in that we could distribute !revert/!rewind to a greater community (like, say, 1.2) because there is a bit less room for admin abuse. It does exactly what it is supposed to -- fix decons.

!rewind 3min

Discuss. (I know this is very unlikely to ever be written, by the way.)

That's what revert used to be (except num revisions instead of time) but then everyone (me included) was like "hey, what if…" and I was foolish enough to code first and ask questions later.
I've thought for a while about switching back to something more basic, but it's much harder to explain to people why you downgraded.

Because I did, not STFU.

It makes sense to me that commands should do one thing and very well, and mostly be inflexible. The time thing might be interesting.

You can avoid this kind of problems by using !pause before using !buildlog and !revert, so that no one will build anything in between.

All well and good unless things are built in between the decon and the admin looking around to find out if it really was a decon or an idiot who hasn't been paying attention to team messages when someone repeatedly said "Moving OM up top"

I think no matter what happens, people are never going to be happy with the syntax of revert.  Either it's not powerful enough for some (which was the case before), or it's too powerful and possibly too easy to do the wrong thing (which is the case now).  I'd almost rather err on the side of being too powerful, simply because it introduces a little more of a curve to administration that might keep those too afraid to read documentation away from doing it poorly.  Which isn't to say that those of us who have done it wrong before haven't read the documentation - I know I reverted 3-4 bits of an alien base and missed the deconned RC when someone took out that and the armory once

Bingo. I'm more for things that benefit the smart, experienced admins. If the people who shouldn't be admins are messing it up, sucks to them. If good folks mess it up on occaision, fine, that's how you learn. Everyone's still happier with a revert screwup than just not using revert in the first place and letting the deconner win.

On the other hand, it seems to me that the reason things like !revert don't make it into the mainstream distribution is because they are abusable.