TIMEOUT command for team competitions

[sinewav]

I think there are times when calling a time-out is appropriate. Let's use this thread to discuss it's feasibility and functionality, and also it's pros and cons. (Of course, I'm really talking about Ladle here, but this could be good for all team games.)

First, why I think the idea sucks. Ladle finals already take a long time. As we see in other professional sports, time-outs can really stretch out a game. Also, a time-out kills the momentum of the game (which is why some teams use time-outs of course). My personal philosophy is, you can't stop a lightcycle, you shouldn't be able to stop the game either. Not having time-outs put more pressure on a team to be ready, be creative, and act quickly and decisively.

Now, why I think it's a good idea. This isn't a perfect game. We have technical problems at times, sometimes severe. And we never solved the problem of substitutes and shuffling. A time-out function, if handled appropriately could actually make the game more exciting, more competitive, and maybe even more fair. Maybe. also, each time-out benefit both teams.

How should it work? Perhaps a time-out can stop play for 2 rounds. That should be enough time to work out any problems. The function activates/deactivates between rounds, so if you call a time-out it won't take effect until the current round finishes. It would be nice to have a center_message that shows the time-out for the duration. And how many time outs? How about 1 per team, per match? This seems like a lot, but I don't imagine the function will be used every time, for every match, by both teams (that could potentially double the playing time).

I guess we could try it out on a test server for a few weeks and see if it suits us. Maybe the TIMEOUT function should only work in the case of a technical problem Armagetron can detect.

[syllabear]

I'd say if both team captains agree for a timeout, then it is given (one team calls it, the other agrees). The timeout then occurs until such a time as one team captain suggests the time out should be stopped (and then play resumes the next round/ the next minute if the game is paused).

[INW]

A timeout could simply be this:

Code: Select all

Fullscreen_message 30 30 second timeout for team Blue.

That would work.

[apparition]

This is how I envision a TIMEOUT

• TIMEOUT only used to discuss and resolve server problems*
• Timeout pauses play after the round ends
• Either team captain can call it at anytime**
• Center message appears "Team A called a Timeout - 2 minutes Remaining"
• Team captains only able to speak/shout
• Captains decide exactly what to do within 2 minutes***
• 1 minute warning
• 30 second warning

*A timeout cannot be used for pee breaks, not for organization, not for strategic reasons. The flow of the game relies on its unstoppable nature!

There's no reason for both captains to agree for the timeout; in a way, this would defeat the point. I can't think of any sport/competition that requires teams to agree that it's okay to take a timeout.

In the event that the captains agree the server is unplayable (for either team) both teams move to the backup server immediately, restarting the match that is being played only.

[Word]

there should be a maximum number of time outs so it's not getting exploited.

(yes i know this can be stupid if the server crashes 3 times in a row but then the most rational consequence would be to play in a different server instead)

[INW]

I believe the easiest way to pause a match for a given time is using the fullscreen_message and applying the correct number of seconds. That completely pauses the game and you wont have to worry about resettings the rounds and score.

[sinewav]

Maybe it can work like EXTRA_ROUND_TIME, but placed before all the grid objects are made? Like a 2:00 minute long chat break - with a countdown message. Everything can be sorted out (like invitations/substitutions/shuffling, and discussion about server quality) and there are no extra rounds to sit through, which waste a lot of time and would be confusing to some less observant players.

I also imagine the family of settings as
TIMEOUT_NUMBER positive integer, number of time-outs per match
TIMEOUT_TIME positive number in seconds, length of a time-out

And I know we're all thinking "Ladle", but let's try to imagine this used in other competitions.

[Titanoboa]

My thoughts are that the possible negative effects outweigh the positive effects. In addition I've never seen a huge need for it.

R and Tx kinda simulated a mini time-out this ladle. Stalled a round until whoever had to brb was ready. I guess my point on that is that if both teams agree on it, the commands/settings/code aren't required.

[Phytotron]

Will players be sent to their room or made to sit facing a corner?

[Discosuperstar]

It seems like there are two different time-outs that can be made.

• One more closely mirrors the way it's done in sports where it's used for substitutions and internal team stuff. In this case there would be limitations on X amount per team, Y amount maximum [total] delay, etc. (appa's way)
• On the other hand, for timeouts that are for strictly technical reasons (no team bias) would probably be better suited for complete game pausing until an explicit resume command (no time limits), and the appropriate commands limited only to admin or team voting. (syllabear's way)

Perhaps these need to be discussed independently?

[Lanfear]

I like this idea. Hopefully it gets implemented... somewhere.