LogBlock

LogBlock logo

Works 100% with 1.7.2

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 Chevels Chevels Jul 23, 2014 at 20:39 UTC - 0 likes

    @pookshuman: just loaded chunks are rollback. You've to repeat command multiple times at differents place in larges zones. It seems to rollback a radius of 128 or 200 blocks

  • Avatar of gdude2002 gdude2002 Jul 12, 2014 at 13:59 UTC - 1 like

    This works on 1.7.9 but badly needs an update to support the new UUIDs. It shouldn't even be that huge of an edit. But it's definitely an important one.

    Owner of The Archives

  • Avatar of chozo4 chozo4 Jul 12, 2014 at 09:30 UTC - 0 likes

    @151baccardi: Go

    Try changing the following in the config.

    banPermission: mcbans.ban.local

    and set the ban permission to something different then don't apply the permission to anyone at all. We've never been questioned this after a ban and never had any rollbacks post-ban as we never gave this perm.

  • Avatar of 151baccardi 151baccardi Jul 12, 2014 at 05:56 UTC - 0 likes

    Omg. The horror. If staff decided to go on a banning spree, and logblock rolls back all player builds, the server will be brand new again and completely erased !! Nice plugin. I cannot find a setting in the config to not do rollbacks after bans. Even with the questioner installed, staff can still type /yes and ruin everything !! Please, does anyone know how to turn OFF this horrific feature of rolling back after a ban ?? I don't even wanna see the question to roll back. People can buy an unban or do a ban appeal. If all their stuff is gone (even after a legitimate ban), what good is logblock if logblock is actually a server destroyer in disguise ?!

    Last edited Jul 12, 2014 by 151baccardi
  • Avatar of apesgrapes apesgrapes Jul 05, 2014 at 11:52 UTC - 0 likes

    @XeonG8: Go

    yes, works fine on 1.7.9.

  • Avatar of pookshuman pookshuman Jul 02, 2014 at 00:18 UTC - 0 likes

    If I do a rollback, should it work on unloaded chunks or just loaded chunks?

  • Avatar of XeonG8 XeonG8 Jun 30, 2014 at 22:40 UTC - 0 likes

    anyone using this on 1.7.9?

  • Avatar of scuroK scuroK Jun 29, 2014 at 12:43 UTC - 0 likes

    THANKS LOGBLOCK I LOVE YOU :D

  • Avatar of ArsenArsen1 ArsenArsen1 Jun 28, 2014 at 09:35 UTC - 0 likes

    It need to update to UUID and how to store to flat file

    BFAK:90959439,01a95dd15008184aff20c1e93bd46624c87863eb3ecdb08fb564c17b1219423b

  • Avatar of mmuziek mmuziek Jun 19, 2014 at 07:36 UTC - 0 likes

    i think this plugin needs a update to support uuid

    otherwise people just change name so you cannot rollback their actions and have to search whats theirs and such

    soo it really needs the update

Facts

Date created
Aug 24, 2011
Categories
Last update
Dec 05, 2013
Development stage
Release
Language
  • enUS
License
Attribution-NonCommercial-ShareAlike 3.0
Curse link
LogBlock
Downloads
355,435
Recent files

Authors