Bukkit

Add optional functionality for the plugin to log commands that a player enters while on duty. This could be helpful for investigating the possibility of a rogue staff member by checking a log of their commands.

The plugin can log commands into a .txt file, with each unique player getting his or her own .txt file. This could lead to clutter, which is why the plugin should make a folder within the plugin folder devoted to log files. Multiple .txt files will make it easier to track each player down individually.

And for those (if any) who might be skeptical of having this implemented, it should be entirely optional, and the issue with third party loggers that can log commands is that it is difficult to tell if a player issued a command while on duty or off duty.

Do you agree that this should be a feature of the Duties Stats addon? I personally think it would fit in there more.

@TH3PF: Go

It would definitely fit there better, although, I personally think you should post a link to that page (on the plugin's main page) seeing as it's not on dev.bukkit. Unless you're planning to post that addon on dev.bukkit.

@CommodoreAlpha: Go

Do you think I should highlight this more on the page?

@TH3PF: Go

Oh... heh, whoops. Didn't see that there to begin with. With people like me, who just tend to skim things and look only for what they need, and those big ol' pictures you put out, that section looked more like a "Credits" section if you know what I mean. (It included names and links, so it didn't look like an "addon" section.)

But yes, you should probably highlight it more, and make it very explicit that those are indeed plugin additions and not "Credits" or "other plugins". Looking at them now, they seem really, really useful.

So today I finally got around to try to implement this. The progress I've made so far looks like this. I divided each dutymode "shift" into log sessions. The images only shows one session, for one player, but I'm pretty certain that it would work in other cases too. As only one player, I've so far found only a few bugs, including the one in the last image of the album. But it may behave differently on a big server, who knows?

I had to make a couple of changes to mainline Duties for it work so therefore you will need two experimental builds if you want to try it out:

Links removed

Additionally I made some changes to the page some days ago and I hopefully the addons section is more visible now.

Apparently I'm not allowed to post 3rd party download links here, so if you would like to get the files, please tell me how you want to receive them.

@TH3PF: Go

I don't see the bug in the last picture of the album. Is it that the title isn't centered properly? (The "[Duties - Stats - Logging]" portion.)

Also, as for getting the files, you could just email it to me at "[email protected]", that is if using email isn't against the rules somehow.

@CommodoreAlpha: Go

Yes, that was the bug I was talking about. I just sent you the email from: "[email protected]".

Sorry for not responding in a while. I got sick recently.

On a 1.6.4 CB R2.0 server, with ONLY the two files you sent me running, most of the features seem to run fine, but only after generic testing. (I only did what a "usual" player would do: run around, throw items, run commands.) I've yet to do stranger things like kill myself or actually run this in conjunction with other plugins.

One thing, and this may just be my idiocy, but I couldn't the command for getting the log (of a player) to show ingame, using the files you gave me. The "overall" log worked fine, but I couldn't get my "personal" log to show up. I looked at the .txt file for my log and it logged everything as it should have.

One small "disclaimer" that you should add to this logging feature is that it must be used with an actual logging plugin, as this is only used to "notice" rogue ops/mods. The actual details, like exact time and coordinates of each action should be handled by that main logging plugin.

I forgot to mention, the command for logs ingame is: /dutystats log [player].

Regarding the disclaimer, I thought the idea of this feature was to only log what commands the players entered while on duty. Was the details like time and coordinates, something you had in mind for the request? It wouldn't be that hard to implement that. The log file may look a bit more cluttery though.

Aw crap, I forgot about reporting back. I sincerely apologise for my irresponsibility.

Yes, apart from the fact that "logging]" was misplaced, it seemed to work perfectly fine.

For the request, what I had in mind was logging commands and actions with time and coordinates, so as to make it easier to discern if certain actions are malicious or not.

For example, it's nice to know that "Steve the Moderator" interacted with a chest, but it doesn't give much information as to what exactly this interaction was. Adding time and coordinates would be helpful so we would know which chest Steve accessed, and when he accessed it. We could use this information to locate the chest, then use another logging plugin like CoreProtect to look at what exactly Steve has done to the chest.

In summary, I mainly wanted this to log commands, but logging the time and coordinates of important interactions like chest-opening would also be helpful.

@CommodoreAlpha: Go

Well, I suppose I can add that. It does certainly seem to be useful.