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
Fc_bans not work! I try to put Vault, but not works. I put plugin in /plugins but when I ride in game /plugins there is not fc_bans:( What to do? I now that im stuped.... Nut pls help me!
Finally got all my plugins on github: https://github.com/Destro168/plugins
From now on I will no longer be including the source for my plugins inside of the file. You can view any and all source on the github (:
(unique post thingy 2)
The reason why is because the format for the command is /ban [name] [duration] [reason], just as listed in /fc_bans. It isn't really meant to be used out of that format yet. I am looking into ways of detecting non-duration strings but the main reason why I haven't added it is because if you accidentally skip the duration and put something that 'looks' like a duration into the command, it can cause you to accidentally temporarily punish somebody when you want to permanently punish somebody.
The solution to this is confirmation messages but the problem with that is then the whole process is 1-step longer. So I'm looking at ways to analyze the reason string such that it isn't checked as a duration.
new issue if you type /ban (playername) (Reason) it doesn't ban them they can rejoin the server.
But typing /ban (playername) 10m (reason) bans them and stops them from rejoining.
Not sure why the first one doesn't work it should.
fixed it Didnt realize the Suite was a Dependency :)
Alright so the first update to the FC_Bans page is done. I'm going to go over it again later for typos, errors, etc. so if there is anything you want to know more about that isn't covered on the first page or in the video, feel free to post a comment.
For a duration you can type in "perm" + anything else. So you can type in ->
permanent, permature, permfjoieajioejwaio if you want and it will perma-ban. Or you could just type in anything that won't tranlsate into a duration and that will perma-ban.
@Destro168
Question, how would one go about a perma ban?
Triple post still don't care!
Uploaded 1.11. Enjoy it! Tell me any bugs if any come up. Should be pretty solid now. Going to start working on art/video, etc. now.
edit: No quad post. Updated to 1.12. We have a new video now -> http://www.youtube.com/watch?v=HtGoTLQNqk0! :D Going to finish the art and stuff tonight, might not actually get to put it up tonight but it should be done tonight. Then I get to update FC_Bounties a bit more and get it to a more mature state, then should be good to go moving forward.
Double post but I don't care.
My plugin is pretty solidly updated. However, I lost my changelog....... So, yeah, this version is coming with no changelog. Um... it will have fixes, xD. Oh well, I'm looking to get all the art-video stuff done this weekend. Should be good to go, college is together and my plugin is looking good to get uploaded. Finished the FC_Bounties update so I'm ready to move on over to FC_Bans.
"The plugin documentation is terrible. To get known what is the syntax of /ban command, I had to download the plugin and look through the source code. I haven't even know you have time (temporary) ban feature. Btw. you should use sth like github to keep source code instead of putting it into JAR."
Thank you for your, erhm, rather blunt feedback. In regards to the documentation, The front page is actually not updated yet, as I haven't reworked it fully or added the art/graphics. The "Updated Main Description" actually refers to the version that I have on my computer and isn't actually what is on the front page.
I'm mostly settled into my dorm at college so I am going to begin coding the plugin this weekend again very likely. I have a lot of updates on my current version, but like I said before, I can't release because it's mostly untested. I also want to add a few more features into the next version to make it better.
In regards to Github, I was unable to figure out how to use github, hence the fact that I am not using it. I have a lot of technical issues trying to install/use it, so, yeah, I just couldn't figure it out *shrugs*. I've said somewhere else I will try again in the future, and I do plan to, but for now it's just not something I am capable of doing due to lacking the skills.
"I am NOT going to use this plugin until you make a proper documentation (like this for example)""
Ok that's absolutely fine. Thanks again for the feedback.
The plugin documentation is terrible. To get known what is the syntax of /ban command, I had to download the plugin and look through the source code. I haven't even know you have time (temporary) ban feature.
Btw. you should use sth like github to keep source code instead of putting it into JAR.
I am NOT going to use this plugin until you make a proper documentation (like this for example)
I've actually been considering possibly using the speed hooks since I saw them, I just have to test to make sure I can actually set them to 0. If I can set them to 0 then it would definately be the cleanest implementation of a freeze. Sorry about lack of updates, caught up with server stuff/fc_rpg. I do still have a pretty nicely updated version of FC_Bans right now that I'm using but it's not really ready for release. And I still didn't add the yes/no thing yet.
I'm actually going back up to college this weekend so I might not even get this update finished this week... just so much going on right now.
edit: Playing around with speed. Can't get it to work. I mean, yeah the bukkit code is 'saying' my speed is changing but nothing is actually changing on the server/my client. My thing with changing the speed is also that clients can change speed so I wouldn't want cheaters bypassing it so I think my current method will just stay. It's a lot more 'guaranteed' that they can't move since the server is manually checking their position every 1/4th (or 1/2, can't remember) a second.
@Destro168
I was wondering if the new speed hook in R2 would make freeze easier? If you just set all of their speeds to zero.
http://dev.bukkit.org/server-mods/playercontrol/ is a plugin that uses these new hooks it would appear.
Just an idea, freeze works well enough as is.
Eh, got very worked up working on my server/FC_Rpg today. I really needed to put some hardcore server maintenance into it today by fixing all the bugs in FC_Rpg and updating all the plugins, etc.
So all the stuff I said I'd have fixed today, I'd say will be put on hold until either tomorrow or Monday. OH WELL. Just a bit more, at least nothing is "broken" and the bugs are really only cosmetic so I don't really feel too rushed about getting this pushed out and want to make sure that it's done right. :p
@Destro168
"I do think that the warning that you are about to overwrite a ban would be nice though and I will probably consider adding a [yes/no] prompt."
That is a good solution I hadn't thought about. This seems like a pretty good idea.
"Ahh, I actually overlooked the fc_bans command. When it says "Unknown command sender", that means that you aren't using a colouredconsolesender to send your command, which is what I happen to use."
I run my server from windows and use the default windows console if that helps.
"When a banned player tries to log in it sends the warning level message. "
I actually very intentionally coded this in. Personally I like knowing when banned players try to join. And remember that only staff will see this (admins), so it won't spam normal chat. I can add a config option, I'll note that.
The ban overwriting is also intentional. I know it might seem like I just overlooked that but I actually like that it overwrites. However, I think maybe I will send the person who overwrites a warning that they just wrote over a ban. That would be a good feature.
The reason that they overwrite is because if a person is banned from the server, what could they possibly do to increase the length of their ban? I mean, they can't break more rules on the server to be banned longer. The other thing is if you add the ban times together, well then you might have issues in which a player bans a player and then later another staff member bans that player not knowing he was already banned. A perfect example is, "A spammer logs onto your server. You have 5 mods that instantly ban him for 5 hours. Well, of course they didn't intend to ban him for 25 hours, but they did. So yeah, xD." Of course global announcements can help with this but meh, if you are rushing/not reading you could mess up and then you would have to use /warn remove several times and /ban remove and then use the ban command again. It could just be hectic. I think the current overwritting is best. For your example of finding more reasons to ban him, well, I think that it would be better if you just looked at the players current bans and then decide how long you want the new ban to last based on how much time they have served. :) I do think that the warning that you are about to overwrite a ban would be nice though and I will probably consider adding a [yes/no] prompt.
"Note: I assume freezes and mutes work the same way as bans, but I won't get around to testing that until tomorrow."
Indeed they do!
"How do these functions work? Does it prevent multiple accounts from ever logging on from the same ip? Just at the same time? Only if someone on that ip is banned?"
I will explain these on the front post. I forgot to do this, my bad. Overlooked it.
"I tried testing some of the console commands - they all return unknown command expect for "fc_bans" that one returns this error. "
Ahh, I actually overlooked the fc_bans command. When it says "Unknown command sender", that means that you aren't using a colouredconsolesender to send your command, which is what I happen to use. There are probably a few more cases but if you are seeing the debug message that's good because normally you will get errors if that isn't caught. I'll look into other types of senders and try to work them into the plugin.
BUG: When a banned player tries to log in it sends the warning level message.
NOT REALLY A BUG: When you ban a banned player the newest ban overwrites the old one. Example would be, I ban STEVE023 for 10days, if for whatever reason someone then bans him for 1day, he will only be banned for 1 day. This isn't really a bug, but just a question of how that should be handled.
I don't like the idea of having to /warn remove to issue a bigger ban. The options seem to be
Personally I think cumulative bans make the most sense to me. The situation this is most likely to happen is a mod will ban someone for griefing for 5days, and then later another mod finds other griefing or rulebreaking of some sort and bans him for 3 days. It would be best to add the punishments together.
Note: I assume freezes and mutes work the same way as bans, but I won't get around to testing that until tomorrow.
A few more things I was wondering about.
PurgeAllMultipleAccountUsers: false PreventMultiAccounting: false
How do these functions work? Does it prevent multiple accounts from ever logging on from the same ip? Just at the same time? Only if someone on that ip is banned?
I tried testing some of the console commands - they all return unknown command expect for "fc_bans" that one returns this error.
@Destro168
Haha, that's fair. I really don't think it's a big deal anyway, they should be able to figure out that moving will hurt them after 1 or 2 hits and it only does half a heart.
As a side note, I just noticed that files show up in the files page before they are approved as well, just not on the main page of the plugin.Nevermind, that is just because you added me as a tester, the subscription emails are the only way for people to get access to it before it's approved.
Ok I'll look into a solution. Maybe I will just make sure that the location that the player is frozen in is "safe" before actually setting it up. I think that will fix it pretty nicely. I won't do the godmode just because it would be a lot more code to add, haha. I'm not lazy but it doesn't seem worth the effort. Maybe I'll add it one day when I'm not neck deep in projects.
That subscriptions toolbar is pretty useful. Hm, never noticed it, haha. Guess I'm going to subscribe to my plugins 'derp'.
edit: OH YEAH. I have to add the ban exporting feature... forgot all about that. I'm going to try to squeeze that into the next update.
edit 2: Oh I didn't know you could download them before being approved. I knew they were there, just didn't know you could download, haha.
edit 3: Ahhh ok that makes sense! Thanks for being a tester :D