SWatchdog
SWatchdog is now Abandonware, how cool is that?
Version: 1.19
Tekkit version 1.13Tekkit - Optimized for Tekkit, not recording machines.
This plugin will record all the broken and placed blocks, with their subtypes, person who broke/placed them & time and date when this happened. Also options for chest access logging as well as animal slaughter logging. There is also functionality to rollback said actions, re-place broken blocks, remove placed blocks ect. Its aimed to be lightweight, since bigbrother, while good, lagged any server I could see it used on. And while there are other block-logging plugins, most of them had sides that didn't appeal to the servers (where I work) owner. Like require the admin to setup the SQL database, the plugin connects to an external database the whole time, or the plugin is way outdated. And other problems like that, so I made SWatchdog. To keep it simple and efficient. We've been using/testing SWatchdog for some time now, and it seems to be a success. No lag whatsoever.
How to reach me
If you have any questions what so ever, have any problems with SWatchdog or want to give feedback / make a suggestion, you can either:
Send me PM here. Thats the most certain way to reach me, since I'm checking my PM's here every once in a while. (Note, a PM at BukkitDev, not a convo at Bukkit.)
Or you can try to reach me at -Server not public yet- ( - or the website ) for the most immediate and clear conversation. ( 0Given that I am online. ^_^ )
Recent changes
- Full control of what you want to record. (Though I doubt anyone would want to log only decaying leaves, even that is possible.)
- Rollback specified players, or blocks, or specified blocks placed by specified players. In the specified area after specified time. Yes, you can now be just about as specific as you want.
- Added automated log-cleaning as an option
- Added a powerful tool for checking the files integrity, option to do this automatically on server restart (and plugin reload) and to repair it (automatically)
- Entering incorrect parameters for a command now automatically shows relevant help to that command.
- Added chest access -logging as an option. Its defaulted to false, so if you want it, just enable it in the config.
- Added chest access -logging results to /sniff look and /supersniff look
- Added /wutil repairintegrity to easily make sure everything is as it should be.
- Added a method to change configs ingame. Yay!
- Added the stick. As an option. You need to enable it and give yourself the perm.
- Rolling stuff back now recognizes failed rollbacks (0 blocks) and suggests what might've gone wrong. (Like giving too specific criteria for example.)
- Added animal slaughter logging
- option to preview rollback before rolling back.
- Improved /WTrack
- Optimized single block sniffing, now faster than ever.
- Optimized WXRay
- ADDED PlayerUndo /WUndoP and PlayerClean /WCleanP to easily rollback spesific players.
- Major optimization, commands run in threads now.
Please note
- Please use uptodate permission plugin. Outdated permission plugins may be unable to handle the latest bukkit permission format. So please make sure your permission plugin is updated to latest R#. If there is no update, just notify the author of the permission plugin to update.
Video Tutorials
These awesome videos came from InstitutionAwesome. Many thanks!
Config
Features
- Everything runs in threads for improved stability
- Option to preview rollbacks.
- Rollback areas on single players
- Records broken and placed blocks on the map
- Records exploded, burned and decayed blocks on the map
- Records water and lava
- Records players accessing chests
- Records endermen breaking blocks, blocks forming and spreading naturally, trees growing, ect.
- Config options for different kinds of events to log. Log what you want!
- Aims to be as light and nonlagging as possible
- Has a powerful indexing system, so it doesn't matter if you have 200 000 or 20 000 000 blocks recorded when you do rollbacks.
- Allows you to rollback ALL the actions of a specific player, with proper security clearance.
- Has automated log-cleaning, as well as manual. Both optional.
- Allows to rollback placed/broken blocks on specified area
- Allows you to rollback specified block type, placed/broken by specified player, on specified area.
- Allows to check single blocks or multiple blocks at a time
- Allows you to track activities of a specific player
- Allows you to check entries by a blocktype
- Allows you to estimate how well it is working on your server, this may also reflect lag caused by other plugins
- Allows to check % of valuable minerals mined by a person below 30Y
- Allows to check slaughtered animals.
- Records all your worlds, commands are relative to the world you are in.
- Failsafe. If SWatchdog encounters an error while running, it will attempt to fix most of the errors. If the error is severe, and it cannot fix it, it will disable it self. (If you find an error it doesn't understand, let me know. I will add it to the list)
- Option for automated log integrity check, and further option for automated log-repair, so even if you managed to blow up your database, it should be no problem.
Enabling wand
- Do /whelp 10 ingame, then follow the instructions. And yes, you can do everything from ingame.
Planned features
- Some sort of super-rollback feature to determine what an area looked like at given point in time, and then remake it
- Make WXRay better, show example locations ect
- Give an option to sort the results of sniffing to a file, so you can go through them (enterrandomamounthere) at a time.
- Add an option to notify admins when certain blocks are being placed.
- Add a thread for warning about possible xrayers
- Dragon egg teleport logging, as an option for creative servers.
- Logging only certain worlds
- WorldEdit logging. Purely as an option, disabled by default.
- Fixing few minor bugs in 1.18
- Suggestions?
Currently working on
- Option to warn when diamonds are being mined
- Option to warn when gold blocks are being mined.
Permissions & commands
Guide to time, rollbacks and some other examples
Can now be found here.
The config file
Installation
Place SWatchod.jar in plugins folder. Enjoy!
In case of a bug-attack
If you encounter a bug, unexpected behaviour or believe something is wrong, please:
- Look at console while running a command, if it fails to run it, it should report there with possibly the reason for what happened.
- Tell the contents of /plugins/swatchdog/ to me via PM or post a message below.
- Tell the latest ID from /plugins/swatchdog/util/ lastIDbroke.world and lastIDplaced.world (or the ID's for a different world, if thats where the problem occurs.)
- Describe your world, is it the default world? Whats its name?
- Post the content of config file, in the util folder
- SWatchdog version you are using, and bukkit version you are using. I have a deep interest in solving any and all bugs you might encounter, so please, just tell about them.
Known problems
- Doors do not rollback correctly. (Only the half that was broken/placed is rolled back.)
- /sniff look is not a waterproof command, so don't use it underwater.
Requirements
Please use the (craft)bukkit version mentioned in the file.
-
View User Profile
-
Send Message
Posted May 15, 2012@Sanzennin
it should not be the hard you could always do this. -logs brocken and placed blocks -records all actions (inclueds fire, lava, water ect.) -does rolebacks -difrent commands for rolebacks -allows you to check actions with a tool or commands.
thats not that hard. if you would like i could right up something for you and send it to you? just trying to help in anyway i can.
also take a look at my server and see it in action if you would like mc1.xlegoz.com:25567
-
View User Profile
-
Send Message
Posted May 14, 2012@Mrkuddl3
Hey, no problem. I'm happy to help. And I'm glad you like SWatchdog.
And I know the front page is a wall of text that discourages people to look further, but its just hard to slim it down, since the plugin has so many features and customizability. (Well, maybe the "Features" section could be summed up better, but other than that.)
-
View User Profile
-
Send Message
Posted May 14, 2012THIS IS THE BEST LOGGING PLUGIN EVER!!!!!
thank you so much for making such a good plugin, i have been looking for days for a plugin that does exactly what this does and you got it spot on thank you, you helped my server so much!!!!
-
View User Profile
-
Send Message
Posted May 14, 2012@Sanzennin
i just went to the other page looking for an awsner and i found it lol sorry to take up your time. just did that to the config and did a restart and now im going to try it. btw im glad there are still plugins that you dont have to set a a sq or what ever that is thank you so much
-
View User Profile
-
Send Message
Posted May 14, 2012@Mrkuddl3
Or... how about you just enable it in your config? Its already there :)
Just type in /wutil setconfig UseTools true /wutil saveconfig and finally /reload. Also make sure you have that particular permission to use those tools.
-
View User Profile
-
Send Message
Posted May 14, 2012@killer120070507
Ah, I think I know what the problem is. It is a bug that I recently noticed, namely, if you try to rollback an area that would go over either of the two borders that divide the map into four quarters, the rollback fails to do anything. So try with smaller area, while I fix the problem.
-
View User Profile
-
Send Message
Posted May 14, 2012you should add a feture that uses a tool like log does so that you can click useing maybe a stick or something just a little tip
-
View User Profile
-
Send Message
Posted May 13, 2012It says this whenever a command is run 2012-05-13 20:12:20 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
and yes it does show up the records with /swss broken feet
-
View User Profile
-
Send Message
Posted May 13, 2012@killer120070507
Hm... when using "/swss broken feet" while standing at the exact location of the grief, does it return anything?
Also, are there any errors in the console?
-
View User Profile
-
Send Message
Posted May 13, 2012@Hoot215 it was break griefing. we already tried to repair the database, still nothing
-
View User Profile
-
Send Message
Posted May 13, 2012@killer120070507
Did the griefer use "place griefing" or "break griefing"? Placement griefing would be lava, generally. If it was placement griefing, then you need to use "/wclean" instead of "/wundo". Also, try running "/wutil repairIntegrity" to ensure that your database is fully intact. Also, fire is logged as "(Burned)" I believe, so if the griefer burned anything, then rollback that player instead. Same with explosions, "(Exploded)".
-
View User Profile
-
Send Message
Posted May 13, 2012I'm having trouble with this mod. Recently we had a griefer, so we tried /wundo p:*name* 2000 -300 0 0 0 0
flying above the area. I'm told it undid a certain amount of blocks, but nothing happens, nothing at all
-
View User Profile
-
Send Message
Posted May 12, 2012@Jaso444
@Hoot215
Yes, I have succesfully rolled back a few world edits. Its usually not perfect, but it works.
Using /wredo does the trick.
There is no reasonable way to do perfect rollbacks for worldedit functions without hooking to worldedit or making a perfect copy of the map every few hours.
Hooking to worldedit would slow down worldediting commands for worldedit, and they're quite slow already.
-
View User Profile
-
Send Message
Posted May 12, 2012@Jaso444
It's basically impossible, sorry. I'd just recommend using standard backups for that.
However, if a logged structure was edited out, you could try using "/wredo". That might do the trick.
-
View User Profile
-
Send Message
Posted May 12, 2012Maybe roll back world edits?
-
View User Profile
-
Send Message
Posted May 12, 2012WUNDERFUL!!!
-
View User Profile
-
Send Message
Posted May 10, 2012@Luwiego
That feature is not implemented yet. Its coming, but it might take a while.
-
View User Profile
-
Send Message
Posted May 10, 2012@Sanzennin
How to should i undo a rollback i just made ?
-
View User Profile
-
Send Message
Posted May 9, 2012@Luwiego
Oh, thats a good idea, but... Ya know, it would take a while to go through 500+ players in the file, to allocate resources for listing those players and further allocate resources for the values that would be associated with each player. It'd be difficult to have it resource effective. I could go through everyone at once, but that adds extra checks per archive entry. SWatchdog reads (on the servers I've tested it) around 5 million entries a second. With the extra check and simultaneos writing, this probably starts to drop rabidly. Or I could go through the entire archive 500+ times (which is, ofcourse, even worse) It would need to be a (small) program of its own. (Otherways someone uses it ingame, and everyone has minor dose of complete server freeze for a second or two.)
I love the idea tho, I'll see what I can do.
-
View User Profile
-
Send Message
Posted May 9, 2012I love the xray feature ! You must add this one, like /wxray top or /wxray suspects, it would show like top 5 ,top10 or just a list of players that could be using xray. Admins wouldnt have to search one by one... ;)