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.
@Sanzennin
I know that. I was just saying that I only made the one change, so I don't see the point in posting a changelog. And why don't you want me to post the code on GitHub?
@Hoot215
Changelog... you know, it doesn't contain any code, just a short description of changes you've made for the version.
Like:
v2.0T
-Fixed bug causing cows to fall down mid-flight
-Added wings to pigs
-Solved world hunger
And don't post it on GitHub. :)
@Sanzennin
I'm not sure what you mean by that, considering that I only really made one change. However, I can post the code on GitHub if you want. I already have a Git repository setup locally for tracking version changes, so it wouldn't take long for me to set it up on GitHub.
@wormzjl
Yes, that would be why it isn't working. In that case I'll just add a config option.
@Sanzennin
I changed the block id of the chest and it shows up like X950:0 for an iron chest.
@Hoot215
It seem that the custom build is not working for me as accesing iron chest is not logged in chest.*.txt. Probably because I changed their block IDs? (I'm running on mcpc build 183 btw)
Adding an config for custom blocks shuold be really nice.
@Hoot215
Do you have a changelog for that?
@wormzjl
Try this custom build: LINK
It has support for the following in addition to regular chests:
I can add support for other blocks on request (or perhaps even add a config option for it if you want). However, note that this version does not have the usual Tekkit changes, and it will still log most machines.
@Sanzennin
I can give you the source on request if you want to pull the changes.
@wormzjl
If you place those chests, do /sws l at them and tell me the exact name of the item, then yes, its possible, I could make a update for the Tekkit version. But what do you mean with custom inventories? IC2 and buildcraft machines are disabled from the logging because they would add so much garbage to the logs. (Most of the Tekkit users specifically asked for this.)
Hello, is there anyway that this plugin could support logging for modded chests (iron chest mod for example) and custom inventories (like IC2 machine access logging)?
Hmm, as far as I know, it should be working with 1.4.4. Post the error you're having.
@blueshfit_1
Please post a ticket containing the required information if you suspect something isn't working right. At a bare minimum, the error is needed to actually fix this problem.
Is there a estimate of when it'll be ready for MC 1.4? As of right now /wundo is not functioning on our server.
@Dhesterfan
@Hoot215
More precisely, every file that has "T" after the version number is aimed at Tekkit. Everything else is for "normal" MC.
@Dhesterfan
No, but it has support for Tekkit.
Is this only for Tekkit?
@Hoot215
@shadvalentine
Well, I considered it. But as you can hardly grief a players inventory, there really isn't a point. Unless you meant like "upon death" inventories? That I could actually add.
@shadvalentine
Not currently. While this is possible, I doubt it will be added to SWatchdog. However, Sanzennin may believe otherwise, so stay tuned regardless.
Is it posable to set it so we can rollback a players inventory?
@flamingotrainer8
First of all, I don't think you can use block IDs as the block. You'll have to use the block name instead, so in this case "GRASS". Second of all, you didn't enter the time. If it happened today, append " 0 0" to the end of the command.
@Hoot215
I say the command /wundo p:BloodStorm3 b:2 10 10
@flamingotrainer8
Looks like you're not entering the command in the proper syntax. Could you please post the exact command that you used?
Also, for future reference, please use a site like pastie.org to post errors. It's much easier to read.