Inactive [SEC/ADMN/EDIT] SWatchdog v1.14 - Log and rollback griefs[1.2.5-R4]

Is there a way to check chests if people have been stealing from chests? Also a wand tool that only admins can use for this (like bedrock or ice) would be great in the next update

Well, simpe way is to have a block above the chest. As for the interactions within the chest itself, its an upcoming feature.
As for wand too, it cannot be placeable block. (It is most likely going to be a stick, as thats generally what people have requested. Or maybe a wooden hoe.)

Hey. WXray won't work right. (i think) When i do the command it says Sniffing and then 0% everywhere... Please help?

Go to your main world, dig down to 20, break some blocks, do (fror your self) /wxray PlayerNameExact
still 0?
Well, post your entire SWatchdog folder to a place I can download it from, I'll take a look. (Or read the "in case of a bug attack" on the swatchdog devpage.)

A stick would be fantastic but make sure that there will be some some permissions thing that only Admins can use the stick for SWatchDog and it doesn't work for others. Also im excited for the interactions within the chest!!

I can`t get it to work right (rollbacking). One time it works, the other it doesnt.. If i try /wundo p:nick 10 10 0 0, does nothing. If i do /wundo p:nick 10 10 15 30, also does nothing. The same with the clean and redo. But i think i get the problem when i specify a player.

Now its working... Freaky...

Can you undo world edit griefs?

Hey, theres a bug with rollbacking. I rollbacked a griefer. With command /wundo p:nick 1000 1000 0 0 0 0 0, and thats what happened. http://imageshack.us/photo/my-images/845/swsbug.png/ . Sometimes players creation get glitched like this without rollbacking.

How can i rollback radius 100 height 100 (all blocks) 2 weeks ago?

I love your profile picture. =) XD
But also, you really need to do a lot with this plugin. For example, you really need to make it so that you do not have to type in so much just to rollback and check blocks. Make it like a stick or log thing like BigBrother or HawkEye. But please, whatever you do, do not make it so you have to make a MySQL. That is the hole reason I came to your plugin. It is just to complicated to set up a MySQL. I love that you can just pop it into your plugins folder and BOOM. Your done.
Great plugin. I use it for my server, and I say its a good plugin for anyone out there who is looking for a plugin for griefer checking.

If it happened yesterday, you need to give the date, if it happened last month, you need to give the month too. Also, if you are using playerName, make sure you use playerNameExact, so p:Sanzennin instead of p:Sanze for example.

Depends. If someone removed a house you built, then you can use /wredo to bring it back. Some blocks might face the wrong direction though, for some reason. Seems bukkit changed that functionality just recently.

When they randomly glitch, its not swatchdog. But as for that picture, the bug is... the wood type? Well, since you gave it 0 0 0 0 0, it took the earliestmost records. If the color of the house was changed later, you should use the date closer to the grief.

its 3/4/2012 today, so (Assuming you're op) /wundo 100 100 0 0 16 3 (That will rollback anything in 100 radius, 100 up (use -100 to specify the area downwards) after the clock 0:00 on 16th day of the 3rd month.)

yeah, I know, I'm working on it. Just need to come up with a few more amazing ideas. Besides, checking a block is just /sws l, thats not too much in my opinion, 5 symbols.
Rollbacking needs some care, I agree.
And yeah, I dislike having to set up the MySQL database or a half a million configs too, so if I ever give the option to use MySQL, its just that, an option. So you can still just toss the swatchdog.jar into the plugins folder and be happy about it.

And sorry for a bit of a late reply for some, generally I notice it quicker if you make a ticket at swatchdog devpage.

Thanks for replying. Finally someone who actually cares what we thing. =)
As for the block history with /sniff l, I agree that is not much at all. While the rollbacks, which I agree on, need some care. Thanks for a great plugin.

Hi, so how to rollback just explosions or fire damage ? The p:Exploded doesnt work.

Because Exploded could be a playername. (A crappy name, but still.) Write it exactly as it appears in the logs:
(Exploded)
instead of Exploded

There are a few issues with muti-worlds... It only wants to rollback in some worlds, some of the time. It still /sniff's everything fine. It just has problems rolling back. It will try to do it.. and rollback 0 edits. I don't have any logs for you, sorry.

Hmm... thats odd, since, I'm rollbacking just fine with different/custom worlds. One thing causing trouble could be... If those worlds were created while server was running, there could be an integrity problem. Try enabling integrity check/autorepair in the config, restart server. Then try?

I'm not sure how the rollbacks work (first time working with rollbacks).
I got my friend to build a 5x10 wooden house. I then filled it with lava.
I used /sniff rad and got when I placed the lava.
Then I did /wundo p:Wolf1026 [Idk how you got this number] [Idk how you got this number] [Hour] [Minute]
I'm not sure how you find the 2 numbers in the middle, and I want to figure it out before I release the server this Saturday.

Oh, those are in the rollback guide and ingame help too. Basically, its /wundo (playerNameExact) (b:Blocktype) <radius> <height> <<time>> where () is optional.

So for example, standing inside the wooden house, somewhat in the middle, you'd use /wundo p:Wolf1026 5 10 0 0 (for rollbacking things that happened today.) I assumed the height of the house was 10. Doesn't really matter if you exaggerate the height if you got nothing but air above the house. Ya rarely need to be too precise with the radius too. Just throw something somewhat close to the desired area. (Unless you're working in a _very_ tight city. )

Also, if you want to use /wclean to clean up the lava, pay attention to what you are logging, and what you are not logging in the config.txt. Some of the configs are disabled by default to keep the servers running light, but if you really need them, you can enable them. Configs such as entities changing blocks (thats sheeps eating grass for the most of the time), chest access, water and lava spreading and block physics are disabled by default, as they are useless for the most servers or just plain eat up more resources than what they are worth. Ofcourse, someone else might give value for these differently, thus them being options you can enable.

um you left all the stuff you placed and broke in the swatchdog folder -_-

Hmm?

Oh, thanks.

Wanted to say thanks for supporting Tekkit : )

When i type /wundo i get intel error so now i cant undo grief..

Try restart your server. It usually happens when you reload your server

Fixed it also. When someone set's fire to something I cant tell who it is it gives me no names

Remember that when you set something a fire, you are actually placing a fire block. So look at the "placed" records for the area instead.

San, don't you also have a feature which let's the user sniff using both logs at the same time?

I'm having a problem, I can't use the stick to check for broken/placed blocks? I have the perm.

Do you mean broken and placed logs? Or old and new logs? Well, /supersniff look checks all logs imaginable. (/sniff look checks recent broken, placed and chestlogs.) Just replace /sniff with /supersniff for whatever command you want to use for log checking, to look the new and old entries.

have you enabled the tools in config? Its something like "UseTools=true" (Its "UseTools=false by default.)

You can also change config ingame with commands such as
/wutil showconfig (<page>)
/wutil setconfig [key] [value]
/wutil saveconfig
/reload

so to say it simple, run
/wutil setconfig UseTools true
/wutil saveconfig
/reload
Its that easy! =D