Inactive [INFO/ADMIN] LogBlock v1.54 - Enderdragon Logging! Tree Grow Logging! [1.4.5]

Discussion in 'Inactive/Unsupported Plugins' started by DiddiZ, Feb 15, 2011.

  1. Offline


    Version: 1.50​
    Find and Backroll those Damn Griefers
    LogBlock release are on DevBukkit:

    LogBlock dev builds:

    Please read the installation guide

    I won't port LogBlock myself to mcAPI. Source code is available, so it shouldn't be to difficult for someone else to do it, also I'm still here. so I can answer questions. If there is more than one willing, that's up to you to handle that.

    The reasons I take this step, are the usual: I quit playing Minecraft about 5 months ago and lastly I was struggling to keep up with updates. The developement of Guardian made slow progress, so I fear it won't be ready to fully replace LB in time.

    Download latest dev build: Jenkins
    View the source code: GitHub
    Table of contents:
    1. Description
    2. Features
    3. Why to use LogBlock
    4. Example command
    5. Older versions
    6. Change log
    7. Todo list / feature requests
    8. Permission nodes
    9. Plugins supporting this
    10. Support the dev
    11. How to post error messages
    12. Advertizing

    LogBlock logs block changes into a MySQL database. Block changes can be placed or destroyed block, explosions, burned blocks, sign text changes, chest access, leaves decay etc.
    It can be used as griefer identification tool, to find out who build a particular building, or even roll back changes by certain players. Other purposes can be e.g: Undoing of forest fires
    All additional features are optional, to keep the database as short as possible. All database actions run in their own threads to avoid server lags.
    The use of permissions plugin (or any clone) is possible, but not necessary.
    Uses Spout for chest logging (but it's fully optional, and there is no need for the client mod at all).

    • Logging for block placing, block braking, fire, explosions, leaves decay, signtexts, lava flow and chest content
    • Very mighty commands system, not only allowing to rollback and redo, but also to tp to blockchanges, delete log ingame etc. Full list of commands.
    • Many parameters for lookup/rollback/redo/tp/clearlog commands: Block changes of one ore more player, in a specific area, in a world edit selection, specific block types only, block changes older or newer that a specific date, destroyed/created block only, in a different world and combinations of all these parameters. Full list of parameters.
    • Rebuilding map after importing a backup (/lb redo)
    • Last parameter to use the parameters of the last command
    • Quick ingame lookup of block history a wood pickaxe or a bedrock block.
    • All commands accessible from console (exept tools :D)
    • Custom queries for tools.
    • Different tool modes (lookup, rollback, redo, writelogfile and clearlog)
    • Saves block data like wool color, log type, torch adjustment, etc
    • Multiworld and multiserver support (some servers sharing the same database)
    • BigBrother log import
    • Loggable super pickaxe plugin (not to confuse with WorldEdit's super pickaxe)
    • API
    • Webstats
    Why to use LogBlock:

    Example commands: (thanks to tha d0ctor, read more about commands here)

    /lb rollback player fire since 1d3h – rolls back fire 1 day 3 hours
    /lb rollback player fire since 1d3h area 15 – rolls back fire 1 day 3 hours within a radius of 15 blocks

    /lb rollback player thad0ctor since 1h - rolls back thad0ctor 1 hour
    /lb rollback player thad0ctor since 1d area 5 – rolls back thad0ctor actions for the last day within 5 blocks
    /lb rollback area 10 since 1h30m - rolls back all modifications within 10 blocks since the list 1 hours and 30 mins
    /lb rollback area 10 before 06.11.2011 - roll back all changes in an area of 1o before June 11th, 2011
    /lb rollback player thad0ctor since 05:36:00 - roll back all changes of thad0ctor since 05:36 (server time)

    Download, Command, Configuration and Details:

    -> Full changelog
    • LogBlock v1.50 # 81 (Dez. 13, 2011)
      Works with CraftBukkit 1.0.1-R1
      • Feature: /lb me shows the total block count
      • Feature: Chest logging without spout
      • Feature: Enderdragon logging
      • Feature: Logging for tree and mushroom grow (thanks to MD5 for the api)
      • Fix: Area param works again with default radius
      • Fix: Rollbacks got slowed down a bit to avoid rare server crashes
      • Fix: If mysql username, password or database only consist of unquoted numbers, LB will read them now
      • Config: World configs changed totally, some names changed and all logging options are now in an own section
    • LogBlock v1.41 #63 (Nov. 15, 2011)
      Works with CraftBukkit recommended build #1337
      • Fix: Players with spawnTools permission are no longer allowed to spawn all tools.
      • Fix: Added a check to avoid "The permission xy is already defined!" errors
    • LogBlock v1.40 #60 (Nov. 09, 2011)
      Works with CraftBukkit recommended build #1337
      • Feature: Custom auto ClearLog
      • Feature: Reduced error spam. Instead of like 40 line of error code, there is now just a warning stating the MySQL con
      • Feature: The queue will now be dumped after 10 tries even when the MySQL server is connected
      • Feature: Custom material names, allows naming custom blocks
      • Feature: LogBlock will now respond to messages when started without MySQL connection
      • Fix: Log import runs now async
      • Fix: Log import errors won't crash the server
      • Fix: Console commands work again
      • Fix: You can now use upper case letter in tool names (I don't know why you even should, but ...)
      • Config: Added, clearlog.enableAutoClearlog in main config. Added materials.yml. Removed clearlog.keepLogDays
      • Permissions: Added 'logblock.spawnTools'
    • LogBlock v1.32 (Oct. 04, 2011)
      Works with CraftBukkit recommended build #1240
      • Feature: Player info logging: firstLogin, lastLogin, onlinetime, ip. No ingame lookup yet.
      • Feature: /lb queuesize to see the current queue size
      • Fix: Door logging logs now also fence gates
      • Fix: Bukkit api break in CB #1191
      • Fix: time restriction works now as intended. Thanks to xrobau
      • Fix: Players with insufficient permissions can't smuggle bedrock from one world to another
      • Config: Added logPlayerInfo
    • LogBlock v1.30 (Sep. 22, 2011)
      Works with CraftBukkit recommended build #1185
      • Feature: Chat lookup /lb chat player diddiz search +admin +sucks +dicks (more info)
      • Feature: Door logging
      • Feature: Dynamic tools, define your own tools
      • Feature: Use since and before to define a timespan
      • Feature: Enderman logging
      • Feature: cake logging (who ate it)
      • Config: Added logEndermen, logCakes and logDoors to world config and moved the tool section in main config.
      • Permissions: logblock.tool changed to and
        logblock.toolblock to
    Todo List:

    Permission Nodes:

    Plugins supporting Logblock:
    List (open)

    When you want to appear your plugin here, tell me about

    Support the developer (that's me :D):
    If you want to support me writing plugins or want to thank me for the plugin/support, you can: Suggest features I missed, report bugs (best with fix :D), donate via PayPal, flattr my plugins, gift me The Witcher 2 (thanks to newyoukdaily), 2x 1GB DDR1 modules (thanks to HonestFlames), or send me the inner life of a laptop or netbook with a broken display (need it to build a model aircraft, so there is no need for parts like display and keyboard).


    How to post error messages:

    I won't aswer questions to general MySQL setup/installation/what is MySQL (there are lots of good tutorials out there, use google)
    Please read the installation guide before asking a question about installation problems.
    Please read the FAQ before posting a error report. It may be solved there.
    In case of rollback or lookup problems: Type /lb savequeue and try again (when it's fixed then, it was a consumer problem, see FAQ)
    When you post error messages, it's important to paste the whole stack trace!

    Newyorkdailys Plugin Support Buisness (open)
    Still can't get LogBlock working, or any other plugin? Are you getting errors in your console and cant figure out why? Newyorkdaily offers Basic/Advanced Plugin support.
    • General/Advanced troubleshooting: FREE!
    • Plugin Installations: 1-2 Plugins - FREE!
    • 3 or More Plugins - $2
    Click on the link below to connect to him now!

    There is a LogBlock irc channel: #logblock at
    You can ask me on skype. My name is 'hawky.diddiz'.
  2. Offline


    Your plugin is awesome, just AWESOME :) Thanks a lot for all your work, the redo feature is great. Thanks for having listened to the feature request ! It works great :D

    I would see one more addition that could make it even easier, add a "/lb redo last" command. The plugin would store the last command for the current user in their current session (won't persist after logout) and when using it, it would redo the last "/lb undo *" command used by the user. The "history" queue can, at first, be the only last command, but it could become are real queue, making it possible to redo more than one step (like WorldEdit allows). Right now you have to remember the last command you've used to redo it if you made a mistake, that's feasible but it's not always easy.

    @Nate204: Try to place "bedrock" (block ID #7) ;) You can change this setting in the config file (toolblockID: 7).
  3. Offline


    aaah /undo command, love you :rolleyes:
  4. Offline


    I seem to be having problems connecting to the MySQL database. No matter what I do I can't seem to log in...

    Is my url correct?
    url: jdbc:mysql://

    EDIT: Nevermind, it was an issue with the DB.
  5. Offline


    Good plugin. Superior to BigBrother, also it doesn't cause massive serverwide lag.
    Bravo to you!
  6. Offline


    #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'INSERT INTO `lb-main` (date, playerid, replaced, type, x, y, z)
     SELECT FROM_UNI' at line 7
    why domen name instead of localhost?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 9, 2016
  7. Offline


    Because it's not on a localhost, I'm connecting to a dedicated MySQL server.
  8. Offline


    Have you enabled remote access on remote DB?
  9. Offline


    Thanks :D
    It doesn't? Hm, in that case my script is broken.
    I got a screenshot yesterday, where the player column still exists. I'll check this.
    Hm, I'm not sure what's causing this. The consumer uses result sets unly to get the id from last insert in the main table, when addind signtext or chest access informations. An empty database doesn't cause an error. Did this happen at a random consumer run, or after placing a specific block/sign/chest?

    Try a bedrock block. Or specify another block in config (toolblockid)
    You can append a time.
    /lb rollback player diddiz 999 days
    Huh? I'm quite sure, if LB can log, somewhere the tables must exist. Maybe in an other database? Look what database you specified in the url config entry.
    I'll add an config entry to order the log to the todo list.
    Hm, I was alredy thinking about something like that, but I forgot it some how. Goes to the todo list :D
    Hm, that's from the bb->lb converter? I'll have to have a closer look at it.
  10. Offline


    Cool job on this plugin. I'm coming from BigBrother due to its lack of updates on the 1.4 changeover.

    Any chance you can add a function for mods to spawn the logging items? At the moment we don't give our mods the ability to spawn items so they will have to make the specified tool every time they want to check something. This also means the block item is out of the question.

    Something like '/lb tool' would give you the specified tool item and '/lb block' would give you the specified toolblock. This would preferably be controlled by a permission setting such as 'logblock.tool' to prevent users from spawning blocks willy nilly.

    Really good job and thanks for picking up the slack from bb. I hope you can deal with the influx in users well :)
  11. Offline


    Hm, of course. Wonder why I didn't thought of that. The code I've alredy in MT, so this will be in next release.
  12. Offline


    Hi, I have a question regarding setting LogBlock up and running. My "world" directory is one up from the server directories (of which I have many, since I don't want to delete the old ones):

    So, for all my servers, I only have one world directory, not a different one under every server directory.

    This works fine, when I just specify in my, using relative directory, "level-name=../world".

    How do I set this up in LogBlock so that it will find my world directory? Same way?
  13. Offline


    Not the path, only the name is relevant. I'll specify this in the installation guide.
    - world
  14. Offline


    Getting an error occured after I connected and disconnected instantly after.
    It spams this repeatedly and when I stop the server it freezes.

    CB 617 - LB v0.11
    06:04:02 [SEVERE] [LogBlock Consumer] SQL exception
    com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Connection.close() has already been called. Invali
    d operation in this state.
            at sun.reflect.GeneratedConstructorAccessor40.newInstance(Unknown Source)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
            at java.lang.reflect.Constructor.newInstance(Unknown Source)
            at com.mysql.jdbc.Util.handleNewInstance(
            at com.mysql.jdbc.Util.getInstance(
            at com.mysql.jdbc.SQLError.createSQLException(
            at com.mysql.jdbc.SQLError.createSQLException(
            at com.mysql.jdbc.SQLError.createSQLException(
            at com.mysql.jdbc.ConnectionImpl.getMutex(
            at com.mysql.jdbc.ConnectionImpl.setAutoCommit(
            at Source)
  15. Offline


    Awww, nullpointer check wasn't enough. Will add a check for closed connections.
  16. Offline


    S**t, I wrote "- ../world" and everything worked fine. Now I changed it into "- world" and LB gives me "this world isn't logged". I wonder what's in my MySQL tables now...this might get interesting...

    Do I need to delete all lb- tables from my database and start again?
  17. Offline


    huh? Hm, let me run a local test.

    So. Didn't expect this behavior. You were right, it has to be "- ../world". I'm sorry. Nothing happened to your tables, change the config entry and al should work fine.
  18. Offline


    If I set toolblockid to 0, will it just stop working (or will it still check when I have nothing in my hand)

    Also, you should add a radius block tool to inspect blocks like you would /lb area

    One more request: Stop zipping the jar files when you upload them >.< :D
  19. Offline


    Also I get this in MySQL when trying to view my lb-main table:

    mysql> select * from;
    ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right synta
    x to use near '-main' at line 1
    So I guess my MySQL version doesn't like the "-" in the default table names? The same select statement works fine for a table like "iconomy".

    Also MySQL doesn't let me drop the tables, for the same reason. I'm in trouble now - does anyone know what syntax to use for tables named like "lb-main"? Because the hyphen there is giving me s**t.
  20. Offline


    Wow, didn't even thought about that. Will add a check.
    Good idea, indeed.
    Try "select * from minecraft.`lb-main`;"
    You've to use backticks.
  21. Offline


    OK, I was able to drop the tables now. How about not by default using the hyphens in table names - they are a big No-No in MySQL!

    And, regarding my other problem: "- world" always gives me "this world isn't logged" now, even if I deleted everything and restarted from scratch. But if I once again change it into "- ../world", everything works. So yes, the relative path DOES seem to matter, in case the world dir isn't directly under my server dir.
  22. Offline


    Not if you are backticking everything properly.
    You hadn't do delete anything. And yes, the relative does matter, like I said before.
    Updated BB->LB converter.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 9, 2016
  23. Offline


    OK, I missed that since you edited the post. But everything at least is working now, which is great.
  24. Offline

    tha d0ctor

    anyone notice any increased lag when using this?
  25. Offline


    Is there any way to check area instead of just specific block with wooden pickaxe? If greifer destroyed a block, i could just click on nearby block. But now i have to place a new block on the place of old to log.

    Also, can you make logs go away after X entries? So it will hold only last 5 entries of specific block.
  26. Offline


    That's the main thing.
    No :D
    Try the bedrock block.
    Hm, maybe. I'll see whats possible.
  27. Offline


    I'm trying to do the BB->logblock conversion but i keep getting this:

    whenever i do any of the conversion queries. Any ideas?
  28. Offline


    It seems you map is larger than 64k blocks diameter?
    You have to change the data type of the colums x and z to MEDIUMINT or INT.
    It's explained more detailed in the installation guide.
  29. Offline


    I want my players to check griefers themselves. But i don't want to give bedrock to them.

    And bedrock block would be kinda hard to get back after checking for griefers.
  30. Offline


    Yeah our map is huge :p Thanks for that :)
  31. Offline


    Bedrock blocks are removed after checking.
    Anyway you could specify another block in config (toolblockID)

Share This Page