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 ProjectInfinity ProjectInfinity Aug 03, 2012 at 23:23 UTC - 0 likes

    Is the log clearing feature ran in server thread or in it's own thread? I am getting insane lag after log clearing, especially after chest logs being cleared.

    I have been trying to get hold of you guys on IRC a few times now without much luck.

    http://pastebin.com/5rxrK0KJ

    Can setting useBukkitScheduler to false help against this?

  • Avatar of jamietech jamietech Aug 03, 2012 at 09:30 UTC - 0 likes

    @mailleweaver: Go

    Read the configuration section on the wiki, the installation section doesn't exist.

    @SuperPyroManiac: Go

    This is currently not built into Bukkit.

    Signature

    BFAK:jamietech,23764,cf2d38ccf0feb4785c6942aa9b69354231d6119b9abeba86238fdc0c2c155e7f

  • Avatar of md_5 md_5 Aug 03, 2012 at 07:20 UTC - 0 likes

    Yes I know Inventory logging is broken, Bukkit fix has been prepared and waiting approval.

  • Avatar of mailleweaver mailleweaver Aug 03, 2012 at 00:31 UTC - 0 likes

    Are there installation instructions anywhere? Clicking the above link (to https://github.com/LogBlock/LogBlock/wiki/Installation) just takes me to a page that says I'm not allowed to edit the wiki. And I don't see "Installation" listed on the pages tab in the wiki.

  • Avatar of thernztrom thernztrom Aug 02, 2012 at 21:12 UTC - 0 likes

    @md_5: Go

    woop woop. Good work!

  • Avatar of SuperPyroManiac SuperPyroManiac Aug 02, 2012 at 18:15 UTC - 0 likes

    Cant wait for physics logging, as someone came into the creative world and used the falling gravel to ugly it all up, lucky no one builds with gravel and WE could take it out.

    http://i1196.photobucket.com/albums/aa406/awesome130/Untitled_zps932188e4.png

  • Avatar of Digitalink2008 Digitalink2008 Aug 02, 2012 at 17:07 UTC - 0 likes

    So very glad to see Logblock is alive and well :) Thanks much to the Devs that keep it going.

  • Avatar of md_5 md_5 Aug 02, 2012 at 09:27 UTC - 0 likes

    I'll post it at the top of this and I'll post it again, LOGBLOCK WORKS FINE FOR 1.3 IT WILL UPDATE ASAP IF ANY NEW ISSUES ARISE.

  • Avatar of jamietech jamietech Aug 01, 2012 at 23:22 UTC - 0 likes

    @mprasolov: Go

    Tickets are actually at https://github.com/LogBlock/LogBlock/issues WorldEdit is also not logged currently, so I don't know why your queue is getting large but please view the Commands section on the wiki.

    @Ovelite: Go

    Please read the Configuration section on the wiki.

    @TigerXtrm: Go

    1) This is configurable. 2) Install the LogBlock Questioner for these features to work, or disable the questioning in the configuration. (Configuration available on the wiki)

    @andrewkm: Go

    http://ci.kitteh.org

    @rodier: Go

    This is a MySQL logging plugin, if you do a simple Google search I'm sure you'll find some free MySQL hosting. (Or your current server host may offer it free of charge)

    @Jackrushton: Go

    I'm not completely sure what you mean by this. Would you care to elaborate, please?

  • Avatar of Jackrushton Jackrushton Aug 01, 2012 at 13:57 UTC - 0 likes

    Hey any chance of this updating within the next couple of days>

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
337,710
Recent files

Authors