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.
Comments
-
_ForgeUser7596480 Owner
-
_ForgeUser7502376 Ticket Manager
-
_ForgeUser8502299 Artist
-
View User Profile
-
Send Message
Posted Mar 19, 2012@wallofchaos
Well, the next update, once ready, should help with this by adding an integrity check, but basically, you most likely have an empty line on top of the placed.world.txt (This is caused by, for example, deleting the log file while the server was running, or adding new worlds without reloading the plugins)
Just remove the empty line, and that should do it.
EDIT: Update is ready. 1.07 now fixes your files integrity automatically on reload, if you enable it on config.
-
View User Profile
-
Send Message
Posted Mar 18, 2012whats with my log constantly. spamming failed to split a placed.world.txt, Retrying soon. But you might want to do it manually. #1 How would you do this manually? what am I placing in side the text files.
eh. no idea what this means.
-
View User Profile
-
Send Message
Posted Mar 17, 2012@Hoot215
Ahhh makes sense thanks for the help
-
View User Profile
-
Send Message
Posted Mar 17, 2012@DanVonTrap
The X-ray feature shows you the percentage of blocks that they mine under level 30. For example, if a person mined 99 stone and 1 diamond under level 30, it would show up as:
Stone: 99% 99.0 Blocks
[Skipping the other ores]
Diamond: 1% 1.0 Blocks
If the player has a very high ore ratio, like 10% diamond or something, then it is quite likely that they are X-raying (though maybe they just found a really good cave, so you should teleport to them and check to be sure. Look for dark passages with no torches, since they usually have fullbright or aren't even seeing the stone, and very small straight tunnels leading straight towards ores, and also tunnels that go straight downwards.
-
View User Profile
-
Send Message
Posted Mar 17, 2012So this plugin is amazing, my problem is is being fairly new to the hole xray thing i dont get the % thing with wxray i mean i do the command but i dont understand what it is showing me, im probably being a complete noob but im just not getting it, how do i work out if somebody is using an xray?
-
View User Profile
-
Send Message
Posted Mar 15, 2012@gysi1337
Oh, this could be the same bug that I noticed yesterday, namely, if you're undoing over an axis, that might mess up the command so some blocks wont get rolled back. I'll look into that.
-
View User Profile
-
Send Message
Posted Mar 15, 2012Ok wxray is still working@ Sanzennin. I wasnt below 30, sry.
But I found out something really strange. I wanted to rollback a whole house that a player has destroyed. I flew over it and typed /wundo p:player 50 -100 18 0 He griefed at 19:xx or something. The command was successfull but some woodenblocks were still destroyed, kinda randomly at some places in the house. I checked the blocks which were still destroyed with /sniff und it told me that the griefer destroyed them at 19:xx. So why are this blocks still destroyed? I flew over the house again and typed a even bigger radius... but this wasnt about the radius because some blocks got restored which were even farer away. Then I flew near some still broken blocks and typed a smaller radius /wundo p:player 10 -10 18 0 and it worked..
its really strange... it seems that if you too far away and want to restore something, that some blocks may won't rollback
-
View User Profile
-
Send Message
Posted Mar 15, 2012@borisgrishenko
Well, thats something I've never heard of. Can you send me the entire swatchdog folder, so I can take a look?
And, are you using /sniff look, or what is the exact command you're using? Placing a block, standing nexto it and typing /sniff rad, gives nothing?
-
View User Profile
-
Send Message
Posted Mar 15, 2012Hello Sanzennin, I'm trying to get your plugin to work correctly. For some reason it only records blocks broken, not placed. When I use the /sniff command on a placed block, nothing comes up. In the plugin files there's no logs of me placing blocks either. There's no error messages in the console about it, it is simply not recording any blocks people place. The only thing it registers is Endermen placing blocks. The config file is at its default settings.
Do you have any insight or suggestions to fix this? If you need more detail I'll be glad to give it, but I don't know much else to tell you.
Thanks!
-
View User Profile
-
Send Message
Posted Mar 15, 2012@bmnccrazed
since player is optional parameter, you need to enter p: in front of the player, as its described on the commands section. As well as block-type is an optional parameter, so you need to enter b: in front of that. If you're rolling back by the playersname, its more effective if you don't enter the block-parameter at all. That, and you are missing several required parameters too.
/wredo (p:PlayerNameExact) (b:Block) <radius> <Height>
<<time>>where ( ) is optional, <> is integer.
As for what is
<<time>>, please refer to http://dev.bukkit.org/server-mods/swatchdog/pages/guide-to-rollbacks-and-some-other-examples/Also, if this makes some blocks that the griefer placed appear, just do /wclean on the same area, with the p:GriefersNameExact instead of the person you're trying to help.
-
View User Profile
-
Send Message
Posted Mar 14, 2012Hi, My server is getting griefed a lot and I tried to rollback the griefs but it wont work, When i do the /wredo command I write: /redo Player Wood 2012 Player being the name of the person im trying to help, Am i doing this correctly or is it just broken? Thanks -bmn
-
View User Profile
-
Send Message
Posted Mar 14, 2012@Niaghaman
Hmm, and you are sure that the player in question has gone excavating already? They won't have a log if they haven't mined under 30Y, in which case, every number is 0. And there is no permission that would interfere with this. One thing that might, could be a bad index file, so run /wutil reindex just in case.
@mantegudo
Well, the reason I made SWatchdog and didn't use plugins like LogBlock, is mainly because our server owner wasn't too happy with them. For example, we do not have a MySQL database, our server host doesn't provide such a service. And we do not want to pay extra to get one, nor want to set it up. You might notice that LogBlock has an entire page describing how to instal it, as well as couple youtube vids, while SWatchdog is simply "Place it in plugins folder. Enjoy!" As for chest logging, its in the todo pile.
-
View User Profile
-
Send Message
Posted Mar 14, 2012@mantegudo
It has some of the same functionalities. Unfortunately, it doesn't log chest contents (yet), as this would be very resource consuming.
-
View User Profile
-
Send Message
Posted Mar 14, 2012@Sanzennin
Hello, I wanna know if this plugin has the same functionalities as logblock and if it logs the chest content.
Thank you.
-
View User Profile
-
Send Message
Posted Mar 14, 2012I also have a problem with WXray. Console sends me errors when I type wxray [nick here], and when I use in-game chat, it gives me an answer but every number is zero, like plugin doesn't count ores etc. It returns correct answer only for me (Admin with '*' permission), like there is a lack of permissions or something?
-
View User Profile
-
Send Message
Posted Mar 13, 2012@xdeathoreox
yeah, its been on the todo for a while, but haven't gotten around to it yet. Meanwhile /whelp will help ya to remember which one to use :)
-
View User Profile
-
Send Message
Posted Mar 13, 2012Suggestion:
Make an overall rollover plugin that will basically, rebuild an area. I found myself always forgetting which command to use, /wclean, /wundo, /wundo. So, how about /wall where it will place and break blocks to get it back to it's original form.
-
View User Profile
-
Send Message
Posted Mar 13, 2012@gysi1337
Hmm, does the console give any error while /wundo or /wxray? If you run command /wutil reindex, does that help?
Do you have any empty lines in the files?
Did you try to go to below 30, mine something, and try to look for the most recent wxray results with /wxray playernameexact 0 0? Does that work, or is it completely out of order?
-
View User Profile
-
Send Message
Posted Mar 13, 2012Updatet from v1.05 to v1.06 and wxray stopped working...
-
View User Profile
-
Send Message
Posted Mar 13, 2012@skillet_master
Well, to be able to remove all the lava, you need to log its spread. This is disabled by default as it tends to fill your logs with junk that most players do not need.( by default, only the placed lava-seed was logged.) However, you can enable lava-logging, and make it rollbackable, by changing the line: WatchLava=false to WatchLava=true in the config.txt. Also, due to lava spreading being natural occurance, the player name won't be tagged to every new lava block, instead, they are labelled as ' (Spread) '