GriefLog
We are discussing plans for Sponge and GlowStone support. Please be patient :)
If you are using WorldEdit 6.0 or later please use the 5.2.2 version. If you are using WorldEdit 5.x.y please use version 5.2.3-worldedit, thank you.
Wiki | The GriefLog wiki is filled with information about GriefLog. We have some information below, but the wiki is much more descriptive. |
Download | Latest build that is approved by bukkit. |
Development Downloads | This build is not approved by bukkit, but it is the most recent, development build. If bukkit updates and GriefLog is not compatible, this is a good place to look for an update. |
GriefLog Source | You can find the latest GriefLog source code here at GitHub. However, if you would rather not just compile it, we recommend downloading the latest Dev Download. (Information Above) |
Permissions | You can use these permission nodes to allow other users to do certain things. |
Description
How many times has someone on your server told you that someone griefed there house, but they don't know who did it? Well, this is a great way to fix that. GriefLog will log every event that happens within your server. It will also separate the log files into worlds. So now you can prove that it was in fact a griefer. Now, you don't need to actually go into the log files, you can take out your GriefLog tool and left click on a block, it will bring up the information. You can also simply use a command to roll back the grief. More information is below.
Usage
So what exactly does GriefLog log? What can it do to help me? Well, GriefLog will log just about anything. It then saves it to a file called GriefLog.txt which can be found in "<YourServerDirectory>/logs/<world>/grieflog.txt." It is the same on every operating system. Here is a list of exactly GriefLog will log:
- When a player joins the server
- When a player breaks a block
- When a player places a block
- When a player uses a command
- When a player changes the world they are in (e.g. Entering the nether)
- When a player leaves the server
- If a player's game mode changes
- If a block is ignited
- If a bucket is emptied
- If an Enderman takes or places a block
- If a Zombie breaks down a door
- If there is any kind of explosion
All of this is logged to a very simple layout. You can choose a block with the GriefLog tool, Use the Search command, or look through the GriefLog.txt files.
Commands
We have many different commands to try and make the plugin as simple as possible to use.
- /glog - This will show you the version of GriefLog you are running.
- /glog tool - This will provide you with the GriefLog tool. You can set the tool in the config.yml
- /glog rollback <options> - to use roll backs, please read the section on our wiki here.
- /glog search <options> - You can search certain events. The options are the same used on the rollbacks.
- /glog page <page_number> - This will let you go through the other pages of your most recent search.
- /glog help - This will bring up the same information you see right here but within your Minecraft Client.
- /glog undo <id> - This will undo the rollback associated with the ID. Do not provide an ID to undo the most recent rollback.
- /glog report - This will report a grief. It will alert the admins of a report when they log in.
- /glog report view - Admins can view information of a grief report. It shows the location of the report, and the reporter.
Need Help?
We are here for you! Feel free to leave a comment, or better leave a ticket. **IMPORTANT**If you are willing to leave the IP address of your server within your ticket, pm, or comment, BlackWolf will be able to enter your server and will have the permission to use the /glog command to see what version you are running. You can disable this feature in the config.yml.
Did you find a bug?
If you find bugs in my plugin feel free to post a comment on this page, send us a pm, or add a ticket. Important: Check your inbox regularly to see if I replied!
Donate
If you want to donate some money because of my awesome work (:P) you can click the donate button on the right on the top of this page. Anything would be appreciated, but you don't have to if you don't want to or can't :)
Metrics
GriefLog creates debug logs, since 5.2.0, in the plugin directory in case there is a problem. You can disable this in the configuration file with the option debug-logging. When you set this to false it will not log any debug information. This information is only used by me to find out more about a bug you might encounter. It will log things like how long it takes to search a file, what is being searched for and if there are any problems when searching, for instance a data type that has been corrupted that can cause the search to fail.
External connections
Since version 5.2.3 GriefLog uses an external service to get the UUID from his name. This has to be done because the search tries to find the UUID of the player you search for in the logs instead of his name. This is because when 1.8 gets here you can change your name, but you can't change your UUID. But to make sure that searching doesn't get more complicated I needed a way to let you guys search for a players name while GriefLog searches for his UUID. For that I currently use an external service until Bukkit will provide one for me, or if they don't I'll keep using this one.
Hey there. I wanted to swing by and say thanks for making a great plugin. I use it to track xrayers and such and it works perfectly. I didn't want to ask a question but maybe one quick one, what does 'warn-on-lava' do? Anyway - great job keep it up! Jack
amazing plugin blackwolf...definitely love using it on my server. It has helped me many a times when a player tries to deny they griefed and I can pull up the logs from this and post it directly to them what they broke, where and when.
@Mayhem777
Don' t tell me, that isn't my plugin as far as i know, it happened on my old server too, but when i tested it, it was because of Essentials, but i can try to remove something to check if it was indeed my plugin. greetz blackwolf12333
BIG BIG BIG BIG BIG BUG, when use waps from nether to another world the server freezes, i tried with essentials, can't use back, spawn, or other warp command, just freezes and disconnects all players :(
@Doogy700
Maybe the grief was longer ago as the current logfile has, so you might wanna search through the older log files manually, i had support for that, but that broke the searching function and if only one person was searching, my cpu was almost burning, so i disabled that. That the block comes back in your inventory is right, than you can check other places too, without having to destroy the block first, after the first check. I hope this helped, greetz blackwolf12333
Okay so I used the deadbush tool but it didn't work so i changed it to Lapis Lazuli block and it still didn't work. When i place the block in the place that was griefed nothing comes up and the block just comes back into my inventory. Help?
Great, easy, good and just epic. Good work keep it up will be fun to see more in the future :)
@confuz3d
Indeed, i had that problem myself too, i'll try to fix that tomorrow, it's getting a bit late here:P greetz blackwolf12333
EDIT: Fixed it i hope:P
Ok the log is now moving correctly :D but commands and dead brush tool does not work anymore :( ill stay with the old on I guess.
Everything is working as it should now! Logs show up in the logs folder! Great work!
@Malarionbwr
No problem, i don't have school at the moment:) greetz blackwolf12333
I will let you know as soon as we do enough for the log to get split! Thanks again for being so quick!
@Malarionbwr
I think i fixed your problem in the 2.8.1 version, but i am not sure, because this doesn't happen on my server:P greetz blackwolf12333
Thanks for the speedy reply blackwolf! I actually did have a folder named logs from the old version of the plugin. When I found the new version was not placing them there, I deleted it to see if it needed to make it on its own. I will re-create it and see if that helps.
As for the OS, unfortunately I have no idea what os my host is running. I rent from daddycheese's eu servers, and use multicraft control panel and net2ftp to access everything.
@Malarionbwr
I assume you use to different operating systems, a windows pc with the ftp client and a server with some distro of linux, that could be the problem, but i am not sure, this shouldn't happen, maybe you could try to first create a directory called logs, and then just wait till the next time it moves to see if it then does work.
greetz blackwolf12333
My plugin is creating files named logs\grieflogDATEHERE.txt - they are not going into the logs folder and I am unable to do anything with them through the ftp client (presumably because of the \?) I did not have this problem on the older version : (
@confuz3d
Fixed your problem in the new release:) greetz blackwolf12333
@blackwolf12333
I did but still doesn't work, i can use the plugin but i have to manually copy & paste the log files to the log folder. read and write permissions are on. If you could tell me what should be the name of log files in the log folder i could name them correctly so the plugin recognize them. (i guess) i'll check maybe it's something with special chars in my path.. i'll post here when I test that!
Edit: changed path name, didnt solve the problem :l
@confuz3d
Hmm, maybe missed something there, you should just create a folder called logs in the root folder of your server, that should work
greetz blackwolf12333
Cool plugin!
Does not work for me as it keep spamming : cant move log file to logs/
Hope there's a way to fix that :\