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


    Hm, that message is rather pointless, when I forget to display the pw -.-
  3. Offline


    Hm, I have a requested feature. I think it would be very helpful if when you rolled back changes someone made, it deleted those logs from the sql database. I find it a bit annoying that even when I rolled back something, it still shows it in the database. Another thing that I noticed is that if for example, you have a wood house, and someone places lava near it, that causes everything to burn down, you cannot rollback the burnt wood. You could possibly fix this by checking blocks near lava and/or fire using world edit, then just replacing them when a rollback happens.
  4. Offline


    Thanks, any ETA on this exciting new cmd system? :D

    PS: I switched from BB, it seems like they are losing their touch >.>
  5. Offline


    Hm, yup, comes to the todo list. Like a question after finishing rollback whether everything rolled back properly and do you want to delete the log, so there is a chance to redo.
    Huh? The wood blocks should be logged, like any burned blocks. Do you have logging.logFire enabled?
    Hm, I'll try to release a preview this weekend. There will be a decent amount of bugs, since the query generation is a bit complex.
    Yup, it's getting quiet about bb.
  6. Offline


    should I wait for .16? sad part is 2 days without this plugin and already we have had 3 griefing incidents..... and BB went down for the count long time ago.... so no alternatives....
  7. Offline


    Can you contact me on skype? Makes asking faster.
  8. Offline


    done :) thanx.
  9. Offline

    Jake Rees

    i keep on getting this error message

    01:28:13 [SEVERE] [LogBlock] Exception while reading config:
    java.lang.Exception: worldNames or worldTables not set porperly
            at de.diddiz.LogBlock.Config.<init>(
            at de.diddiz.LogBlock.LogBlock.onLoad(
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(
            at net.minecraft.server.MinecraftServer.e(
            at net.minecraft.server.MinecraftServer.a(
            at net.minecraft.server.MinecraftServer.init(
  10. Offline

    Nathan C

    Well, the Logblocks database finally reached 513,000 rows.

    Problem is that there is now massive chat delay. There is no abnormal or high CPU or RAM usage.

    It is just simply chat delay. No "Can't Keep Up" messages either!

    Removing this plugin fixes it. Is this a limitation by this plugin, that it will lag after that many rows? I had BigBrother with over 2 million, and it worked fine.

    Note, I have restarted both the server and clients multiple times. The chat is delayed and many other users report it. The chat shows in console, but it will not appear on the server for a long time..
  11. Offline


    Well, show me your loggedWorlds and tables. According to the typo you are using an older LB version.
    Hm, that's new to me. I've 1.5 mio rows and no problems, I also heard about some guy with 30 mio rows. The only I can imagine, is that the consumer works very slow for some reason or blocks the bandwidth (when using a remote mysql server). In first case it could help to lower the cunsumer.minCountPerRun to 0.
  12. Offline


    Are there any known plugin conflicts? I'm having an issue where logblock builds up a massive queue over some number of hours, and then only gets rid of it when I stop the server. Just now I shut it down after it had been running about 14 hours (with 50 players) and the queue was 190,000. It's still counting down as I type this...25k....15k....yeah. No idea why it's acting this way.
  13. Offline


    Me too, but it helps to disable consumer.useBukkitSchduler.
  14. Offline


    Ah, of course. Thanks.
  15. Offline


    State of the new commands system: 80%
    The new commands system will allow flexible commands with the paramers:

    • player - list of one or more players
    • area - followed by the radius
    • selection - the current worldedit selection
    • block - list of block types to show
    • created, destroyed - show only created or destroyed blocks
    • time - like the current time format
    • since - a date maybe "12.04.11"
    • limit - how many rows to show
    • sum - none, players, blocks - the summarization like current area or play command
    • world - will allow lookup, rollback commands from console or a different world
    • asc, desc - change the order of displayed log
    Alredy working:
    • Normal lookup
    • most parameters
    • writelogfile
    • sum blocks (including /lb me)
    Not working:
    • tp commmand (teleports to the result of a lookup)
    • rollback/redo
    • last parameter (stands for the parameters of the last lookup)
    Not implemented:
    • Binding querys to tools
    • option to delete log after rollback
    • confirmation quertion to rollbacks/redos
    • since parameter
    • additional syntaxes for time parameter
  16. Offline


    Some of those features/commands sound excellent. You're doing great work with this plugin!
  17. Offline


    My server is pretty big (100+ players online at all times.)

    and whenever I stop the server it's like this:
  18. Offline


    When it spams "queue overloaded" before shutdown work on your consumer settings, when not, set useBukkitScheduler to false.
  19. Offline


    why i'm forced to do a reload for lookup ?

    (action before i reload i can't see, after reload i can ?!)

    PS : Sorry for my bad english, i'm french.. :3
  20. Offline


    Hm, well, what exactly does lb say before reload (even in the console)? Some more informations about your setup would be helpful.
  21. Offline


    mhh, it says nothing, but how can i make the refresh of the MySQL DB by LogBlock more fast ? (every 10secs will be great ?)
  22. Offline


    When you mean consumer.delayBetweenRuns, it's default 6 seconds.
  23. Offline


    Is this plugin logging and rollbacking chest content like BB ?
  24. Offline


    No, don't like the hacky and insecure way BB it does. When 2 players open the same chest, there is no way to tell who did what.
  25. Offline


    Yes, but it's very cool to rollback the content of a chest.
  26. Offline


    Indeed, and I will add full chest logging as soon as I encounter a good solution.
  27. Offline


    User has a huge tree built by logs. He then added leaves by hand a long time ago. I think before we had leaf decay working or something. when we burn down the tree and logs, the leaves come back but start decaying immediately. Any ideas to fix? or is this just a minecraft thing.
  28. Offline


    Hm, you could use plugin to disable leavesdecay.
    The fire most likely triggered the leaves decay, and since I also rollback the blocks data, the decay bit flag is still set. Not that good, will remove that flag soon.
  29. Offline


    Could you please add coordinates to the logfiles? One of my players is using flint and steel but I don't know where!
  30. Offline


    The new commands system will solve your issue:
    /lb tp player firebug block fire created
  31. Offline


    Could you add to the OP, your website, or GitHub specifications for the database tables. Playerids and xyz are pretty obvious but "replaced, type, data" are a bit obscure. Thanks :)

Share This Page