| 1 |
Since
two
days,
the
server
apparently
no
longer
knows
what
game
version
to
host
(
.
19/.
20/.
22)
.
The
outdated
versions
have
a
bug
where
the
build
menu
crashes
when
removing
a
unit
from
queue,
causing
the
interface
to
break
for
most
players.
Replays
aren't
saved
for
MM
games
and
games
not
using
ZK
1.
5.
4.
19.
Due
to
this,
Elo
isn't
updated
either.
(
+Spring
crashes
every
time
a
game
starts
for
me)
|
1 |
Since
two
days,
the
server
apparently
no
longer
knows
what
game
version
to
host
(
.
19/.
20/.
22)
.
The
outdated
versions
have
a
bug
where
the
build
menu
crashes
when
removing
a
unit
from
queue,
causing
the
interface
to
break
for
most
players.
Replays
aren't
saved
for
MM
games
and
games
not
using
ZK
1.
5.
4.
19.
Due
to
this,
Elo
isn't
updated
either.
(
+Spring
crashes
at
the
start
of
every
game
for
me)
|
| 2 |
\n
|
2 |
\n
|
| 3 |
All of these features are pretty central to the user experience, which is why I'd suggest fixing them asap and notifying users that the server is currently in need of maintenance. Acknowledging the problem would at least give newcomers the hope to come back another day when the game is working again.
|
3 |
All of these features are pretty central to the user experience, which is why I'd suggest fixing them asap and notifying users that the server is currently in need of maintenance. Acknowledging the problem would at least give newcomers the hope to come back another day when the game is working again.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
Now to make this rant and actual meaningful thread:
|
5 |
Now to make this rant and actual meaningful thread:
|
| 6 |
* What are we going to do to avoid such failures in the future?
|
6 |
* What are we going to do to avoid such failures in the future?
|
| 7 |
* If it still happens, how will we respond to it for a quick resolution?
|
7 |
* If it still happens, how will we respond to it for a quick resolution?
|
| 8 |
\n
|
8 |
\n
|
| 9 |
For the former, we should definitely set up a proper testing server. The current test server requires complicated configuration and a Chobby restart to connect to it. You need to be core-admin to set up the proper engine and update the server to the current state. Then you need to clone the zk github and set it up as game because zk:test is not working anymore. No wonder nobody is using the test server. Connecting to the server should be a simple switch in the login screen and automatically use the latest engine and zk version.
|
9 |
For the former, we should definitely set up a proper testing server. The current test server requires complicated configuration and a Chobby restart to connect to it. You need to be core-admin to set up the proper engine and update the server to the current state. Then you need to clone the zk github and set it up as game because zk:test is not working anymore. No wonder nobody is using the test server. Connecting to the server should be a simple switch in the login screen and automatically use the latest engine and zk version.
|
| 10 |
\n
|
10 |
\n
|
| 11 |
For the latter, there has to be a revert button. It would set the server's engine, zk and infra version to what was used before the last roll-out. Of course this would first require a concept of "roll-outs" other than github version tags and the server to be actually able to choose the version of the game that is being used.
|
11 |
For the latter, there has to be a revert button. It would set the server's engine, zk and infra version to what was used before the last roll-out. Of course this would first require a concept of "roll-outs" other than github version tags and the server to be actually able to choose the version of the game that is being used.
|
| 12 |
\n
|
12 |
\n
|
| 13 |
\n
|
13 |
\n
|
Close server for maintenance?