| 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 | ||
| alcosatz |
|
||
FT Classic Op
Registered Member #39
Joined: Fri Dec 02 2005, 10:30PMPosts: 1545 |
As mentioned here: -[link]- "The Negotiator" (most hostages killed) award on FTC's HLstatsX site for yesterday, Sunday August 26, went to "Dr. Doak (Double Agent)" with 23 hostages killed. The day after Emerican mentioned a hostage killing problem with Dr. Doak I recall seeing an award of 90 hostages killed in one day by the same person. My thoughts have always been that intentionally eliminating hostages to turn a round into deathmatch is not legit. IMO, the only reason for CT's to kill hosties is because CT's have already rescued at least one hostage or they are in the process of doing so. T's killing hosties seems contrary to the premise of a hostage rescue map. My questions to all of you: should intentional hostie killing by T's be punished, and if so, how is the determination reached that T hostie killing warrants punishment? If this behavior should be curtailed do we enforce it as admins and let "anything go" when admins are not around, or do we automate the process by enforcing it with a script/plugin? Writing a script or adapting an existing one such as this: -[link]- ...seems like a reasonably easy way to prevent this. I can handle writing/adapting the plugin. Setting operating parameters such as: A player, playing as a T, killing X amount of hostages per session (or per hour, day, etc) results in a 30 minutes ban. This would be similar to the TK protection ban that has been active for literally years on FTC. I'm open to suggestions and further discussion if many of think this is the wrong approach. Please let me know what you think. Yes, I am aware that Omni likes to shoot the asian hostage. This may cramp his style a little! 
|
||
| Back to top |
|
||
| Jesus[tzahal] |
|
||
![Jesus[tzahal]](/media/avatar/100x0/upload/mango_kiwi.1172003384.jpg)
Registered Member #530
Joined: Wed Jan 03 2007, 10:56PMPosts: 807 |
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
|
||
| Back to top |
|
||
| jigg4joe |
|
||
Registered Member #326
Joined: Wed Jul 05 2006, 04:15AMPosts: 635 |
i warn doak every time he joins. he kills all the hosties anyway so i end up kicking him. doesn't come back for a bit after that. personally, i vote for a ban. as a general discussion on some sort of hostie killing threshold, i think it may be difficult to script if you are going to account for special circumstances like snowman rush, asian hostie killing, etc. i say leave it as a judgment call to the admins that are in-game and follow the warn, kick, ban procedure with abusing players. then have a simple script that only a serial hostie killer would trigger, like 10 hostie kills in 5 rounds (or 6 in 3 as jesus suggested). that way, if no admins are on, it would get rid of people that are blatantly and intentionally killing hosties. |
||
| Back to top |
|
||
| alcosatz |
|
||
|
FT Classic Op
Registered Member #39
Joined: Fri Dec 02 2005, 10:30PM Posts: 1545 |
Thanks for the post, jigg. Just to clarify (because I realized I completely left this out in my initial post) my concern is whether something more than mp_hostagepenalty is needed, or anything at all. Sorry I left that out of the my first post. I don't think the scripting will be much more complex than what I've already done for the LimitBuy plugin. The challenge of programming it isn't really a problem, but I understand the complexities that Steel suggests could take some time to work out. However, the major advantage of using a counter of individual T hostie kills that expires each kill (but tracks across reconnects) after a certain time means that accidents are handled but consistent T hostie killing is tracked and punished. |
||
| Back to top |
|
||
| [FT] CaTPooP |
|
||
nightrider![[FT] CaTPooP](/media/avatar/100x0/upload/sketch2s.1145985608.jpg)
Registered Member #122
Joined: Sat Jan 07 2006, 09:16AMPosts: 202 |
yeah im real sick of this guy. not only does he kill the hosties every round, hes just an all around ass. if someone is hiding in the plants, he'll walk up and shoot the pot. he was killing hostages tonight and i warned him on several occasions. a 30 min ban sounds about right for intentional hostage kills. limiting it to terrorists would eliminate many obvious problems, like ct's killing a hostage after they have rescued one to win the round, etc. Edited Tue Aug 28 2007, 01:08AM |
||
| Back to top |
|
||
| Omni |
|
||
terrible one
Registered Member #33
Joined: Tue Nov 29 2005, 11:50PMPosts: 1292 |
[FT wrote ... CaT_PooP] limiting it to terrorists would eliminate many obvious problems, like ct's killing a hostage after they have rescued one to win the round, etc. Ts, can kill Hostages with a legitimate reason. If the Ts is chasing after the CT rescuing the hostages then it would be a good idea to kill the hostages to prevent the CT from winning; i mean after all, they are Ts, not nice ppl when it boils down to a situation like that This has happened to me be4 and it is something i feel needs to be kept in mind. Another point, is that if the ban is set to low then CTs will use hosties not only as "body" shields but as "ban" shields. (do i need a further explanation here?) Lastly, for the most part regs don HK (Hostage Kill). It will rape your rank b/c they lose points for killing hosties. |
||
| Back to top |
|
||
| Zero |
|
||
I want to fuck your hand.
Registered Member #571
Joined: Thu Feb 15 2007, 09:59PMPosts: 2809 |
I agree with Omni, we are terrorists, and it should only happen if you are chasing them #1. or if you accidentally are trying to kill a CT and you clip the hosties (how I rack up the HKs) #2 plus, we always have the joke of killing the Azn hostie, lol |
||
| Back to top |
|
||
| A Drunk |
|
||
Registered Member #437
Joined: Sat Sep 23 2006, 02:18AMPosts: 1224 |
I say if you kill all 4 of them, then they should be punished. If you are just going to shoot the asian hostie (like most of us like to do), then it is alright and they should just let that go. | ||
| Back to top |
|
||
| Pockyninja |
|
||
Ruler of all that is pocky
Registered Member #28
Joined: Mon Nov 28 2005, 11:17PMPosts: 704 |
[quote] As mentioned here: -[link]- "The Negotiator" (most hostages killed) award on FTC's HLstatsX site for yesterday, Sunday August 26, went to "Dr. Doak (Double Agent)" with 23 hostages killed. The day after Emerican mentioned a hostage killing problem with Dr. Doak I recall seeing an award of 90 hostages killed in one day by the same person. My thoughts have always been that intentionally eliminating hostages to turn a round into deathmatch is not legit. IMO, the only reason for CT's to kill hosties is because CT's have already rescued at least one hostage or they are in the process of doing so. T's killing hosties seems contrary to the premise of a hostage rescue map. My questions to all of you: should intentional hostie killing by T's be punished, and if so, how is the determination reached that T hostie killing warrants punishment? If this behavior should be curtailed do we enforce it as admins and let "anything go" when admins are not around, or do we automate the process by enforcing it with a script/plugin? Writing a script or adapting an existing one such as this: -[link]- ...seems like a reasonably easy way to prevent this. I can handle writing/adapting the plugin. Setting operating parameters such as: A player, playing as a T, killing X amount of hostages per session (or per hour, day, etc) results in a 30 minutes ban. This would be similar to the TK protection ban that has been active for literally years on FTC. I'm open to suggestions and further discussion if many of think this is the wrong approach. Please let me know what you think. Yes, I am aware that Omni likes to shoot the asian hostage. This may cramp his style a little! [/quote1188266243] Sounds good to me. I don't normally have to much problem with this but recently I played with a dude named jizzbucket and he would sabotages the T team by waiting for the ct to come rescue to hostages and then shoot the ones in the projector (jizz was on T not ct) |
||
| Back to top |
|
||
| Wildcard23 |
|
||
Registered Member #514
Joined: Wed Dec 20 2006, 06:33AMPosts: 1067 |
I'm also in agreement with Omni. I have been on for a few hours at a time on FTC and ended up with a 30 minute ban because I will clip a hostage or throw a nade while a CT has hosties following them. Also, if you are in projector, a lot of T's to include myself take an angle towards paper room and end up clipping hosties when you strafe when someone starts firing at you. I agree that we need something else in place but I'm not sure of a great solution at this point in time. |
||
| Back to top |
|
||
Powered by e107 Forum System
|
|