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 benneht benneht Apr 15, 2014 at 20:22 UTC - 1 like

    I feel like md_5 holds like the entirety of bukkit on his shoulders.

    Looking for some help with coding, have a lot of great ideas, but not the time nor manpower to complete them all. Shoot me a message.

  • Avatar of BSigil BSigil Apr 12, 2014 at 19:11 UTC - 0 likes

    With the 1.7.8 update, Logblock seems to be completely gorked. It's not logging player changes, and the things it does log (TNT explosions) won't rollback. Is there something I can do on my end to fix this, or do I just have to wait for an update?

    EDIT: My mistake. I don't know what happened with my initial test, but it's logging things just fine, it seems. Still no rollbacks, though.

    Last edited Apr 13, 2014 by BSigil
  • Avatar of jamietech jamietech Apr 10, 2014 at 06:57 UTC - 1 like

    @Darunia18: Go

    There is an active discussion in the GitHub issues which anyone may join.

    Signature

    BFAK:jamietech,23764,cf2d38ccf0feb4785c6942aa9b69354231d6119b9abeba86238fdc0c2c155e7f

  • Avatar of Willcomputerguy79 Willcomputerguy79 Apr 10, 2014 at 05:36 UTC - 1 like

    @Darunia18: Go

    The thought of Mojang actually allowing name changes scares the crap out of me, to be honest. And if this really is going to happen, then I ask the same :) I hope LogBlock devs can keep up the great work and somehow make it work with the new name-change update.

  • Avatar of Darunia18 Darunia18 Apr 10, 2014 at 02:13 UTC - 0 likes

    Just a general question I'm asking developers of plugins I use: have you started looking into the username changes/UUID issue, and figuring out ways to convert the old system to the new, etc? I'm trying to get ahead of the game and make sure all our plugins and our MySQL database is prepared for when they flip the switch and activate name changes. Thanks for all the hard work you put into LogBlock! Keep up the great work!

    BFAK:90832957,00e53379dae8d56339909696136e7bf1c929a5029f865aa205d24b9bb604fe47

  • Avatar of XxGurleenxX XxGurleenxX Mar 29, 2014 at 11:23 UTC - 1 like

    @mantoko: Go

    Yes it logs it in LB Chat which you can use:

    /lb chat player <name> [<time>]

    You must have chat logging enabled in your Logblock config

    @DrunkFLG: Go

    You'd get more help following this:

    "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."

    Last edited Mar 29, 2014 by XxGurleenxX
  • Avatar of mantoko mantoko Mar 23, 2014 at 06:22 UTC - 0 likes

    Does the plugin log player commands ?

    You are searching for good hosting why don`t you try http://enderhosts.co.uk/index.php.

  • Avatar of DrunkFLG DrunkFLG Mar 21, 2014 at 00:50 UTC - 0 likes

    So I've recently installed logblock onto my FTB unleashed server (version 1.5.2 if that matters). I connected the mySQL database and added the world names into the config file as stated but whenever I try to do anything logblock related the chat will state that this world is not logged. Certain commands such as /lb tool will return a internal error message. Any way to fix this?

    Edit: Forgot to add, I'm using version 1.80 of LB. Also, since the FTB unleashed modpack adds in extra dimensions such as the twilight forest I'm also finding that logging those worlds doesn't work either. Using /lb world DIM1 will simply return a "this world does not exist" error.

    Last edited Mar 21, 2014 by DrunkFLG
  • Avatar of 65Wolf 65Wolf Mar 19, 2014 at 22:27 UTC - 0 likes

    Running CB 1.7.2 r. 0.4 (dev build 3023) adn using Logblock v 1.80.

    For some reason, all my players are getting access to the gold pick to use for the logblock tool. They do not have permissions giving. The only people with that permission (or any logblock permissions) are my Mods/Admins. Is there a known bug that is allowing all players to have access to this tool?

    Last edited Mar 19, 2014 by 65Wolf
  • Avatar of Max_Coffeebreath Max_Coffeebreath Mar 19, 2014 at 17:23 UTC - 0 likes

    Is there a way to look up sign text?  I know that it is being logged to database but haven't been able to find any way to look it up (other than to go poking around in my database).

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
336,052
Recent files

Authors