Loading...
  OR  Zero-K Name:    Password:   
Title: TEAMS: All welcome!
Host: CZrankSpringiee
Game version: Zero-K v1.2.9.9
Engine version: 91.0
Battle ID: 302977
Started: 9 years ago
Duration: 27 minutes
Players: 8
Bots: False
Mission: False
Rating: Casual
Watch Replay Now
Manual download

Team 1 Lost
Chance of victory: 53%
XP gained: 86
RUrank[tre]PAK died in 30 minutes
Skasi died in 30 minutes
RUrankTwinH died in 30 minutes
DErankBlackWinter died in 30 minutes
Team 2 Won!
Chance of victory: 47%
XP gained: 106
FIrank_edrush died in 21 minutes
GBrankPrincey died in 21 minutes
USrankDeeDiebS
FRrank[IDF]rudubu




Preview
Filter:    Player:  
sort
Skasi
R U TROLLING ME! WE WON! AAAAH #GBCONSPIRACY
WHAT IS THIS! SERIOUSLY! DRAMA! LYNCH SOMEONE

fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
QQQ not fair, I played so well (honk)


(yes I am completely serious, there is definitely a bug here)

edit for more information:
For some reason the game decided to drop the winning team's players, I noticed that ingame by seeing the usual "connection lost" icon. Watching the replay shows it has the winner team right ingame, see "Team 1 wins!" in the chat.
Screenshot of replay's "game over" view
+0 / -0
9 years ago
I formally declare that GBC has nothing to do with this. (this time that is...)
+0 / -0
FIrankFFC
9 years ago
Orfelius just testing his new powers here!
+0 / -0

9 years ago
Game has something against you skasi.

It says in screenshot that skasi was cut short.
+0 / -0
quote:
it has the winner team right ingame, see "Team 1 wins!" in the chat.

Are you sure? Doesn't Spring index from 0? That would mean the site obeys Sprung Spring correctly. Spring also had to declare your allyteam dead because you all disconnected so the question is mostly why the disconnects happened. Was there a resign? It seems from your screenie that at least one enemy player ( @[idf]rudubu ) also got disconnected.
+0 / -0
Skasi
9 years ago
Not sure if Spring starts with 0, I assumed the team 1 in the chat was the same team 1 as in the playerlist. Might be wrong though, a simple test could answer this.

There were no other timeouts in the chat missing above in my screenshot, I made sure of that when resizing the chat for the shot.
+0 / -0