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.
@Hoot215
If using /wutil setconfig WatchChestAccess true
you need to
/wutil saveconfig
and /reload too.
@AlvinTheChoster
1. You could simply edit the config file and change "WatchChestAccess=false" to "WatchChestAccess=true".
2. You should be able to type in "/wutil setconfig WatchChestAccess true".
Hi,
So I just downloaded this, and I wanted to turn on chest access.. I'm having trouble turning it on though..
I used http://dev.bukkit.org/server-mods/swatchdog/pages/the-config-file/, but I am unclear on what [key] is, and what [value] is. If you could type the command that would turn chest access on that would be great!
Thanks.
@codemanj94
These started showing up after you updated to 1.17? Okey, I'll see if there is something wrong with the tool using event.
@muggerfugger
Ok, and the console gives no errors? Does the log show (in the log file) for every block you break/place, or is the problem with the logging part?
Did you update to 1.17, and did the problems start occuring after you did?
@Sanzennin
i've had the plugin installed for a few months now, and i remember it working months ago. but havent needed to use it til recently. And i have updated it to the latest versions.
what i do is look at a recently placed blocked and type /sws l or look and it randomly will show me details on a block, but doesnt work for all of them.
i even tried deleted all the watchdog logs, and reboot the server to start from scratch. then i placed a block, and did it to that block and it didnt give me any info back.
some of my members built some new things today, and the command is only working on some. maybe some plugins are conflicting with it, but i dont have any logging plugins for this sort of thing.
http://pastebin.com/zFvkk36z Getting some errors. Not sure why.
@muggerfugger
Well, I'm assuming you just installed the plugin.
1. Make sure that the log you are trying to check has actually had actions. (After installing the plugin.)
For example, place a block, then look at it and do /sws l
Note that there is no way to get info on any block placed or destroyed prior to installing the plugin.
2. Make sure you are using the right command for the job.
For example, don't try to look for placed blocks with "broken" as parameter.
3. Make sure you are targetting the block you intended to target. As in, move the "aim" over the block you want to check while using /sws l, or stand in the middle of the block when doing /sws broken feet or /sws placed under
4. Make sure the blocks are getting logged. (Sounds like you already confirmed that they are being logged.)
@muggerfugger
If neither of those (in combination) work, please post a ticket containing all of the required information.
Doesnt work for me at all. Seems to create a log and log each block that is broken or placed. but sniff look returns zero historyv
http://owhatever.com/ss/EIS.png
@kyrosiakio46
There is the stick at the moment, I'll add a config for different blocks later. For the info how to enable the stick, do /whelp 10 ingame.
I don't know whether or not the plugin has this already... but could you add a feature where a player can just set a certain block, or item, as a tool. and just by rightclicking on a block, they get the history of the block.?
@Sanzennin
How long has it been? A day and a half? lol.
@Sanzennin
Well, it would seem that Bukkit has the best devs of all time ever. The file is still not here.
@Hoot215
Well, what can I say? The lazier the dev, the better he is. On an unrelated note, I've moved maybe 25 meters today.
@Sanzennin
Good to see that you've finally started using threads. This should definitely help with lock-ups. I'll get right on testing that.
v1.17 submitted. Probably takes a few hours before Bukkit staff checks it. Few being anything between 2h and 48h.
Major changes to the code, commands are running in threads now. I was a tad bit sleepy (as in dying of insomnia) while making all this, tell any bugs ya find asap.
@Wannab007
It depends on what you mean by that. It will log people placing and destroying Tekkit blocks just like any other, but versions suffixed with a "T" won't log most machines because they generate loads of spam. SQL support may come in the future.
@codiaz
Yes.
Is this compitable for 1.4.5?
does this log all of the tekkit blocks?
also can we get an option for sql
@Hoot215
The current source-code distribution method is quite sufficient in my opinion. We've been through this before, right? Anyways, lets take it to PM's.