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

    Simon Welker

    Would be cool. :>
  3. Offline


    I don't have access to do that on my remote db server. What about the local error?
  4. Offline


  5. Offline


    So whats the word on using this on a system using Linux? it uses the CLI. If you could, could you make a tutorial for Linux that would be greatly appreciated.
  6. Offline

    Simon Welker

    Thanks man! But I think it's not working... Have you tried it out? For me, no lb entries appear if someone else or me eats the cake. :/
    -- could it be that it has to be enabled in the config? I'ma try that.
  7. Offline


    Ouch... I cant do that heh
  8. Offline


    Yes, you have to :D
  9. Offline


    its not logging chests on my world anymore. why would this be? everything is updated!
  10. Offline


    I get spammed with this error EVERY time I try to enable LogBlock, usually after an hour or so of it running:

    2011-09-06 17:04:37 [SEVERE] [LogBlock Consumer] SQL exception on INSERT INTO `lb-main` (date, playerid, replaced, type, data, x, y, z) VALUES (FROM_UNIXTIME(1315346499), 8, 0, 280, 0, '1121', 85, '566');:
    com.mysql.jdbc.MysqlDataTruncation: Data truncation: Out of range value for column 'type' at row 1
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(
        at com.mysql.jdbc.MysqlIO.sendCommand(
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(
        at com.mysql.jdbc.ConnectionImpl.execSQL(
        at com.mysql.jdbc.ConnectionImpl.execSQL(
        at com.mysql.jdbc.StatementImpl.execute(
        at com.mysql.jdbc.StatementImpl.execute(
    It'll go away if I delete all the tables and start over, but it inevitably starts again not long after
  11. Offline


    Tried "/lb savequeue"?
    This error causes no harm at all. Ignore it, or update to dev build #14+, it's hidden there.
  12. Offline


    didnt help

    Okay new problem. When i log a chest it doesnt say when people stole items. even on a fresh install with chest logigng enabled. It logs it when I destroy a chest and if i right click the top it says unspecified actions took place.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
  13. Offline


    Sounds odd. Maybe using an older spout version?
    Does it log the content when you brake a filled chest?
  14. Offline


    Yes, It does. I am on spout 1.0.5.xxxx
  15. Offline


  16. Offline


    Can anyone give me his config.yml? when he edits it..cause my sql server does not work!!
  17. Offline



    Is there any fix for the "unspecified action" problem? Logblock is having problems with this and stuff isn't being rolled back
  18. Offline


  19. Offline


    LB can only log what it gets. Under some circumstances bukkit provides no block type.
    Oh, bad to hear
  20. Offline


    Could the Ore to Client obfuscation plugin be causing this?
  21. Offline


    Could be, this needs some testing.
  22. @DiddiZ
    When looking up chest log, how do i filter specific items or taking out or putting in only?
  23. Offline


    type dirt stone
    taken/put isn't supported atm
  24. That only seems to work for placed/removed blocks and not type of blocks in/out of chest. Atleast its not working for me with v1.26
  25. Offline


    You have to use it together with chestaccess parameter, like
    /lb player diddiz chestaccess type diamond
  26. Ah yes, that works great. Thanks
  27. Offline


    How come my logs get cleared out every time my server restarts? This makes it very difficult for us to track any griefers. :(

    - naturautopia
        port: 3306
        host: xxxxxxx
        password: xxxxxxxx
        user: xxxxxxxxx
        database: xxxxxxxx
        logCreeperExplosionsAsPlayerWhoTriggeredThese: false
        logKillsLevel: PLAYERS
        - dmansinful
        - 0
        dumpDeletedLog: false
        keepLogDays: 4
        askRedos: false
        askClearLogs: false
        askRollbacks: false
        askClearLogAfterRollback: false
        - 8
        - 9
        - 10
        - 11
        - 51
        - 10
        - 11
        - 46
        - 51
        maxTime: 4 days
        maxArea: 250
        delayBetweenRuns: 6
        forceToProcessAtLeast: 25
        timePerRun: 100
        useBukkitScheduler: true
        toolID: 270
        toolQuery: area 0 all sum none limit 15 desc silent
        toolblockID: 7
        toolBlockQuery: area 5 all sum none limit 15 desc silent
        defaultDist: 20
        defaultTime: 30 minutes
        linesPerPage: 15
        linesLimit: 1500
    version: '1.26'
  28. Offline


    You have set the log to be kept for 4 days. Increase that, or disable auto clearance (set keepLogDays to -1) and delete the log manually "/lb clearlog before 4d".
  29. Offline


    Is there anyway to find the IP of the player who broke the block? E.I. "Someone's account was hacked, therefore it was not them who committed the griefing/damge/etc""
  30. Offline


    It's a common excuse, but no, ip aren't logged yet.
  31. Offline


    By you saying "aren't logged yet" I'm assuming its planned?

Share This Page