LogBlock logs block changes into a MySQL database. Block changes can be placed or destroyed block, explosions, burned blocks, sign text changes, chest access, leaves decay etc. It can be used as griefer identification tool, to find out who build a particular building, or even roll back changes by certain players. Other purposes can be e.g: Undoing of forest fires All additional features are optional, to keep the database as short as possible. All database actions run in their own threads to avoid server lags. The use of permissions plugin (or any clone) is possible, but not necessary. Uses Spout for chest logging (but it's fully optional, and there is no need for the client mod at all). https://dev.bukkit.org/projects/logblock/
Requirements
You require a MySQL database the configure LogBlock, (Create a MySQL database for Bukkit Plugins)
Edit this config file /plugins/LogBlock/config.yml
Then change the following sections to include your database settings after creating your MySQL database.
mysql:
user: username
port: 3306
password: pass
host: localhost
database: minecraft
Save the config file then type reload into your console or /reload ingame and the plugin will start working
Command Reference
/lb help Ingame help
/lb params List of all params
/lb commands List of all commands
/lb permissions List of all LB related permissions you have
/lb tool Gives the lookup tool (default woodpickaxe)
/lb tool [on|off]
Toggles whether the tool is enabled or not
/lb tool [params]
Binds a new query to the tool. This affects only you and works until server reload/restart.
/lb toolblock
Gives the block lookup tool (default bedrock)
/lb toolblock [on|off]
Toggles whether the tool block is enabled or not
/lb toolblock [params]
Binds a new query to the tool. This affects only you and works until server reload/restart.
/lb savequeue
Saves all block changes immediately into database. Useful for rollbacks after huge fires.
/lb lookup [params], /lb [params]
Shows you the result of a query.
/lb writelogfile [params]
Write the result of a query into a log file to "/plugins/LogBlock/log". The layout is similar to the message from the wood pickaxe. If no results were found, the log file will be empty
/lb tp [number]
Teleports you to the location of a block change in the last lookup or rollback errors. To be able to teleport to lookup results you have to use coords param for the lookup, eg:
/lb player diddiz destroyed block diamond_ore coords
/lb tp 1
/lb tp 2
/lb page 5
/lb tp 62
/lb tp [params]
Teleports you to the location of a block change. E.g. /lb tp player diddiz teleports you to the last blockchange of player diddiz.
/lb rollback [params], /lb undo [params], /lb rb [params]
Rolls back block changes.
/lb redo [params]
Redoes block changes, counterpart of rollback.
/lb clearlog [params]
Deletes the log. Cannot be undone, except you have dumpDeletedLog enabled and import the dump. It's highly recommended to do a lookup first, and call /lb clearlog last to avoid deleting accidentally wrong log.
/lb hide
Toggles hiding. No actions from a hidden player will be logged! Be careful!
Example Commands
/lb rollback player fire since 1d3h - rolls back fire 1 day 3 hours
/lb rollback player fire since 1d3h area 15 - rolls back fire 1 day 3 hours within a radius of 15 blocks
/lb rollback player thad0ctor since 1h - rolls back thad0ctor 1 hour
/lb rollback player thad0ctor since 1d area 5 - rolls back thad0ctor actions for the last day within 5 blocks
/lb rollback area 10 since 1h30m - rolls back all modifications within 10 blocks since the list 1 hours and 30 mins
/lb rollback area 10 before 06.11.2011 - roll back all changes in an area of 1o before June 11th, 2011
/lb rollback player thad0ctor since 05:36:00 - roll back all changes of thad0ctor since 05:36 (server time)