Perhaps we could have enhanced logging of VoxelSniper that would allow for rollbacks after the server has restarted or crashed?

Or maybe an indicator of who edited which blocks, so any griefing done with VoxelSniper could be tracked.

I was considering a persistent undo cache for #64.

Do note, by the way, that VoxelLog already logs snipes. It doesn't keep track of every block changed (that would get horrendously massive). But it does record the central snipe block, the brush used, the person, and a timestamp.

So all you have to do is estimate about where the center of the snipe was, and roughly when it happened, and the sniper can be found in the logs already. It won't do ROLLBACKS, but it will allow you to find somebody to blame.

Cisco & Ridge are never around to check it though :/

I thought voxelLog was changed so that it saved in a publicly accessible dropbox or http-linked folder? If not, just tell Cisco/Ridge to share the voxelLog folder?

Kinda silly to recode something in voxelsniper that already exists, just because the folder with the info doesn't happen to be shared...

As far as I know sharing the Log folder won't be very helpful since VoxelLog logs the logs into a NoSQL database.

The VoxelLog you're talking about GavJenks and Monofraps is the old one.

There's some new VoxelLog plugin that saves to a database, and we need MikeMatrix to make some way to access it (or so cisco says).

Mono is referring to the correct one. And yes I am currently working on a web frontend for it.