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.
Hey, I was wondering if logging worldedit has been discussed or thought of to add to SWatchdog.
@landontc
Oh, that is currently in the TODO, it's not in the plugin yet.
How do you disable SWatchdog from logging certain worlds?
That could be it! Thank you. Again, we do like this tool as it is quite powerful without immense lag. And it let's us keep the vanilla setting on our server. Thank you again.
@LosaruTaiyo
Have you enabled chest logging? If so, you can see who accessed the chest and when by using /sws l on the chest. (Doublechests are 2 individual chests btw)
The plugin does not (yet) record transactions, since as the bukkit is currently, there is no efficient method of getting single transactions.
No errors so it could be either older griefs or just us trying to get used to the program.
Another question. It says this logs chest activity? We can't seem to figure out how and we've had recent thefts from chests. Or is that a future detail that accidentally went in with the features?
@LosaruTaiyo
Supersniff should work in the same way as sniff. Make sure the records you're trying to find actually exist in the logs. Are there any errors in the console? And whether or not you use the plugin offline has no effect.
We use this program on our server and it works great for immediate issues, but we can't get the supersniff to work. Someone said it was because you had to use it offline? Any help would be great though. Aside from thefts, this plugin has caught us a few griefers.
@GODDAMNBBQ
Just rollback the player '(Exploded)'. Make sure you have your radius and time parameters correct as well.
I'm having trouble figuring out how to rollback tnt damage, anybody help?
@Lostferret13
Oh, special chests aren't logged yet. (Yeah, I know the tekkit version is dragging behind a bit, since there aren't that many tekkit users compared to regular MC. But I'm not going to abandon Tekkit, because I love it myself, so don't worry. :) )
Also, if you are planning on giving the wand to the regular players, I'd advice against it. It hardly matters how good a plugin is if a group of players decide to go on a spamming spree with the wand. It's an easy way to spam 10 commands per second per player. 10 players = 100 cmd/s, 6000 cmd/min.
Of course, if you meant moderators or other responsible players, that's the intented target group for such commands.
As for the wand, did you: Enable it in config, give yourself the permission to use it? If so, check if its working by destroying a block and placing a block in the place you destroyed a block from, then left click, then right click while holding a stick.
hi Sanzennin.
I am using the latest TEKKIT version of your plugin (thanks for the support btw!)
I got The chest logs to work, though It does not tell me what people took.
How do I set up Wands? It is too confusing for some of my players to memorize the commands and I would love a quick way for them to lookup information on broken, placed, and chest access.
Many thanks!
@Lostferret13
For checking chest access, do /sws l while looking at the chest.
Also, what version of SWatchdog are you using? Latest tekkit, or latest regular version?
On a tekkit server, How do I activate the wand? /whelp 10 doesn't do it.
also, what is the command to check chest access?
@Hoot215
@eprimex
Not to mention you don't need to really set it up, unless you want to change the default config. Which can be done in game while the server is running. You don't need to make it connect to SQL database, you don't need to find the textfile you wrote your SQL databases password to, you just throw the .jar into plugins folder and that's that.
@eprimex
It's far more lightweight, and doesn't require an SQL database.
the question is; WHY to choose this over logblock?
@deleted_10274781
There will be updates when there are new features / things actually need to be updated due to bukkit changes. Latest SWatchdog version still fully functions with latest Bukkit beta version.
If you have some sort of problem, malfunction or just generally need help, provide more info about the problem you're having as per stated above.
Looks like rollbacks doesn't work. Can you please update the plugin ? Thanks :)
@LeeTheENTP
Well, naturally you can't find out what happened before the plugin was active. It's not called a "logging" plugin for nothing ;)