LogBlock Plugin FAQ

After installation, LogBlock will create a MySQL database connection and begin logging automatically. Check your server logs to confirm the database connected successfully, then use `/lb query` to start looking up block changes in your area.

You need a working MySQL server with connection details (host, port, username, password, and database name). Enter these credentials in LogBlock's config file, and the plugin will create the necessary tables automatically on first run.

Stand near the block and use `/lb query` to see recent changes in that area, or use `/lb area ` to search a larger region. The results will show the player name, timestamp, and action (break/place).

Yes, use `/lb rollback player: ` to undo all changes by that player in your current area, or combine it with area parameters like `/lb rollback player: area: ` for more control.

Configure a tool item in the config file and assign it query parameters—then right-click with that tool to instantly run your preset search instead of typing commands every time.

No, LogBlock processes all database writes in separate threads to avoid impacting server performance, even with hundreds of thousands of log entries. The main server thread stays responsive.

You can configure the retention period in the config file to keep logs for as long as you want—days, weeks, months, or indefinitely. Old entries are automatically purged based on your settings.

Yes, the config file lets you enable or disable logging for specific block types, entity changes, and actions to reduce database size and focus on what matters for your server.

Rollbacks are permanent changes to your world, so always double-check your query results and area radius before executing a rollback. Consider doing a test query first to confirm you're targeting the right blocks and players.

Yes, LogBlock stores everything in a standard MySQL database that developers can query directly to build custom tools like player statistics dashboards or administrative panels.