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


    Maybe, if I get the time ...

    Yes, I put that on the todo list.

    I'm quite sure, your database istn't really called "db".
  3. Offline


    Well, I set it up. It properly logs stuff, however when I try to do
    /rollback Skilinium 99999

    It says

    Rolling back Skilinium by 0 minutes.
    Edit count: 0

    Even if I have edited the things within the same minute.
  4. Offline


    type /rollback Skilinium 99999 days
  5. Offline


    Hmm, that looks like it works, however.
    It only removes the block that I created and not the blocks that I deleted.

    Edit: I just checked, it doesn't log the bricks that have been removed.
  6. Offline


    You don't have to use the console to configure it, but it's actually harder to setup remote access (securely) and get a GUI working with it IMO.

    Before creating a table you must create a database and tell MySQL to use that database.
    So you would do:
    ->create database minecraftDB;
    ->use minecraftDB;
    ->create table table1

    The database and table names are whatever you've setup on your server obviously.
  7. Offline


    I suppose you're right - in the config I removed db - now it doesnt error but I dont think the plugin is working at all. I'm very new to mysql - is there a way I'm suppose to manage this and create that correct 'db' ?
  8. Offline


    You'll have to create a database for minecraft on your MySQL server, the name of the db you enter where you just removed "db"

    I'll look at this
    Edit: No problems with bricks

    btw: With next update flint and steel setted fire will be logged
  9. Offline


    Hey thanks for porting this, I will check my old database ;)
    But I love the new radius rollback from BB, would be awsome you could implement this, it's extremely advantageous!
    --- merged: Feb 16, 2011 10:06 PM ---
    Oh, there's an conflict with BB!

    LB and BB have different DBs, now If I start my Server, BB want to connect to the same Database(Not table) as LB. Why, because the use the same java connector?

    My old LB db works ;)

    Yep, it logs bricks, creating and destroying!
    --- merged: Feb 16, 2011 10:24 PM ---
    A bug with rails:

    cb #328

    It doesn't log, if I destroy the block with iStick or a similar tool.
  10. Offline


    Ouh ... hard to imagine, I'll have to get BB to run to check this.

    Yes, and it probably never will

    lol, that looks amazing. Edit: But this isn't caused by LB
  11. Offline


    Bukkit has no hook for this? Would be intelligent, because the logging of some hacked clients!

    Meanwhile we are relative powerless against those hacked clients
  12. Offline


    That are two different things. Plugins like WorldEdit, iStick or VoxelSniper place/drestoys the bloks direct without triggering the blockPlace/Break event.
    The client can't modify the map directly.
  13. Offline


    @DiddiZ is there any imprvements in performance area? I still worry of running this with 60 players running around the map. I even still think lags my server now and I'm using 1.1. Not sure if you improved it or maybe it can't be improved or maybe it does not need it maybe it's fine.

    Any comments on this be great :) I'm a pussy for performance hehe
  14. Offline


    The SQL part is mainly untouched from original LogBlock. It shouldn't lag that much. I can't say that for sure (my server has a peak of 11 players).
  15. Offline


    Okay thanks. I kind of get worried I wish there was ways to benchmark things like this hehe.
  16. Offline


    MM couse the "Problem: Track Direction Modification (Use a wooden pickaxe on track to change it's direction)

    It's not LogBlock!
  17. Offline

    Michael Murphy

    can you make the chatspamming *A block has been destroyed* message optional via config please :p
    Thankyou for releasing this btw ^___________^
  18. Offline


    When I get our mysql sorted out ill be testing this out as well.
  19. Offline


    There is no mesage like this ...
  20. Offline


    I had this before because of that dropchest plugin.
  21. Offline


    mh its working good for me but he dont add a created sign in the database xD only a destroyed.
    Give it a change to add the Sign Create log into the database?
  22. Offline


    Updated to vo.3
    (see the changelog)

    Also fixed
  23. Offline


    Do I have to use some special bukkit launcher to use MySQL or just installing MySQL to Ubuntu?
  24. Offline


    You just have to have a MySQL server
  25. Offline


    That easy? Nothing more?
    How much does MySQL eat RAM? I just have 70mb - 100mb free space on my VPS.
  26. Offline


    I am in no way questioning your coding ability but kind of curious. Did you put in a random check for when the garbage collector should run?

    For example:

    Have a variables that looks something like:

    gc-percentage: 0.1
    gc-max-runs: 30000

    What these would do is to setup the basics (that I can remember as I am doing this off the top of my head) of a GC system.

    gc-percentage says: out of all the times the system updates the db 10% of the time it should check to see if there are records to be removed.
    gc-max-runs: If by any chance the GC has not ran in 30000 executions then run the GC even though it didn't hit the 10%
    gc-min-runs: If by any chance the GC has hit the 10% AND there has been less than 5000 executions than do not run the GC.

    This is the basic setup for an efficient GC.
  27. Offline


    I shouldn't call it Garbage Collector atm, it's only runs one time at server start. I dont think that many servers run longer than a week, and that there is no need to delete right in time.
    Maybe I can add something, if I think that there is a need.
  28. Offline


    Adding permissions soon, Because I want to be able to give my mods the ability to use this? Good work so far though!​
  29. Offline


  30. Offline


    Uh ...
    I qoute from the description:
  31. Offline

    Michael Murphy

    ah, I assumed it was the griefing tool trying to scare people into playing good because big brother did it also.

    Thanks for clearing that up

Share This Page