A 1 minute timeout , could, i repeat, could be useful. But its not really going to deter anyone, just going to make them wait. an i never mentioned anything bad about that.BackTrak wrote:QUOTE (BackTrak @ Jan 17 2008, 07:44 PM) I don't know about that Finger, it seems that it would get people to quit hanging around on NOAT for a game to start so that they can quickly stack a side. The one minute timeout that Baker suggested would be fine if the user is displayed a timer until they can join. (Some user feedback would be required). This would be much better than just sitting flashing, waiting for the comm to accept. I haven't kept logs, but I'm sure I'm waiting longer than 60 seconds to join on some launched games.
If it's selectable as a game mode, I think it's an interesting idea.
Baker, thanks for the info, very clear.
My issue AND THE ONLY THING I MENTIONED, was with the idea of not allowing someone to play on a team unless there was another person wanting to join the other team. the 'strict mode' "IDEA"
Baker posed an idea he was having and "I" think its a bad one, now baker, my not liking your idea doesn't mean i don't like you or your ideas, just that ONE.
Out of everything ive read so far, i didn't like one thing that looks like might have been an afterthought.
picking one game randomly to 'prove' your point doesn't cut it. or is every game the same. My point on this is later on in the game, when there arent always going to be 2 ppl wanting to join. What about if a team drops a person, how will strict mode handle that( see end of my post)
Heres an idea, only allow comms to allow players in the order that they try to join, or instead of a 1 minutes timeout, make it random, say between 10 and 45 seconds, including your idea (strict mode) all 3 have flaws.
end of post
Or did i miss the point of strict mode? ( not sarcastic)
is strict mode only going to be implemented for the first 1 minute? that might work better...









