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

Discussion in 'Inactive/Unsupported Plugins' started by DiddiZ, Feb 16, 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, did you try /lb savequeue before?
  3. Offline



    Uhuh, I did. And it said that there were no things in the que. But I tried a few minutes ago, and it seemed to work. Don't know if it'll still work after a couple of days though.

    (Noob question: where the heck is that quote button? So I can auto. quote someone's post?)
  4. Offline


    Hope so.
    Reply button :D
  5. Offline


    The server is dedicated, and I'm editing the server with a remote editor, is that what you mean?
    If thats what you mean, yes its remote, how would I go about doing that?
  6. Offline


    So do I, but I'll post a reply here as soon as I get a concrete result.

    (Wow, how could I be so blind. But thanks. :p)
  7. Offline


    Forgot to mention that I was talking about your MySQL server ...
  8. Offline


    Earlier in the (LogBlock v1.01) after rollback (/lb rb player pomo4ka) and (/yes) appeared message (/lb clearlog last) deletes the entries that have already been used.

    This function was for me very useful. Now it is gone, and the command (/lb clearlog last) removes all of the latest entry in the table. What should I do?
  9. Offline


    I only removed the message, /lb clearlog last should still work
    When you use it for areas, you have to stay an the location.
    Btw, you mentioned some performance issues: Next version will be about 4 times faster :D
  10. Offline


    Thank you. And for the players command (/lb clearlog last) will not? Or for example can be done (/lb clearlog player pomo4ka last) or (/lb clearlog player pomo4ka 10m), etc.
  11. Offline


    Um ...
    /lb rollback player pomo4ka area 10 since 14:00:00
    /lb clearlog last
    is still equivalent to:
    /lb rollback player pomo4ka area 10 since 14:00:00
    /lb clearlog player pomo4ka area 10 since 14:00:00
  12. Offline


    Well, when I did (/lb rollback pomo4ka) and then (/lb clearlog last) told me that he remove the last record of all time.
  13. Offline


    It's due to you don't enter a time for /lb rollback. That got fixed in v1.10.
  14. Offline


    Uh, I didn't set up the MySQL server, the hosting company did it for me. It worked fine until a /reload, which is making me wonder..

    EDIT: I also checked the MySQL server, its running fine!
  15. Offline


    Sorry course I could from the poor knowledge of English. I still do not understand why it does not work as before.
  16. Offline


    Hm, there was an issue, that LB sometimes failed to read the config.
    The "connection to" message is 100% proper and using pwasseord yes?
    When you dont provide a time for a rollback command it's default 30 minutes, for clearlog commands it's unlimited. But it should be fixed with 1.10 (so it'll overtake to 30 mins even when you didn't specified a time).
  17. Offline


    Got it. I think it used to be better. Now this is slightly useful.
  18. Offline


    Got the sql files unfortunately our data is mixed into the new data in the same database.

    What can we do abut this?

    Old data
    Looks like we have 2 sets of old data ones with create/destroy ones with none there.

    New data
    First set goes to page 52536 ID 1576062
    Second set goes to page 260593 ID 7817779

    Instead of a PlayerID we have there names etc .

    Some someone whip up a sql that will fix this for us cross referencing with the lb-players and adding ones not in there in?

    Cause we do not want to loose history from august or so last year to may this year.

    Or tell me how to separate the data so we can update it.
  19. Offline


    Firstly, how did you get there? Did you just rename the columns?
    Rename the column playerid back to player and execute this query:
    The update u are missing is the one from LB v0.7:
    Code (Text):
    1. INSERT IGNORE INTO `lb-players` (playername) SELECT DISTINCT player FROM `<table>`;
    2. ALTER TABLE `<table>` ADD `playerid` SMALLINT UNSIGNED NOT NULL AFTER player;
    3. UPDATE `<table>` INNER JOIN `lb-players` ON `<table>`.player = `lb-players`.playername
    4. SET `<table>`.playerid = `lb-players`.playerid;
    5. ALTER TABLE `<table>` DROP `player`;
  20. Offline


    Is there any way to optimize the MySQL server to work with the plugin LogBlock? I now have about 16.000 records. This statistic is approximately 4 hours of the server. I want to keep them always, without removal.
  21. Offline


    Yes. It does say connection to and uses the password. It has not changed a bit from what it originally did except for the error.
  22. Offline


    There are also some index optimizations coming.
    What statistic?
    Strange ... really. And the MySQL server didn't change? Another port, ip, db?
  23. Offline


    Another guy did it i think he just renamed the columns for bukkit so we kinda have a really old database so most of the sql updates were not done :( as you can see we still go back to create/delete in actions. I edited my post previous page we have older data with create/delete tie in action they will also need to be updated as somehow there must have been a sql update we never put in back last year.

    Problem is we have thousands of pages and its all in 1 table so I need to update everythingto the new structure somehow which I don't know what queries to use to do all this so kinda need help here to get this done :/

    I have the ID numbers of the types.

    First set goes from 0 to 1576062 (Create/delete actions + playernames)
    Second set goes from 1576063 to 7817779 (playnames)
    Where 7817779 onwards is the latest logblock data. (latest version)

    Hope that's a better help?
  24. Offline


    I'm not sure if i read the wiki wrong or if no such feature exists, but why doesent "/lb tool mode chestaccess" work?
    I want to be able to smack a chest with the tool to see who accessed that chest.
  25. Offline


    You want to say you are now storing the player ids as varchar?
    Should be very slow ... who does something like that?
    Year, "CREATE TABLE `temp` like `lb-main` SELECT * FROM `lb-main` WHERE id < 1576063;"
    then you can update the tables, and merge to one later.
    The normal lookup does that :D
  26. Offline


    I don't know you you actually mean here.

    I updated using your query without splitting and its worked and all ID's are in.

    But the data is still create/delete etc for actions for the first set to that number 1576062 is that a problem?

    I created a backup before starting of the database to sql.
  27. Offline


    Um, most likely you now have many playerid as playernames in lb-players table ...
  28. Offline


    Unfortantly I do and none of the previous initial logs are working either :(

    But Hey I have the second section of logs back again :/

    So what happens here?

    Trying to import the backup on my local mysql but its 625mb.
  29. Offline


    That works only for the log with player names still in there. New newer log alredy has a playerid stead of the name, so it added the id as name. You better delete these names :D
  30. Offline


    Don't get you again what im going is install the backup on my local system (which is going now) its too big to reupload then I Ill cross referance as what I feel is all names are deleted from the newer ones now :/

    Or just output data from tables and reupload the new data to get the server going again and then work on the older data making it compatible.

    Ill use your query to output split the data up on my test system.

    "CREATE TABLE `temp` like `lb-main` SELECT * FROM `lb-main` WHERE id < 1576063;"

    Is that all I need and change the < to > ?

    Then do it multiples to split the data up.

    You told me how to do the middle data what about the initial first data with the create/destroy in actions how do i bring that up to date also?

    Also is there a way to renumber cross referencing names as Ill have 3 sets of name id's which is not cool.

    I'm kinda basic at doing sql etc but know a very small amount and cleaning up some mess we had from someone else here :/

    Update: unfortunately my backup wasn't full I guess were screwed with the latest data since going to bukkit.
  31. Offline


    You've to use the same lb-player table all the time, ot it will end up giving one player different ids.
    I'm sorry when my query messed up your data, I couldn't know that all your log was in a single table :'(

    When you still need my help, add me on skype (hawky.diddiz) or give me acces to the db, think I'd be faster than expaining it all to you.

Share This Page