LogBlock is an anti-grief prevention plugin designed by one of the most amazing plugin developers out there
the plugin consists on stopping griefers and even catching them in the process. The plugin can be found at bukkit.org ; It's a strong anti-grief prevention plugin that is a much need in your minecraft server. The plugin itself logs, and saves the grief / block change of everything ( which you enable ) on the server. So with this plugin I could pull out my trusty logblock wand and view who griefed my fountain! It uses MySql databases to save these massive logs so that you have no worries on having to have a overload of logs on the server database!
How do we set it up?
First, you'll need to download this plugin, and gladly enough I have the link here so it's one click away. http://dev.bukkit.or...-mods/logblock/
Next, You'll need to insert the jar file into your plugins folder for your server, this will allow the plugin to generate / create the necessary files needed to run logblock.
~Make sure you have your MySQL provided by Your Hosting Company~
Once you have the files generated you should see a nice folder inside the plugins called ' logblock ' Let's go inside this folder to config the plugin correctly.
Once your inside the folder you should see the file config.yml, You'll need to open this file with whatever your favorite text editing program is.
Your Hosting Company should provide you with the correct entrys to set this up.
Lets say they sent me a post with this information for my MySQL
Thanks Åxçel for signing up with us, here's your MySQL information.
The database name of your MySQL is ' minecraft '
Username: Åxçel
Password:123456789
You can connect to the MySQL through 192.168.1.1 ( This could also be a domain.... http://www.yourdomain.com/ )
This information should be 100% significant to start up your logblock.
All the information is color codded so that you see exactly what goes where.
You do not need to worry about the port. The default port given is 100% ok.
Everything should be ready to go after your done! Logblock is now in your procession and antigriefers beware!
What are the permission nodes?
logblock.lookup:
description: 'Grants access to /lb lookup commands and allows defining custom tool queries'
default: op
logblock.rollback:
description: 'Allows rollback, redo and write logfiles'
default: op
logblock.clearlog:
description: 'Allows to use /lb clearlog'
default: op
logblock.hide:
description: 'Allows to hide from logging'
default: op
logblock.tp:
description: 'Allows to use /lb tp'
default: op
logblock.me:
description: 'Allows to see oneselfs stats with /lb me'
default: true
logblock.ignoreRestrictions:
description: 'Allows to ignore the rollback restrictions rollback.maxTime and rollback.maxArea'
default: op
logblock.spawnTools:
description: 'Allows to spawn tools'
default: true
What are the logblock commands?
It just so happens that I have the command reference by my side and I'm willing to share it with you. So here it goes with some sample commands aswell!
/lb help
Ingame help
/lb params
List of all params
/lb commands
List of all commands
/lb permissions
List of all LB related permissions you have
/lb tool
Gives the lookup tool (default woodpickaxe)
/lb tool [on|off]
Toggles whether the tool is enabled or not
/lb tool [params]
Binds a new query to the tool. This affects only you and works until server reload/restart.
/lb toolblock
Gives the block lookup tool (default bedrock)
/lb toolblock [on|off]
Toggles whether the tool block is enabled or not
/lb toolblock [params]
Binds a new query to the tool. This affects only you and works until server reload/restart.
/lb savequeue
Saves all block changes immediately into database. Useful for rollbacks after huge fires.
/lb lookup [params], /lb [params]
Shows you the result of a query.
/lb writelogfile [params]
Write the result of a query into a log file to "/plugins/LogBlock/log". The layout is similar to the message from the wood pickaxe. If no results were found, the log file will be empty
/lb tp [number]
Teleports you to the location of a block change in the last lookup or rollback errors. To be able to teleport to lookup results you have to use coords param for the lookup, eg:
/lb redo [params]
Redoes block changes, counterpart of rollback.
/lb clearlog [params]
Deletes the log. Cannot be undone, except you have dumpDeletedLog enabled and import the dump. It’s highly recommended to do a lookup first, and call /lb clearlog last to avoid deleting accidentally wrong log.
/lb hide
Toggles hiding. No actions from a hidden player will be logged! Be careful!
Example Commands:
thanks to tha d0ctor
/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)
Credits given to the LogBlock Creators, whom are probably some of the hardest working people out there, they deserve everything last appreciation and donations that they get! Logo taken from the logblock dev page at bukkit, i claim no rights on making it nor do I claim it as my own, it is property of logblock.
LogBlock Creators:
DiddiZ
Manager
Author
EDIT: Reworked the Guide a bit, making it easier to read thanks to Nentify!
I honestly prefer HawkEye just for the web interface, but this is a pretty good tutorial.
lol to the center joke.
It's just how I originally had it, since I was only going to be using this guide within my hosting community xD
I think I might post a guide for HawkEye
Also did you know hawkeye and logblock and bigbrother are all teaming up to create one greifing prevention plugin called Guardian?
So they say. Development has slowed, LogBlock is still developing their own plugin, HawkEye/BB have gone missing leaving md5 alone. Quoted from the BukkitDev page:
Lead developers:
md_5
DiddiZ (Retired / Inactive)
oliverw92 (Retired / Inactive)
It's a shame really.. :l
Wow that is a shame
Maybe they are trying to keep it hidden. xD
But good guide am I right?
Yeah, keep up the work. Good guide for starters. My only recommendation would be to make it a bit clearer.Some of it's quite bunched up, even just doings things like making a permission bold, and an explanation of what it does in italics underneath would look nicer with a single-line space in between each node for example.
logblock.hide Description: 'Allows to hide from logging'
Default: op
logblock.tp: Description: 'Allows you to use /lb tp'
Default: op
Thanks tons, took your formating idea, and put it into action! Much appreciated
Also, free bumbies are awesome
I appreciate the time put into the guide, but guardian will soon be taking over both hawkeye and logblock. Meaning this will be of no use soon.
Herogx, If you read the earlier posts you would see the conversation talked about Guardian, infact, Guardian may not happen at all saddly. Since what we have seen is that all development stopped on it.
And thank you for the kudo.
So they say. Development has slowed, LogBlock is still developing their own plugin, HawkEye/BB have gone missing leaving md5 alone. Quoted from the BukkitDev page:
Must say this was very helpful. Problem I am having however, is even after editing LogBlock/config.yml and changing the database name, user name, info, etc... I'm still unable to get logblock to communicate with my web host (godaddy, go figure) and properly write from my server folder (on my home based machine) to the database I specify.
It keeps giving the default information you listed above (default db paramaters) even after I've reloaded the plugins etc.
EDIT: Will post a script parse / log information to show you default values it keeps pushing towards.
Must say this was very helpful. Problem I am having however, is even after editing LogBlock/config.yml and changing the database name, user name, info, etc... I'm still unable to get logblock to communicate with my web host (godaddy, go figure) and properly write from my server folder (on my home based machine) to the database I specify.
It keeps giving the default information you listed above (default db paramaters) even after I've reloaded the plugins etc.
EDIT: Will post a script parse / log information to show you default values it keeps pushing towards.
Say I know it's a long time in all, but if you still need help, send me a message and I'll help you out!
I have a question for you LogBlock Masters. Yesterday one of the new admins on our server found a greif and did a roll back. The problem is he rolled back way way way to much. How or can I even fix that now.
I have a question for you LogBlock Masters. Yesterday one of the new admins on our server found a greif and did a roll back. The problem is he rolled back way way way to much. How or can I even fix that now.
I know this is a pretty late reply, but I don't think you are able to. :/ Sorry.
What is LogBlock?
LogBlock is an anti-grief prevention plugin designed by one of the most amazing plugin developers out there
the plugin consists on stopping griefers and even catching them in the process. The plugin can be found at bukkit.org ; It's a strong anti-grief prevention plugin that is a much need in your minecraft server. The plugin itself logs, and saves the grief / block change of everything ( which you enable ) on the server. So with this plugin I could pull out my trusty logblock wand and view who griefed my fountain! It uses MySql databases to save these massive logs so that you have no worries on having to have a overload of logs on the server database!
How do we set it up?
Next, You'll need to insert the jar file into your plugins folder for your server, this will allow the plugin to generate / create the necessary files needed to run logblock.
~Make sure you have your MySQL provided by Your Hosting Company~
Once you have the files generated you should see a nice folder inside the plugins called ' logblock ' Let's go inside this folder to config the plugin correctly.
Once your inside the folder you should see the file config.yml, You'll need to open this file with whatever your favorite text editing program is.
Inside the file you will see this exactly...
mysql:
user: username
port: 3306
password: pass
host: localhost
database: minecraft
Your Hosting Company should provide you with the correct entrys to set this up.
Lets say they sent me a post with this information for my MySQL
Thanks Åxçel for signing up with us, here's your MySQL information.
The database name of your MySQL is ' minecraft '
Username: Åxçel
Password:123456789
You can connect to the MySQL through 192.168.1.1 ( This could also be a domain.... http://www.yourdomain.com/ )
This information should be 100% significant to start up your logblock.
All the information is color codded so that you see exactly what goes where.
You do not need to worry about the port. The default port given is 100% ok.
Everything should be ready to go after your done! Logblock is now in your procession and antigriefers beware!
What are the permission nodes?
The permission nodes are as follows.
logblock.*:
description: Gives access to all LogBlock commands
children:
logblock.lookup: true
logblock.rollback: true
logblock.clearlog: true
logblock.hide: true
logblock.tp: true
logblock.me: true
logblock.ignoreRestrictions: true
logblock.spawnTools: true
logblock.lookup:
description: 'Grants access to /lb lookup commands and allows defining custom tool queries'
default: op
logblock.rollback:
description: 'Allows rollback, redo and write logfiles'
default: op
logblock.clearlog:
description: 'Allows to use /lb clearlog'
default: op
logblock.hide:
description: 'Allows to hide from logging'
default: op
logblock.tp:
description: 'Allows to use /lb tp'
default: op
logblock.me:
description: 'Allows to see oneselfs stats with /lb me'
default: true
logblock.ignoreRestrictions:
description: 'Allows to ignore the rollback restrictions rollback.maxTime and rollback.maxArea'
default: op
logblock.spawnTools:
description: 'Allows to spawn tools'
default: true
What are the logblock commands?
It just so happens that I have the command reference by my side and I'm willing to share it with you. So here it goes with some sample commands aswell!
/lb help
Ingame help
/lb params
List of all params
/lb commands
List of all commands
/lb permissions
List of all LB related permissions you have
/lb tool
Gives the lookup tool (default woodpickaxe)
/lb tool [on|off]
Toggles whether the tool is enabled or not
/lb tool [params]
Binds a new query to the tool. This affects only you and works until server reload/restart.
/lb toolblock
Gives the block lookup tool (default bedrock)
/lb toolblock [on|off]
Toggles whether the tool block is enabled or not
/lb toolblock [params]
Binds a new query to the tool. This affects only you and works until server reload/restart.
/lb savequeue
Saves all block changes immediately into database. Useful for rollbacks after huge fires.
/lb lookup [params], /lb [params]
Shows you the result of a query.
/lb writelogfile [params]
Write the result of a query into a log file to "/plugins/LogBlock/log". The layout is similar to the message from the wood pickaxe. If no results were found, the log file will be empty
/lb tp [number]
Teleports you to the location of a block change in the last lookup or rollback errors. To be able to teleport to lookup results you have to use coords param for the lookup, eg:
/lb player diddiz destroyed block diamond_ore coords
/lb tp 1
/lb tp 2
/lb page 5
/lb tp 62
/lb tp [params]
Teleports you to the location of a block change. E.g. /lb tp player diddiz teleports you to the last blockchange of player diddiz.
/lb rollback [params], /lb undo [params], /lb rb [params]
Rolls back block changes.
/lb redo [params]
Redoes block changes, counterpart of rollback.
/lb clearlog [params]
Deletes the log. Cannot be undone, except you have dumpDeletedLog enabled and import the dump. It’s highly recommended to do a lookup first, and call /lb clearlog last to avoid deleting accidentally wrong log.
/lb hide
Toggles hiding. No actions from a hidden player will be logged! Be careful!
Example Commands:
thanks to tha d0ctor
/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)
Credits given to the LogBlock Creators, whom are probably some of the hardest working people out there, they deserve everything last appreciation and donations that they get! Logo taken from the logblock dev page at bukkit, i claim no rights on making it nor do I claim it as my own, it is property of logblock.
LogBlock Creators:
DiddiZ
Manager
Author
EDIT: Reworked the Guide a bit, making it easier to read thanks to Nentify!
I honestly prefer HawkEye just for the web interface, but this is a pretty good tutorial.
lol to the center joke.
It's just how I originally had it, since I was only going to be using this guide within my hosting community xD
I think I might post a guide for HawkEye
Also did you know hawkeye and logblock and bigbrother are all teaming up to create one greifing prevention plugin called Guardian?
Wow that is a shame
Maybe they are trying to keep it hidden. xD
But good guide am I right?
Thanks tons, took your formating idea, and put it into action! Much appreciated
Also, free bumbies are awesome
Herogx, If you read the earlier posts you would see the conversation talked about Guardian, infact, Guardian may not happen at all saddly. Since what we have seen is that all development stopped on it.
And thank you for the kudo.
Bumpity bumpity...
It keeps giving the default information you listed above (default db paramaters) even after I've reloaded the plugins etc.
EDIT: Will post a script parse / log information to show you default values it keeps pushing towards.
Say I know it's a long time in all, but if you still need help, send me a message and I'll help you out!
Thanks man!
That's permissionsEX failure, all you need to do is put
- -logblock.*
on a rank which you don't want them to have it
I know this is a pretty late reply, but I don't think you are able to. :/ Sorry.