undo last thing another player did via console

[ichVII]

TL;DR

Give admins the power to undo griefers actions quickly and swiftly

What ?

some command like /undo playername, that works excatly like that player pressing ctrl z

Why ?

Do i really have to explain this?

[ssilk]

Yes. Me as griefer would just paste so much, that it is impossible to undo, to make sure, the game is ruined.

How do you you undo, when the griefer has made more things, than you can undo?
What will you do, when other players meanwhile have “overwritten” the things he has made?

[ichVII]

Griefer enters the game, places a stupid bp and gets banned in less then a minute. That happened to me and this feature would help a lot

[ichVII]

Thats like saying, if the method doesmnt help against 100% of griefers, its not worth doing at all. Reminds me of stupid NRA arguments.

[eradicator]

I don't see any way to access the undo functionality via the api, so there's no moddability for this either. Moddability would imho allow finer grained control than a one-shot command. So i'm not gonna +1 this because it's not about modding :o.

Deleting ghosts of a specific player is easy ofc:

Code: Select all

/c local griefer_name =             "PutPlayerNameHere"              for _,s in pairs(game.surfaces) do for k,v in pairs(s.find_entities_filtered{name='entity-ghost'}) do if v.last_user.name == griefer_name then v.destroy() end end end

@ssilk I have to agree with @OP that your sarcasm is not helpful. The mere possibility of circumvention is not a sufficient reason to not have a system at all. (Not saying there aren't possibly other valid reasons.)

[ssilk]

What your script does is not undo, it destroys everything a griefer has done.
There is also not as much sense as you think in a interface for undo for modders: you cannot undo only things from one player, when another player has pasted over that afterwards - the result is not repeatable. You need to undo in the correct order.

If you mean deleting, then we can rename the subject of this thread, because “undo” always has this interference with time. That’s the idea of an undo.

But also then: I can easily paste some really big bp over everything before being kicked. We had that already viewtopic.php?f=6&t=43310

And I don’t understand why pointing out weaknesses in suggestions should be sarcastic. I see that as service and part of my “job” in this subboard.

[eradicator]

Griefer enters the game, places a stupid bp and gets banned in less then a minute.

Deleting ghosts of a specific player is easy ofc:

What your script does is not undo, it destroys everything a griefer has done.

Don't remember saying anything else. That in itself *is* ofc a partial undo going by the meaning of the word even if it doesn't use what the engine calls "undo".

There is also not as much sense as you think in a interface for undo for modders: you cannot undo only things from one player, when another player has pasted over that afterwards

You're focussing on an edge case again. At least from my experience players are usually far away from each other. And in any case the engine *already* has to deal with that. So in the best case you can undo 100 steps (or whatever the max undo history length is), worst case you can only undo 10 steps because someone wasn't properly educated on not to manually mess with griefed blueprints. Exposing undo/redo to the API doesn't change that. It is already possible to maintain a full history of build/destroy events on the lua side and use that, but that's a lot of redundant data if the engine is keeping it already.

If you mean deleting, then we can rename the subject of this thread

Since when do threads get renamed based on what I say?

[ssilk]

Well,ok, I have been irritated by the word undo. And still be.