Loading...
  OR  Zero-K Name:    Password:   
Title: Tigger_99's Battle
Host: USrankTigger_99
Game version: Zero-K v1.7.3.10
Engine version: 104.0.1-1156-gb72a9cc
Started: 4 years ago
Duration: 24 minutes
Players: 4
Bots: True
Mission: False
Watch Replay Now
Manual download

Team 2

AI: Legacy (1) <CAI>
Spectators

Show winners



Preview
Filter:    Player:  
sort
4 years ago
So this was streamed on Twitch. The server fell behind and never catches up at the 90% mark in the replay, ruining the match (and a streamer's opinion of Zero-K). If you look at https://www.twitch.tv/videos/411669240 at the 45:40 mark you can see some weird shenanigans happening with caretaker build orders and the resulting fallout for the players.
Might be a good candidate for profiling as players were getting Lua OOM errors and Desync. I couldn't duplicate the high memory usage with my limited knowledge of the widget profiler.
+0 / -0

4 years ago
the caretakers were finishing construction of a queued caretaker. The game at that point was lagging heavily so it probably only looked like it took a long time.
Matches with modded income multipliers get to super ultra lategame where zk is bound to lag, but its especially bad with AI as they spam orders a lot everywhere.
+0 / -0
Was there anything that these players could have done to make the game playable again instead of a case of force-resign and 'ETA: Unknown'? Like slowing down the game speed, if they knew it was possible?
+0 / -0

4 years ago
Slowing down the gamespeed (- and + to control this) does help but its hardly a fix. You might have cheats enabled and delete things that way but essentially really high resources + big map + AI leads to a lot of lag. Not letting AI grab the whole map would help a bit. The first map you chose (icy run) wouldnt have been as bad.
If you want to fight together against an onslaught you could try playing against "chickens" AI, there are maps made for this purpose but you don't have to use those.
+0 / -0