Open GoogleCodeExporter opened 9 years ago
Bots can't participate in the tourneys! So they can't join to game with tourney
rules.
Other possibility to make them always ready. But I prefer them to be off from
tourneys.
Original comment by igorpana...@gmail.com
on 21 Aug 2009 at 10:18
like i already told you via IRC:
[11:24] <moRtem> as soon as countdown starts, /unready should be disabled too
[11:25] <moRtem> out of experience some ppl act lame and repeately /unready when
countdown is almost finished
[11:26] <moRtem> the /pause command should be called /timeout to go conform with
other games
[11:27] <moRtem> and the /timeout should be cancelled by /timein
[11:28] <moRtem> while /timein should be available for the whole team (of the
player
who called /timeout -- otherwise you'll encounter weird situations when the
/timeout-caller leaves the game, or switches to spec etc. -- usually timeouts
are
called when someone has to go etc and someone else jumps in)
[11:42] <moRtem> ah..i forgot to add, that there shouldn't be more than 'n'
timeouts
per team per game
[11:42] <moRtem> usually that value is set to 3
[11:43] <moRtem> and i don't think another /timeout should reset countdown
Original comment by mortijs-...@yahoo.de
on 22 Aug 2009 at 10:21
Two server variables to control the behaviour:
g_allowReady <0/1>
g_allowTimeouts <0/1>
Original comment by igorpana...@gmail.com
on 23 Aug 2009 at 6:44
i would solve it a bit different:
+ g_allowTimeouts should be named g_Timeouts and store the number of timeouts
available per team. So e.g. g_Timeouts 3 would mean, that each team is allowed
to
call 3 timeouts.
+ g_timeout_time should be added. This variable would store the Duration of
each timeout.
+ g_timeout_timeinDelay should be added. It stores the duration between someone
doing
/Timein and the real unpausing of the match, so that players got time to get
ready
again. (also a countdown should be added here of course - the last seconds
unterlined
with some sound).
Original comment by mortijs-...@yahoo.de
on 23 Aug 2009 at 8:10
Suspended until issue 57 isn't done.
Original comment by igorpana...@gmail.com
on 8 Sep 2009 at 6:26
Original issue reported on code.google.com by
igorpana...@gmail.com
on 21 Aug 2009 at 9:40