Loading...
  OR  Zero-K Name:    Password:   
Title: MatchMaker 17
Host: Nobody
Game version: Zero-K v1.5.4.0
Engine version: 103.0.1-747-g2ef5870
Started: 21 days ago
Duration: 3 minutes
Players: 2
Bots: False
Mission: False
Watch Replay Now
Manual download

Team 1

GBrankLlamadeus
Team 2

CHrankAdminDeinFreund
Spectators
USrankFealthas

Show winners



Preview
Filter:    Player:  
sort



CHrankAdminDeinFreund
21 days ago
(edited 21 days ago)

This great "competitive" RTS's lobby just kills your running game to connect to another battle. At least ask before kicking me out of battles.

Bad Meta might be tiring and boring, but the random crashes, disconnects and what happened here is what really discourages me from taking this game seriously.
+2 / -0


CZrankAdminLicho
20 days ago
You mean you queued for PW battle and then joined 1v1? Knowing there is no stepping back from PW?
+0 / -0

DErankkatastrophe
20 days ago
Happened to me as well, and i didn´t know that there is no stepping back.
A warning might be useful.
+0 / -0


CZrankAdminLicho
20 days ago
There could be stepping back in the attack phase.. in that case joining 1v1 could remove you from queue..

But after "attack" when defending side has 10 minutes to respond, I cannot imagine working "step back".
+0 / -0



CHrankAdminDeinFreund
20 days ago
If there's no stepping back you shouldn't be allowed to join MM.

Tbh I didn't expect PW to even happen. Effectively it didn't happen because PW was broken, but it still kicked me out of this game yet considered it "elo worthy". That's like forcing me to throw games.
+1 / -0



GBrank[GBC]1v0ry_k1ng
20 days ago
There really should be no possible circumstance where a player is auto kicked from a game to join another. If queued for PW, disallow join other games?
+1 / -0