LogBlock

LogBlock logo

Works 100% with 1.7 / 1.8

The best block logging and rollback solution for the savvy server administrator.

LogBlock is the best block logging plugin for Bukkit server. Not only is it awesomely powerful, it’s blazing fast! Everything is logged into a MySQL database, allowing developers to hook in and produce things such as player stats and even administrative panels. Every loggable action can be logged with LogBlock: WorldEdit, leave decay, fire, sign changes, explosions, chest changes, player and animal deaths, chat, commands and more!

Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.

LogBlock will very rarely break between Minecraft / Bukkit updates, however if you find it does, please be sure to try a development build from above, as we generally test new releases there until deemed stable.

What is LogBlock?

LogBlock is a tool which allows you to keep track of almost everything on your server, while also giving you the ability to rollback (revert) or redo changes made by users and natural occurrences such as liquid flow or leaf decay. Additionally, LogBlock is able to log and rollback chest contents, sign text and more! LogBlock was originally created by bootswithdefer for HMod, ported to Bukkit by DiddiZ and is now actively maintained by md_5, ammar2 and the community of developers on Bukkit. We accept pull requests on GitHub frequently which means that community developers can add features they wish to see quicker than LogBlock developers are able to from tickets. All database actions are run not only in their own threads, but are queued into a consumer to minimize lag on the main thread. This is great for larger servers! All optional features (not dependencies below) are enabled and disabled from within the config file allowing complete control over what is logged thus ensuring database size is kept to a minimum.

Notices

Most virtual chest plugins are not compatible with LogBlock. Because they do not set the player who is opening the “chest”, LogBlock can’t do what it’s meant to be able to do, thus, making errors in your console. Please report these issues to the fake-chest plugin developer, NOT LogBlock developers.

Issues are read more frequently on the GitHub Issues page as compared to the comments below. When updating to LB1.57, if you already have a large database and have changed your columns to MEDIUMINT, INT or LARGEINT, you do not need the updater to fix this for you automatically. To stop this behaviour, simply change “version” in the configuration to ‘1.57’.

If you are experiencing an error such as this please read the FAQ for answers.

If you're receiving errors regarding players from the consumer such as "[Consumer] Failed to add player <playername>" then change all `playerid` columns to MEDIUMINT or INT in each table that contains them. This may take a long time if you have a lot of rows.

Optional Dependencies

  • WorldEdit (Recommended)
  • Permissions plugin
  • LogBlock Questioner

Need help?

Found a bug or an issue? Please report it (and attach code if you know how to squash it) on our ticket manager.

Just need help in general or have an urgent, more private bug? Join us on IRC at irc.esper.net #LogBlock and ping a +o or +v for faster help. Webchat is available here if you don't have a client, or prefer to use it.

As always, check if your question is on the FAQ before asking!

Installation

  1. Installation
  2. Permissions
  3. BigBrother log import
  4. Configuration
  5. MySQL Configuration

More Information

  1. FAQ (read me first!)
  2. Command reference
  3. Configuration
  4. Helpful Commands
  5. MySQL Connection Problems
  6. MySQL Schema
  7. SQL Queries
  8. Parameters

Are you a Developer?

If you wish to contribute to the LogBlock project, head on over to the GitHub page, fork the project and submit your pull request(s).

If you wish to develop a plugin that interacts with LogBlock in some way, read up on the API here. Support for API and more can be found in the IRC channel, which is listed above.

Developer builds can be found here. (These builds have not been approved by the BukkitDev staff. Use them at your own risk.)

Still need help? Join us on IRC at irc.esper.net #LogBlock and ping a +o or +v for faster help.

Please do not post comments requesting support. Report bugs here or, alternatively, talk to a real person. Commenting below is a surefire way to not receive help.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of KevinGelking KevinGelking Jul 16, 2016 at 08:35 UTC - 0 likes

    @Chevels: It sort of works. Most blocks can be rolled back but there are many which aren't properly rolled back for me on 1.10.0 with logblock for 1.9 (the latest available one).

    If you do currently need bulletproof block logging I honestly don't really recommend LogBlock due to its current inability to roll back a handful of blocks and especially their data tags.

    If its a small server and you dont expect major grief to happen until the actual 1.10 update hits you can just throw it on and try it :) It won't break your server to try.

  • Avatar of Chevels Chevels Jul 15, 2016 at 15:31 UTC - 0 likes

    Hello, this plugin does it work in 1.10?

    My server: "Sur les Ruines d' Heavy-Craft" Aka "Heavy-Craft Reloaded", since March 2011!

  • Avatar of J2D2 J2D2 Jun 29, 2016 at 20:11 UTC - 0 likes

    @SureWay: Go

    Are you going to keep updating this plugin ? I do encourage you to do so

  • Avatar of Porama6400 Porama6400 May 15, 2016 at 04:32 UTC - 0 likes

    SQLlite Please

  • Avatar of Rodirik200 Rodirik200 May 10, 2016 at 19:12 UTC - 0 likes

    Hello!

    I will use your LogBlock Logo for a Wiki post is that ok?

    sorry for my bad English im German.

  • Avatar of Renzotoms Renzotoms May 10, 2016 at 16:50 UTC - 0 likes

    Please update for Minecraft version 1.9.4.

  • Avatar of Wicstar Wicstar May 05, 2016 at 23:12 UTC - 0 likes

    Hello, I keep getting this error spamming my log: [18:03:14] [Craft Scheduler Thread - 60/WARN]: Exception in thread "Craft Scheduler Thread - 60" [18:03:14] [Craft Scheduler Thread - 60/WARN]: org.apache.commons.lang.UnhandledException: Plugin LogBlock v1.94 generated an exception while executing task 12 at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoSuchMethodError: org.bukkit.Server.getOnlinePlayers()[Lorg/bukkit/entity/Player; at de.diddiz.LogBlock.Metrics.postPlugin(Metrics.java:324) at de.diddiz.LogBlock.Metrics.access$400(Metrics.java:46) at de.diddiz.LogBlock.Metrics$1.run(Metrics.java:212) at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftTask.run(CraftTask.java:71) at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more

    Any help ?

  • Avatar of Tiippex Tiippex Apr 23, 2016 at 21:30 UTC - 0 likes

    @SureWay: Go

    Page is down :/

  • Avatar of SureWay SureWay Apr 09, 2016 at 14:45 UTC - 0 likes

    @ARX7Arbalest: Go

    Yes, the development build see http://ci.md-5.net/job/LogBlock/changes Build #270

    Last edited Apr 09, 2016 by SureWay
  • Avatar of ARX7Arbalest ARX7Arbalest Apr 08, 2016 at 22:57 UTC - 0 likes

    A little Question is this Plugin compatible with 1.9 ?

Facts

Date created
Aug 24, 2011
Categories
Last update
May 06, 2016
Development stage
Release
Language
  • enUS
License
Attribution-NonCommercial-ShareAlike 3.0
Curse link
LogBlock
Reverse relationships
9
Downloads
448,000
Recent files

Authors