Loading...
  OR  Zero-K Name:    Password:   
Title: [A] Free For All
Host: Nobody
Game version: Zero-K v1.10.4.1
Engine version: 105.1.1-841-g099e9d0
Started: 11 days ago
Duration: 21 minutes
Players: 6
Bots: False
Mission: False
Watch Replay Now
Manual download

Team 1
Chance of victory: 33.8%

ILrankChomolungma
NLrankmalric
Team 2
Chance of victory: 12.6%

FRrankSlaab
PHrankethanmarcusg
Team 3
Chance of victory: 53.6%

ROrankizirayd
NZrankmarkivs
Spectators
GBrankSab
INrankTheWarning

Show winners



Preview
Filter:    Player:  
sort
11 days ago
Game chance and elo calculation does not take into account how players will make alliances. We instantly got an alliance against our team, which destroyed us. In fact, the game gave us a 60-65% chance of winning, which is a lie. I don't believe for a second that we can win two fronts at the same time.
+1 / -0
11 days ago
In one of the posts they wrote that the formulas were tested and they calculate the chances of winning well, I think that this is garbage and the formulas cannot accurately assess all states.
+0 / -0
11 days ago
It is also worth noting that an instant union from the first second of the match does not give more than one chance to win. We lost right away, there were no mechanisms to win and it does not depend on our skills. Even a player with 1900 elo who builds shields, his simple attacks are enough to take spots.
+0 / -0
11 days ago
So what balance would you propose? You might like Slaab+Chomolungma instead, but then me and ethanmarcusg would say "we have no chance". I think there are cases in which there is no good "solution".


+0 / -0
quote:
Game chance and elo calculation does not take into account how players will make alliances. We instantly got an alliance against our team, which destroyed us. In fact, the game gave us a 60-65% chance of winning, which is a lie.


The predict function does not take game circumstances into consideration. It only takes WHR into consideration. it is a very poor predictor of game outcomes (outside of 1v1 probably) and should not be relied on in any capacity.
+0 / -0