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


    Yes the items show up it will say who takes what items or placed inside the chest. When i try and do a rollback nothing happens. maybe i need to put the right time!?
  3. Offline


    You always need the right time :D
  4. Offline


    Nope, it's set to -1. Are you willing to talk on IRC or something?
  5. Offline


    Sure, skype hawky.diddiz and irc #logblock, but as it's late here i'll able to respond forst tomorrow.
  6. Offline


    Do you need Spout in order to have 1.26 working?
  7. Offline


    No, only for chest logging.
  8. Offline


    Okay. Does that need Client Mod version of Spout or can I just have the server-side plugin only?
    Oh wow that was bad english btw :p
  9. Offline


    Server side is fine.
  10. Offline


    You updated something in the thread but i don't know what! XD
    Btw at what stages do you update to a recommended version?
  11. Offline


    Added "spout is optional"
    Either when it contains a critical fix, or a mayor feature was added and it's tested for a while, or there is a new recommended bukkit version with api breaks :D
  12. Offline


    I have a problem here.
    I already set up MySQL and it kept telling me in the console

    "LogBlock has been disabled"

    Can someone help me..?
  13. Offline


    Is there a way to avoid stacking items on rollback?
  14. Offline


    Look for the cause earlier. There should be a stack trace.
    Don't think so, at least not easily.
  15. Offline


    Found a problem with workbench logging
    Items only get recorded when they are in the left side of the workbench when you press E not the taken out items
  16. Offline


    Hm, there shouldn't be any items logged for workbenches, as they can't be storaged in there ...
  17. Offline


    please remove 'since'
    /lb rollback p:LoggerTest r:25 t:15m

    Please?! :D
  18. Offline


    /Offtopic (?)
    I see at your Youtube that if a player connects, they see "who's online" and colors. Trying to find it, but where is that at? (we don't use Permissions)
  19. Offline


    My logblock stop working after some minutes that I startup my server .... When LogBlock stop working I just receive this message each 10 seconds in the console/log:
    "[LogBlock Consumer] SQL exception on INSERT INTO `lb-server` (date, playerid, replaced, type, data, x, y, z) VALUES (FROM_UNIXTIME(1314053926), 115, 12, 0, 0, '80516', 65, '-824');: "

    My serverhosting company told me that it wasn't a MYSQL database issue, I need some hand.
  20. Offline


    Does LogBlock recognize grief caused by users using WorldEdit's Superpick command ( // )

    I have noticed that BigBrother does not recognize users using WE's // command to break blocks.
  21. Offline


    I love this plugin. But I want to request a new feature: the "owner" parameter. It would look for the player who placed (owns) the block (sorry, kinda hard to explain). It would be used like this: say I want to see chestaccess for bob. I would type "/lb lookup player bob chestaccess". But I would'nt know if bob took those items from his chests or joe's chests. with the owner parameter, I could type "/lb lookup player bob chestaccess owner joe" This would return everything that bob took and placed into chests joe created. It could also be used to see who destroyed the blocks of someone else. "/lb lookup player bob owner joe" would return all blocks that bob destroyed that were originally placed by joe. Finally, if no players are specified, it would work like the "coords" parameter, only it would return names instead of positions. For example: "/lb lookup player bob owner" could return: "08-22 16:55:53 bob destroyed Dirt placed by joe"
  22. Offline


    Some improvements are planned
    That's iChat, but it works with permissions
    I guess the error message said something about data truncation at column x?
    Then ->
    It can't, but i wrote a loggable super pickaxe plugin
    I get what you mean, sounds really interesting, but it' rather hard to implement in a not server blown way, as it requires a subquery for each block to find the owner. I'll put it on the todo list
  23. Offline


    Just switch from HawkEye, you're less laggier :p
    DiddiZ likes this.
  24. Offline


    I guess its the same function like the chest then ? but it works on workbenches aswell.....and I thought it should be like that :D
  25. Offline


    Nah, it shouldn't. Fixed that, thanks :D
  26. Offline


    Cool But...
    To Much Spam...
    And Maybe Not Chestacsses or what
    Maybe ca...
    the commands to long men
  27. Offline


    @DiddiZ did you ever make a admin web page to allow searching things a tad bit easier. Another certain plugin does this I love the website part but I love logblock hehe.
  28. Offline


    Could you be more specific? :D
    And regarding to commands lenght: Some alredy have shorthand versions.
    I know it, and alredy planned my own version of it (including rollback), but I need FrozenCow of DynMap to finish the WebBukkit plugin for easy LB commands integration.
  29. Offline


    Whhere and waht are the permissions nodes

    Is there a simple command like /bb here to lookup grief in your area?

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


  31. Offline


    Ewww nasty. I was hoping some pure SQL features. Not something else to cause more load to the server :p

Share This Page