Sulfurlogger

A Paper plugin that logs blocks destroyed by Sulfur Cube explosions to CoreProtect and attributes them to the player responsible.

Normally these explosions have no author: CoreProtect records nothing, and there is nothing to roll back after griefing. Sulfurlogger remembers who loaded the cube with TNT and who ignited it, and ties the destruction to that player.

Features

• Logs destroyed blocks to CoreProtect, so they can be inspected and rolled back as usual
• Detects the player who gave the cube TNT (fed it to the cube or released it from a TNT-loaded bucket)
• Detects the player who ignited the cube:
  • flint and steel or fire charge;
  • weapons with the Fire Aspect enchantment;
  • burning projectiles and fireballs;
  • explosion of primed TNT or another Sulfur Cube (chain reactions)
• Data is stored directly on the entity (PersistentDataContainer), so it survives server restarts
• The igniter is held responsible for 5 minutes; after that, responsibility falls back to the player who loaded the TNT

How it works

When a cube explodes, every destroyed block is logged to CoreProtect under the name #sulfur-<player>. If the responsible player cannot be determined (for example, the cube was released by a dispenser), #sulfur-unknown is used.

Commands

The plugin has no commands of its own. Use the standard CoreProtect commands:

/co lookup user:#sulfur-PlayerName
/co rollback user:#sulfur-PlayerName time:1h radius:30
/co inspect

Requirements

• Paper with Sulfur Cube support
• CoreProtect with the API enabled (API version 9 or higher). In CoreProtect's config.yml, set api-enabled: true

Limitations

• Only block destruction is logged; damage to players and mobs is not recorded
• A cube released by a dispenser is attributed to unknown
• No file logs are kept; all data lives in CoreProtect (if you chose right version of it)

Installation

1. Put Sulfurlogger.jar into your plugins folder
2. Make sure CoreProtect is installed and its API is enabled
3. Restart the server