LogBlock

LogBlock logo

Works 100% with 1.7.2

The best block logging and rollback solution for the savvy server administrator.

LogBlock is the best block logging plugin for Bukkit server. Not only is it awesomely powerful, it’s blazing fast! Everything is logged into a MySQL database, allowing developers to hook in and produce things such as player stats and even administrative panels. Every loggable action can be logged with LogBlock: WorldEdit, leave decay, fire, sign changes, explosions, chest changes, player and animal deaths, chat, commands and more!

Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.

LogBlock will very rarely break between Minecraft / Bukkit updates, however if you find it does, please be sure to try a development build from above, as we generally test new releases there until deemed stable.

What is LogBlock?

LogBlock is a tool which allows you to keep track of almost everything on your server, while also giving you the ability to rollback (revert) or redo changes made by users and natural occurrences such as liquid flow or leaf decay. Additionally, LogBlock is able to log and rollback chest contents, sign text and more! LogBlock was originally created by bootswithdefer for HMod, ported to Bukkit by DiddiZ and is now actively maintained by md_5, ammar2 and the community of developers on Bukkit. We accept pull requests on GitHub frequently which means that community developers can add features they wish to see quicker than LogBlock developers are able to from tickets. All database actions are run not only in their own threads, but are queued into a consumer to minimize lag on the main thread. This is great for larger servers! All optional features (not dependencies below) are enabled and disabled from within the config file allowing complete control over what is logged thus ensuring database size is kept to a minimum.

Notices

Most virtual chest plugins are not compatible with LogBlock. Because they do not set the player who is opening the “chest”, LogBlock can’t do what it’s meant to be able to do, thus, making errors in your console. Please report these issues to the fake-chest plugin developer, NOT LogBlock developers.

Issues are read more frequently on the GitHub Issues page as compared to the comments below. When updating to LB1.57, if you already have a large database and have changed your columns to MEDIUMINT, INT or LARGEINT, you do not need the updater to fix this for you automatically. To stop this behaviour, simply change “version” in the configuration to ‘1.57’.

If you are experiencing an error such as this please read the FAQ for answers.

If you're receiving errors regarding players from the consumer such as "[Consumer] Failed to add player <playername>" then change all `playerid` columns to MEDIUMINT or INT in each table that contains them. This may take a long time if you have a lot of rows.

Optional Dependencies

  • WorldEdit (Recommended)
  • Permissions plugin
  • LogBlock Questioner

Need help?

Found a bug or an issue? Please report it (and attach code if you know how to squash it) on our ticket manager.

Just need help in general or have an urgent, more private bug? Join us on IRC at irc.esper.net #LogBlock and ping a +o or +v for faster help. Webchat is available here if you don't have a client, or prefer to use it.

As always, check if your question is on the FAQ before asking!

Installation

  1. Installation
  2. Permissions
  3. BigBrother log import
  4. Configuration
  5. MySQL Configuration

More Information

  1. FAQ (read me first!)
  2. Command reference
  3. Configuration
  4. Helpful Commands
  5. MySQL Connection Problems
  6. MySQL Schema
  7. SQL Queries
  8. Parameters

Are you a Developer?

If you wish to contribute to the LogBlock project, head on over to the GitHub page, fork the project and submit your pull request(s).

If you wish to develop a plugin that interacts with LogBlock in some way, read up on the API here. Support for API and more can be found in the IRC channel, which is listed above.

Developer builds can be found here. (These builds have not been approved by the BukkitDev staff. Use them at your own risk.)

Still need help? Join us on IRC at irc.esper.net #LogBlock and ping a +o or +v for faster help.

Please do not post comments requesting support. Report bugs here or, alternatively, talk to a real person. Commenting below is a surefire way to not receive help.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of masteryodaaa masteryodaaa Aug 08, 2012 at 17:43 UTC - 0 likes

    After we uppdated to 1.3 random players can use the stick and se placed blocks and they dont even have permissons what happend and what can i do?

  • Avatar of Rowtag87 Rowtag87 Aug 08, 2012 at 15:40 UTC - 0 likes

    @AbuRom: Go

    arrrr thanks man! Awesome!

    But now it only works for OP's and doesn't use the Permissions. How can i handle this?

    Last edited Aug 08, 2012 by Rowtag87
  • Avatar of Mixon87 Mixon87 Aug 08, 2012 at 10:30 UTC - 0 likes

    I am a noob to this plugin, but may I ask: Is it possible to rollback all player actions no metter how long he did something? Because, when u finds griefer it may past more then 30 mins, and everytime Iam tryting to rollback it says: No actions for the past 30 mins. Thank you.

    mixon87

    Join: US.SANC.US / MC.SANC.US

  • Avatar of AbuRom AbuRom Aug 08, 2012 at 09:28 UTC - 0 likes

    @Rowtag87: Go

    Actually, what jaimie said worked for me!

    Here's the config part that I changed:

    tools:
      tool:
        defaultEnabled: true
        mode: LOOKUP
        aliases:
        - t
        params: area 0 all sum none limit 15 desc silent
        leftClickBehavior: NONE
        item: 270
        rightClickBehavior: TOOL
        permissionDefault: 'OP'
        canDrop: true
      toolblock:
        params: area 0 all sum none limit 15 desc silent
        permissionDefault: 'OP'
    

    @jamietech: Go

    Thank you very much Jaimie!

    Last edited Aug 08, 2012 by AbuRom
  • Avatar of Rowtag87 Rowtag87 Aug 08, 2012 at 08:56 UTC - 0 likes

    @jamietech: Go

    The message says, You aren't allowed to do this.

    I set the permissions and im OP.

    There is no error in console. I also can't use the bedrock if i use one in hand, it just places the block.

    Last edited Aug 08, 2012 by Rowtag87
  • Avatar of jamietech jamietech Aug 08, 2012 at 08:37 UTC - 0 likes

    @AbuRom: Go

    Try setting permissionDefault to 'OP'

    Signature

    BFAK:jamietech,23764,cf2d38ccf0feb4785c6942aa9b69354231d6119b9abeba86238fdc0c2c155e7f

  • Avatar of AbuRom AbuRom Aug 08, 2012 at 04:19 UTC - 0 likes

    I don't really use a permissions plugin for anything as I don't use groups and have no one but me and 2 other people as full power admins, however, even with ops, Logblock does not allow me to use toolblock and such...

    Why is this? Is there any way to give myself permission without having to use a permission plugin (as the only one I set up is essentials).

    I tried popping it into permissions.yml (the main server permissions) however that didn't change a thing.

    Ideas?

  • Avatar of jamietech jamietech Aug 07, 2012 at 23:43 UTC - 0 likes

    @Damimad: Go

    Ensure you have logging setup in (world-name).yml files

    @Davyhalliday: Go

    Are your tables populated with data or is it safe to remove them for LogBlock to recreate them?

    @Josef2222222222: Go

    OK THIS HAS BEEN TAKEN INTO CONSIDERATION

    @Mixon87: Go

    As far as I know you would /lb rb world <worldname>, and no, there is no permission node for this. Only give administrative tools to users you trust.

    @Kartikitrak: Go

    This is not a LogBlock issue but a SQL issue (or your database is not able to be queried remotely). Consult with Google or your service provider :)

    @EndCraftMC: Go

    Please read the FAQ on the Wiki.

    @Rowtag87: Go

    Please specify what error you are receiving. Saying 'it doesn't work' doesn't help. ;)

    @agorapolis: Go

    Please read the FAQ on the Wiki.

    @Damimad: Go

    Ensure that world is configured to be logged in both the config.yml and the (world-name).yml

    @Gonzalez22: Go

    Please give us any errors you receive.

    @Rowtag87: Go

    @Nekuroi: Go

    Are you given a no-permission message or something else?

  • Avatar of Nekuroi Nekuroi Aug 07, 2012 at 23:01 UTC - 0 likes

    @Rowtag87: Go

    same issue but using bpermissions

  • Avatar of Rowtag87 Rowtag87 Aug 07, 2012 at 18:15 UTC - 0 likes

    All /lb tool commands are not working for me. i give the logblock.* permission, every other command works. Im not able to lookup. I use Bukkit 1.3.1 RB and LB 1.56!

    Also using groupmanager.. for perms.

Facts

Date created
Aug 24, 2011
Categories
Last update
Dec 05, 2013
Development stage
Release
Language
  • enUS
License
Attribution-NonCommercial-ShareAlike 3.0
Curse link
LogBlock
Downloads
361,391
Recent files

Authors