Open GoogleCodeExporter opened 9 years ago
The need for this was most obvious when the reddit group tried to organize a
bitmatch tournament.
Other controls might include...
Being able to make persistent Admin Announcements
Being able to suspend action until teams are set
Being able to prevent player-initiated team changes entirely
Being able to set a countdown timer for when "official" play will resume
...although I'm not sure all of these features fit into a single umbrella BBB
gameplay mode or server setting.
Original comment by youat...@gmail.com
on 1 Nov 2011 at 1:53
Pushing off to 016a, though some of these items could be implemented sooner,
and some are covered by other cases.
Original comment by watusim...@bitfighter.org
on 9 Dec 2011 at 11:28
Needs review and decision on what to do for 019, what to defer to 020, and what
to delete altogether.
Original comment by watusim...@bitfighter.org
on 7 Nov 2012 at 9:20
Offical level vs intermission level: Make this a "tournament server" option,
which could be toggled in the hostgame menu.
Being able to make persistent Admin Announcements: Make this always on using
/announce (done already?)
Being able to suspend action until teams are set: Certain levels this would be
nice on. perhaps a /manualteams command, or something specifiable in the level
editor per level?
Being able to prevent player-initiated team changes entirely: A server option
in the hostgame menu for this would be great.
Being able to set a countdown timer for when "official" play will resume: This
won't be used outside of tournaments, and I'm not sure its necessary if we
distinguish between intermission maps and official ones.
Original comment by bobdaduc...@gmail.com
on 21 Feb 2013 at 9:33
From what I gather, we've got most of this already in some form. I think we've
decided to totally nix suspending games, which seems fine to me because there's
a simpler system we could use.
Basically, I think if we add a /intermission command then this is solved. I
imagine /intermission as simply displaying an intermission message and time
remaining in intermission, then restarting the current level (with the same
teams) once the timer is out.
You can simply disable team changing in the INI, which will fix the teams. Then
we have /announce for announcements (if it isn't permanent then we should make
it permanent in all cases, to be cleared by passing an empty string).
Original comment by bkcon...@gmail.com
on 28 Jun 2013 at 4:02
There is also a /resetscore command, and don't forget /shuffle!
Original comment by buckyballreaction
on 28 Jun 2013 at 4:49
Maybe an intermission is better handled by loading a level and letting people
play, but with an intermission tag on the screen somewhere. The intermission
time would be controlled via normal game-length controls, and it would give
folks something to do while they were waiting.
Original comment by watusim...@bitfighter.org
on 1 Jul 2013 at 9:43
Original comment by bkcon...@gmail.com
on 28 Jul 2013 at 3:28
Original comment by bkcon...@gmail.com
on 1 Aug 2013 at 6:02
Original comment by bkcon...@gmail.com
on 1 Aug 2013 at 6:05
actully i could see these being used outside of tournaments I know i would
perhaps make it official?
perhaps a /suspend and a /resume commands combined with a /lockteams
/unlockteams command.
Original comment by Cory.Pou...@gmail.com
on 17 Dec 2013 at 11:46
Original issue reported on code.google.com by
watusim...@bitfighter.org
on 5 Jul 2011 at 1:16