FC_Bans
FC_Bans is the ultimate system for organized server moderation. This plugin allows you to perform all normal moderation commands such as, ban, mute, kick, and freeze. However, this plugin ties those mod commands into a system of warnings that keeps a history of key information about each punishment dealt to players. This creates a system of punishment records that staff can tap into to effectively resolve any player behavior situation.
This plugin also has a few features that it comes with included into its normal moderation commands. Muted players can’t place signs, you can toggle whether or not to announce global announcements for punishments through a command, all punishing commands can have reasons added for recording history, players are informed as to when their punishments end, players can be given immunity, and all commands have full permission nodes so that you can define exactly what people can and can’t do.
To get started using the plugin, visit this link: FC_Suite_Shared
For information on making tickets or contact information, please visit: Click Me
@Destro168
If you are subscribed to the plugin it emails you when a new version is out, even if it isn't approved yet.
I will do some more testing on the freeze bug to see if I can recreate it. It did damage when teleporting me back to the location. It appears if you are close enough to a wall when frozen, when you move away and it teleports you back, it damages you, and I think it might be a good idea to give frozen players godmode, you wouldn't want mobs/other players to kill them either while frozen anyway. (Also, the dmg might be coming from that weird suffocation bug in 1.3.1 that they fixed in 1.3.2
How are you downloading the file when it's not approved? o.o
Is that normal? o.o
Good feedback, I'll get to work tomorrow morning as it is 1 am and I'm hitting the hay. xD
Permission node -> FC_Bans.viewjoinwarnings If that doesn't work I'll go recheck code but that should be it.
I'll fix all the issues that you mentioned.
"I was able to kill myself by running around while frozen - I assume this only happens next to walls (it was suffocation damage) "
Could you elaborate more on how you managed to suffocate? Do you think I should add a temporary god mode to frozen players then? Even when you died, did you revive still frozen and stuck inside the wall, basically being completely trapped?
edit: I actually decided to go ahead and just fix the bugs anyway. I just need to know more about the freeze thing before I can fix it because I can't kill myself when surrounded by walls. Keep the bugs/suggestions coming. :D
@Destro168
Gonna download 1.0 and give it a thorough testing over the next day or two! thanks for the update!
EDIT: Initial testing - What is the permission node (or is there one?) For seeing the warning level when a player logs in?
Global Broadcast:
Check:
Kick:
Freeze:
I'll do some more testing soon.
I just want to post an update because... why not.
Anyway, I've been coding out FC_Bans pretty hardcore all day today. I updated all of the color scheme stuff that I had previously ignored, a truly GODLIKE chore that took like 2-3 hours alone. But I won't go into that.
Anyway, the color scheming is done. The time conventions that I was using to parse commands has been updated heavily and thrown into FC_Suite_Shared because I plan to have it used on FC_Rpg.
I also think this is an important time to point out that I actually NEVER make changelogs before I start coding or while coding. I pretty much wing it 24/7, lololololol. So this next update will have a very small changelog aside from mentioning a few new features because in all honesty I've had to do so much minor tweaking to everything to make sure that everything looked good and was working properly that I won't be able to remember all my changes this time. I had to make sure you could properly ban players who logged off and make sure that you could do everything in the console and blah, just a lot of usability upgrades and testing of features.
So 1.0 should be out either tonight or tomorrow. I'm going to release on the next version just because I think everything is pretty solid and I don't expect to have to make any real changes to the plugins core functionality and I can update at will if needed in the future. Also, it's better if I just put at release because if .9 was completely bug free then we'd be stuck on .9 BETA for a perfectly stable release, lololol. It's pretty much done but I want to go about adding the freeze command now since everything is working good. I'm going to also go through peman3232's suggestions once more and other suggestions to see what else to add and what else not to add (btw I added the warning level on join thing already, I had to add it immediately cause the idea was so good, ^^).
edit: Pushed out release tonight so I can be on bugfix watch tomorrow. Enjoy the release when it's approved. Wish meh luck D:
Also, in regards to file size ->
76.5 KB -> 95.4 KB jump. That's like... 18.9 more kbs or a 24.705% size increase, if the calculator I used was right. Wow! That's a lot of changin' D:
I kind of like the recent check thing the most. I can do this pretty easily as it will be purely in memory and not stored in the file. This will, of course, wipe every time you restart/reload your server. I don't really want to deal with storing recent issues with all of them. It's a good suggestion, I'll try to do it in a way that is cool :P
I really like the warning level on join idea a LOT. I think this is pretty legit, definitely going to put it into the next version.
And I 'might' do MySQL. I can set it up again and relearn the language but just don't expect this any time in the near future. I would have to run many experimental builds for it though, totally separate from the main build.
I had a few other ideas for tracking abusive staff members and helping track things in general.
Perhaps add temporary logging to each command so that you can issue a '/check recent ban' or '/ban check recent' something along those lines and see the last 10 of that type issued. That way if you do a '/kick check recent' and there's 10 kicks by the same staff member you can look into it.
Or you could log the commands to staff members when they issue them in addition to the user they used it on (but that would double the amount of logging). I know you said you have no way to test mysql but a mysql database would make lookups to check for abusive staff really easy.
Another thing that might be nice is some messages to staff (with the correct permission) that will tell them the warning level of someone when they log in. (perhaps only if it is "high")
Say if steveo203 logs in, the plugin can run a check when he logs in and sends a message to all of the staff with 'FC_Bans.message' if his warning level is classified as "high" as determined by the config file.
Just a few ideas,
I was using the plugin and I found that there is an issue with banning players, *woops*. The /ban command is buggy and um, there are a few other things. Old console immunity is gone but I am reinstating that. Expect a hotfix build out soon.
The ips are actually meant to stay stored in the FC_Bans config. The ips do not contribute anything specific and are there just for logging purposes.
I know Essentials stores ips now, but if you happen to not run Essentials for some reason, well, now you can see player IPs and you can ban their ip by checking the file. Or if you ever need to see a players ip for some reason and just can't get it, well, it's there now. There is a configuration option to disable the feature if you want and you can merge the old header with the new header if you want ("PlayerIps" with "PlayerIps (You can delete this... blah blah")). Again, the sections are totally optional.
Glad it worked for you and thanks for the feedback! :D
@Destro168
I lied. I went ahead and ran 0.81 on RB1. (apparently I can download files before they are approved if I am subscribed.) I haven't done much testing yet. The bans and warnings all transferred to the the FC_suite folder. But the IPs didn't. And it doesn't appear to be storing IPs in those files at all (still in fc_bans config).
Cool thanks peman32323 :D!
The changes are nice. I will wait for 0.9 (and hopefully RB2) and give them another thorough testing. RB 1 doesn't run all that well, so I am not really running it much atm.
FC_General.jar is a library that is shared between all of my plugins. It is required to use my plugins. It is hard to maintain all 3 plugins and I rewrite a lot of very common functions. Essentials/Multiverse do the same sort of thing, but instead of making something like EssentialsGeneral, Essentials.jar itself is used since it is required to use any of the Essentials plugins. Same goes for Multiverse, you require Multiverse to use the other multiverse plugins (I think though, not 100% sure, don't quote me). In my case, my plugins all have a lot in similar and I don't think it would be right for me to make it so that FC_Announcer is required for FC_Bans to work. Catch my drift? :D
There are two .jars I dont understand why.
Actually peman3232, the newest update isn't approved yet. But thanks for the enthusiasm ! The latest version is actually 0.7.
@Destro168
New update looks awesome, and the planned features are really exciting as well. I am also mainly waiting for a stable 1.3.1 CB build before I do much of anything.
New version out. The next version will probably be the last version before I go to release. I'm waiting for 1.3.1 to come out before I release it. So expect a little bit of a delay on it.
I will try to finish it tonight/tomorrow, but I want to make sure it's nice and bug free and also put up graphics/art/video and make everything fancy like the new FC_Announcer page and try to finalize it. After that I'm going to try and perfect FC_Bounties (seems pretty bug free, but I want to test it out to be sure).
Sadly very low. I know mysql, don't get me wrong, I just have no test environment for it locally and my dedicated server doesn't have it added.
What's the chance of mysql integration?
It already automatically records the time that and date that any offense is given Gameitall. Maybe I don't understand what you mean?
Thanks for the feedback! :)
Hey just used this plugin on the server :D OMG so much better than some of the other ones we used. it would be cool if you could add color options and make it so you can record the date and time of the issued cmd Example.
after giving the cmd.
1. [7/20/12] (2:00) [username] warned Spamming Chat! 2. [7/21/12] (2:00) [username] warned Fast moving! 3. [7/22/12] (2:00) [username] banned Hacking!
ECT.........
Idk just some ideas if your looking for any. Waiting to use on our 80 slot server as soon as it comes out of beta :D
good build!
(Mike)