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 rustyshakelford2 rustyshakelford2 Dec 16, 2014 at 18:24 UTC - 1 like

    LogBlock saved my world. We lost our recent backups at the same time something corrupted our world. I restored a month old backup and did a LogBlock redo and things were almost exactly as we left them. I love this plugin.

  • Avatar of andrewkm andrewkm Dec 15, 2014 at 09:53 UTC - 0 likes

    Can confirm LogBlock working great on Spigot 1.8

  • Avatar of FlyingSpaniard FlyingSpaniard Dec 13, 2014 at 17:26 UTC - 0 likes

    Seems like the new doors are indeed not logging. Oak doors work fine, however

  • Avatar of Jewremy Jewremy Dec 13, 2014 at 09:58 UTC - 1 like

    Block places, breaks, etc are logging just fine (even with the new blocks). It's door interactions that aren't logging properly. Specifically, the new doors. Old (oak) wood doors work great, as usual.

    Last edited Dec 13, 2014 by Jewremy: clarify doors
  • Avatar of xDeeKay xDeeKay Dec 10, 2014 at 19:55 UTC - 0 likes

    @aussie1579: Go

    They actually are being logged. Every block within LogBlock is logged by it's ID, however the names you're seeing when using the lookup tool are simply the names given to the block at the time of LogBlock's version. For example, when using the lookup tool on something like granite, it should be displayed as stone, because granite has the same ID as stone (0), just with a different block data (1 and 2). I hope this helps you understand a little more.

    You can change the names of blocks in materials.yml

    BFAK:90614316,98a3e7bd1eb1489efacfa4a0dabfaf4996c873ef38e8a420fab31bf03f78f7ac

  • Avatar of aussie1579 aussie1579 Dec 08, 2014 at 16:06 UTC - 0 likes

    @Schneidertm: Go

    not from what I have seen, vast majority of the newer blocks are simply not logged.

  • Avatar of Schneidertm Schneidertm Dec 08, 2014 at 12:37 UTC - 1 like

    @aussie1579: Go

    The new 1.8 blocks and the banners are logged. I don't understand why so many people want an update. May a Uuid update, but I think it isn't necessary.

  • Avatar of aussie1579 aussie1579 Dec 07, 2014 at 01:00 UTC - 0 likes

    @lme999: Go

    besides the new blocks not being logged? it works

  • Avatar of lme999 lme999 Dec 06, 2014 at 03:33 UTC - 0 likes

    Have any of you tried using LogBlock on Spigot 1.8? From what I've tested it seems to work perfectly..

    Last edited Dec 06, 2014 by lme999: Reply didn't work.

    === I'm looking for a private plug-in developer for my server. Interested? PM me! === craftingcrafter.com Hybrid Minecraft Mini-games server.

  • Avatar of raphy123 raphy123 Dec 03, 2014 at 18:58 UTC - 0 likes

    Hi :)

    Yes an update for spigot 1.8 may be cool :)

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
373,968
Recent files

Authors