From: SourceForge.net <no...@so...> - 2003-03-21 17:22:03
|
Patches item #704674, was opened at 2003-03-16 23:00 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=303248&aid=704674&group_id=3248 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Lars Luthman (larsl) Assigned to: Nobody/Anonymous (nobody) Summary: CTF cheat prevention Initial Comment: On some CTF servers some players are cheating when they are alone on a team by signing off and joining again every time someone else grabs their flag. This resets the team flag, and when the join again it is back at their base. This patch adds a new command line option to bzfs: -tftimeout <seconds>. This makes the server wait for the given number of seconds after the last player in a team signs off before the team flag is reset. By giving a value of 30-60 seconds (depending on the world) this kind of cheating would be prevented - the tank that is carrying the flag will have enough time to capture it. When the flag is captured it will disappear, even if the time isn't up yet. If the -tftimeout option isn't used, or if it's set to 0, the team flags will be reset immediately when the last player in a team signs off just as they will without the patch. I'd like to see this in CVS, but I'm not sure what the policy is regarding new features like this. What do you think? Should I commit it? ---------------------------------------------------------------------- >Comment By: Lars Luthman (larsl) Date: 2003-03-21 18:34 Message: Logged In: YES user_id=60497 New version - this patch doesn't start the timeout when the last player leaves, but when the team flag is dropped and no players of that team are playing. If someone grabs the flag before the time is up it won't disappear until next time it is dropped and the timer is started again. It will also disappear when it's captured. The default value for -tftimeout is changed to 30 seconds. ---------------------------------------------------------------------- Comment By: Lars Luthman (larsl) Date: 2003-03-17 17:30 Message: Logged In: YES user_id=60497 Thank you for the feedback. 1: Not using a time limit when someone is carrying the flag is a good idea - people would probably be annoyed if the team flag they just had found disappeared while they were carrying it (I know I would). I'm not sure that resetting the flag as soon as someone drops it is good, though. On some maps it's very hard to get the flag from the enemy back to the home base in a single run - you often get killed and have a teammate take over, several times. How about starting a timer as soon as someone drops the flag, and then zap the flag if no one has touched it when the time is up? 2: Yes, it's probably better to turn this feature on by default, instead of having to use a command line option to turn it on. I don't mind command line options, though, as long as they have sensible default values - the more flexibility the better. And some people might want to be able to turn it off with '-tftimeout 0'. What do you think? ---------------------------------------------------------------------- Comment By: Isak Styf (istyf) Date: 2003-03-17 11:45 Message: Logged In: YES user_id=232617 Hi. I think this sounds like a nice feature, but i would like to propose a few changes. 1: Dont use a timed limit from when the last player signed out. Instead check whenever a team flag is dropped or captured if there are any players left on that team. If there aren't, make the flag dissappear. 2: This is a good feature. If players leave their team even though their team's flag is at large, they should be penalised. Therefore i think this should always be in, and not toggled by yet another startup argument. The args are starting to get very very many by now, and i dont think that adding a startup flag for each and every feature is a good way to go. Ideally there should be an in game menu option for every flag, and implementing that is getting more and more of a pain. =) Just my thoughts. /// Isak Styf ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=303248&aid=704674&group_id=3248 |