| 1 |
A spectator has the same game state save/restore complexity issue as the server would.
|
1 |
A spectator has the same game state save/restore complexity issue as the server would.
|
| 2 |
\n
|
2 |
\n
|
| 3 |
It
wouldn't
be
the
worst
idea
to
just
have
a
player
or
two
who
are
on
the
team,
but
don't
get
any
units.
A
full
spectator
would
have
gained
insight
into
the
secrets
of
the
opposing
team,
which
seems
problematic.
Sometimes
a
team
could
benefit
from
an
extra
pair
of
eyes.
|
3 |
It
wouldn't
be
the
worst
idea
to
just
have
a
player
or
two
who
are
on
the
team,
but
don't
get
any
units
(
but
could
take
over)
.
A
full
spectator
would
have
gained
insight
into
the
secrets
of
the
opposing
team,
which
seems
problematic.
Sometimes
a
team
could
benefit
from
an
extra
pair
of
eyes.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
Actually now that I think about it, is the player limit set at 32 because of the expected number of units that would be built by that many players, or some other limitation? If I can't fit into an over-full lobsterpot I would accept a 2nd-class-player role of some sort, kind of hands-on spectating.
|
5 |
Actually now that I think about it, is the player limit set at 32 because of the expected number of units that would be built by that many players, or some other limitation? If I can't fit into an over-full lobsterpot I would accept a 2nd-class-player role of some sort, kind of hands-on spectating.
|
loading mechanism of rejoining battle