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 maw_a_timewalker maw_a_timewalker Feb 06, 2016 at 11:02 UTC - 0 likes

    @pepper82: Go

    no not in "everyday" use

    it can happen that it takes a lot of resources, but thats only if you enable worldedit logging, and someone does >1.000.000 blocks changes, then logblock will read all the logging info into memory and send it slowly to the SQL server

    Hey hey hey LOOK my server :3 Right ... HERE :D

  • Avatar of maw_a_timewalker maw_a_timewalker Feb 06, 2016 at 11:00 UTC - 0 likes

    @unclemark: Go

    Hey

    You can edit how logblock shows the date, in logblock config find
    lookup:
    dateFormat: MM-dd HH:mm:ss

    and change it to something like
    lookup:
    dateFormat: YY-MM-dd HH:mm:ss
    and it will only show the 2 last number of the year (14-15-16)

    or do
    lookup:
    dateFormat: YYYY-MM-dd HH:mm:ss
    then it will show the "full" year :3 (2014-2015-2016)
    i would recommend this one, as it is easy with the top one to confuse the year with the day.

    you can also mess around with the date display and add it in any order you want

    Last edited Feb 06, 2016 by maw_a_timewalker: looked derpy
  • Avatar of pepper82 pepper82 Feb 04, 2016 at 16:49 UTC - 0 likes

    Isn't this plugin a performance eater?


    German Minecraft Server [RPG][PVP][SURVIVAL][+MANY FEATURES]
    Minecraft RPG Survival PvP Server

  • Avatar of unclemark unclemark Dec 01, 2015 at 09:04 UTC - 0 likes

    year - feel free to consolidate this. I'm sorry but I can't look up grif from last year or 2 years ago - because it has no date (as in YEAR)

  • Avatar of unclemark unclemark Dec 01, 2015 at 09:02 UTC - 0 likes

    and if I'm lucky enough to live hundreds of years, don't make the year xx .. make it XXXX 2015 2101 2558 8192

    hmmm

    Anything over a 9999 year calendar is too soon to call. Please add a date specifier to logblock lookup , rb etc

  • Avatar of unclemark unclemark Dec 01, 2015 at 08:59 UTC - 0 likes

    add a frikken year specifier to the date lol - no - whatever

  • Avatar of unclemark unclemark Dec 01, 2015 at 08:55 UTC - 0 likes

    The only thing that absolutely sucks like ass lips is that 2014 is missing 2013 is missing 2012 is missing 2011....

    I do logblock tool and it's retarded

    the date says 3-16 !!!!!!

    lol

    3-16 2015 , 2014 2013 2012 2011 ????

    ????

    03-16 takes the same characters as 31613

    except it has no year

    lol

    loooooooooooooool

    Omg

    sorry

    I just finally had to post this since it hasn't been corrected, EVER !!!

  • Avatar of FlashLight32 FlashLight32 Oct 11, 2015 at 23:34 UTC - 0 likes

    we need a logger for armor stand any way to make this?

  • Avatar of Dillzzzzz Dillzzzzz Sep 12, 2015 at 11:18 UTC - 0 likes

    can this find out who last touched a block? Coreprotect is mad for me, I just don't like it as SQL doesn't seem to work and the worldedit version is messing on it.

    Havoc OP PvP Banner

  • Avatar of scuroK scuroK Aug 22, 2015 at 09:29 UTC - 0 likes

    thanks for keepkng logblock updated! <3

Facts

Date created
Aug 24, 2011
Categories
Last update
Jul 25, 2015
Development stage
Release
Language
  • enUS
License
Attribution-NonCommercial-ShareAlike 3.0
Curse link
LogBlock
Downloads
426,315
Recent files

Authors