Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Rollbacks / Enhanced logging #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.
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...