Get 0.05 TON 💎Earlier Versions
| Name | Size | Uploaded | Game Version | Downloads | |
| BlockLogger v1.2 release | 17.61 KB | Mar 8, 2012 | CB 1.2.3-R0.1 | 7,428 |  Download |
| BlockLogger v1.1.1 release | 17.04 KB | Mar 4, 2012 | CB 1.2.3-R0.1 | 741 | Download |
| Block Logger v1.1 release | 17.03 KB | Mar 3, 2012 | CB 1.1-R6 | 756 | Download |
| BlockLogger v1.0 release | 16.27 KB | Feb 22, 2012 | CB 1.1-R4 | 801 | Download |
| Block Logger v0.9 beta | 12.34 KB | Feb 21, 2012 | CB 1.1-R4 | 445 | Download |
Description
Block Logger
This simple plugin gives users with permissions the ability to use a wand and detect what has been done to a specific block.
Using the config you can change which item is the wand, and how many logs to keep per block. Default, it's 3.
The logs are currently stored in a non-human-readable form, and stored per chunk. To prevent too large of harddrive reads.
Currently it logs
- Block placing/breaking
- Furnace/Chest/Door opening
- Fire ignition
Permissions
- blocklogger.use – Allows the user to toggle and use the wand.
- blocklogger.exempt – All of the users actions are ignored and not logged
Features
- Ability to ignore logs based on block, player, and event type
Commands
- /lwand [on/off] – Toggles the wand on/off
- /lwandhelp – Displays help for BlockLogger
Usage
- Left-click with the wand out to see what's happened to a particular block
- Right-click with the want to see what's happened to the block above the selected block. (Useful for crops)
Planned features
- SQL Support
- Ability to set a buffer/saving time, to put less stress on harddrives
- Detecting where fire started and tracking it back to the player
- Detecting where water started etc..
- Roll-back actions
Add a comment