| Fish Tank Clan :: Forums :: General Forums :: Server: Fish Tank Classic |
|
« Previous topic | Next topic » |
| Rules Change? T Hostage Killing | ||
| This topic is now closed |
| Author | Post | ||
| Vincent Vega |
|
||
Registered Member #578
Joined: Fri Feb 23 2007, 07:00AMPosts: 176 |
Jesus[tzahal wrote ... Wow that's not confusing or anything to read, Steel ] Well, there is the time where we can say "ALRIGHT GUYS KILL ALL THE HOSTIES AND RUSH SNOWMAN!!!" but that usually only happens in a full server and it's a fun round. What can be made possible is: T Player; must have at least 2 hostage kills IAR to have it count towards the counter. If counter reaches/exceeds six in a course of three rounds then a kick is issued. T Player; must have at least 2 hostage kills IAR to have it count towards the counter. If counter reaches/exceeds twelve in a course of thirty minutes then a temp ban is issued. -- That means that if you go 2 hostages a round, you need to do it 6 of 12 rounds (12 rounds being that 12x2.33=27.96 minutes, which is basically 28... 2.33 being 2:20minutes) This means that if you kill the asian hostage and JUST the asian hostage then it won't count. Also there will need to be an auto-clean off feature (i made up that feature  ) where it will disregard any killings more than thirty minutes prior. Meaning, if you kill 10 hostages with 28 minutes in, it will drop the first ones when it gets to thirty.The problem with the time limit: You can reconnect. Unless there is a way to store the info over a reconnect that may the only problem which means that the next scenario that you can do is: Kill all four hostages two rounds in a row I don't know what I am saying anymore so I'll leave it for now We could also have the option (Dont know for sure) of giving those hosties some more health and keep the regular system in place. That way, if hosties are killed we can be sure its intentionally. Only downside I see at the moment (drugged) is that hosties would be an awesome human shield. |
||
| Back to top |
|
||
| aborted fetus |
|
||
The All-Cum Diet
Registered Member #47
Joined: Mon Dec 05 2005, 04:55PMPosts: 1888 |
I have long since been an opponent of hostage killing. I feel that not only does increase the round time, but it also changes the dynamic of the game – turning a hostage server into a DM sever. There are times when the CT killing of hostages can be strategic. We’ve all performed the ‘rescue two, kill two’ strategy before. However, non-strategic hostage killing by CTs (simply killing them all) should be an offense. Furthermore, I really can’t think of a legitimate reason why a T would ever need to kill a hostage. I think that making hostage killing a server offense would be beneficial. The script looks interesting, and would be great if it could be set to compound hostage killings by the hour. |
||
| Back to top |
|
||
| Wildcard23 |
|
||
Registered Member #514
Joined: Wed Dec 20 2006, 06:33AMPosts: 1067 |
I hear what you are saying Fetus and I agree. My only hesitation is, like I have said earlier, that I don't want to end up banned or other people banned for throwing grenades at CT's who have hosties following them or strafing a hostie during a gun battle. I mean, nothing is perfect, but just something to keep in mind. 
|
||
| Back to top |
|
||
| aborted fetus |
|
||
|
The All-Cum Diet
Registered Member #47
Joined: Mon Dec 05 2005, 04:55PM Posts: 1888 |
Wildcard23 wrote ... I hear what you are saying Fetus and I agree. My only hesitation is, like I have said earlier, that I don't want to end up banned or other people banned for throwing grenades at CT's who have hosties following them or strafing a hostie during a gun battle. I mean, nothing is perfect, but just something to keep in mind. Yeah, that is a good point. I know that I have killed many hosties while in pursuit of CTs. |
||
| Back to top |
|
||
| BuBBLe GooSe |
|
||
The Original MilfHunter
Registered Member #163
Joined: Mon Mar 06 2006, 02:24PMPosts: 1592 |
Or we can just ban Doak (like many have requested) and the problem will be solved. Doak has played 6 times since Aug 20th and has killed 252 hosties in that time. (Works out to an avg of 42 hostie kills a day.) -[link]- If you want to go through with a plugin style enforcement, it should be loose enough not to punish those players who occasionally clip hosties. It should focus on getting rid of blatant and intentional Douchebags. Something like 12 hostie kills per hour (or 1/2 hour) and resulting in a 24 hour ban essentially only catches people like Doak. Edited Thu Aug 30 2007, 01:19AM |
||
| Back to top |
|
||
| alcosatz |
|
||
FT Classic Op
Registered Member #39
Joined: Fri Dec 02 2005, 10:30PMPosts: 1545 |
Or... we can do both! I perma-banned Doak earlier this week, AND I've written a plugin to manage frequent hostage killing. The algorithm basically works like this: If you kill a hostage you accrue a token associated with your Steam ID. These tokens dissipate over time (CVAR determined, current setting is one token removed for every two rounds played [being spec doesn't count]). If the number of tokens associated with your name exceed a CVAR-settable threshold (current set to 10) then you get banned for 60 minutes. Your tokens are tracked across sessions, so disconnecting and reconnecting does NOT reset it to zero. Also, killing all four hostages will result in a kick and your tokens are NOT reset which means reconnecting and continuing to kill hostages will still push you closer to the ban threshold. There is a CVAR setting that will determine whether hostage kills are counter for CT's or not. Excessive CT hostage killing is rare so I am partial to only counting T hostage kills. There are some improvements that can be made to this logic but I believe it accommodates most reasonable circumstances where asshattery is not involved. I also understand that T hostage killing is not an everyday nuisance, but automatically policing it seems like a good idea. What do you think? Does this sound legit? I've tested it over the past few days and it seems to work well but the possibility of it going haywire and not behaving as intended is a risk. I want to put it on tomorrow evening and, if I do, I will be sure to be in game or reachable via xfire to handle possible issues. Also, a side note: this same type of logic can be applied to team killing rather easily. Mani etc. tracks teamkilling over sessions, but counters are reset on disconnection. Something similar to this plugin (with thresholds and dissipation rates tweaked, of course) would handle players that frequently TK, reconnect under a different name, TK, rinse, repeat... Feedback is welcome, thanks. |
||
| Back to top |
|
||
Powered by e107 Forum System
|
|