Minecart Rapid Transit Wiki:Blockcheck

From Minecart Rapid Transit Wiki
Jump to navigation Jump to search
Ambox important.svg This page in a nutshell: All block placements, block removals and container transactions on the main server are logged and retained for at least four months. Moderators may inspect this history at any time, and administrators may roll back changes. Ambox important.svg

Blockchecking is a tool available to moderators and above that displays the complete history of a particular block or container. It uses the CoreProtect plugin for CraftBukkit.

What information is logged

The following information is recorded:

  • Players adding items to a chest or hopper through the inventory interface
  • Players removing items from a chest or hopper through the inventory interface
  • Block placements by players, pistons, or WorldEdit
  • Block removals by players, pistons, and WorldEdit

All of these logs record the name of the player, the timestamp (accurate to 36 seconds) of the event, and what block or item was used.

Who can check logs

Moderators and above have the ability to perform CoreProtect inspections by using the /co i command. Once a block has been selected, further interactions can be viewed using /co l # to view seven items per page.

Administrators can roll back changes using /co rollback u:user t:time r:radius. This tool quickly undoes all changes within the specified parameters. Changes that are rolled back are struck out in the interaction history when viewed with /co i or /co l and can be restored using /co restore u:user t:time r:radius.

Retention of Logs

We purge logs at the end of each month and keep a minimum of four months of data available at all times. Because of this, some builds may be too old for CoreProtect data to be available for them.

Associated MRT Policies

Thousand Hour Clause (KHC)

Main article: Incomplete builds

Template:Minecart Rapid Transit:Incomplete builds

Old Build Clause (OBC)

Main article: Old builds

Template:Minecart Rapid Transit:Old builds