Loading...
  OR  Zero-K Name:    Password:   
Title: COOP vs AI (chickens or CAI): All welcome!
Host: CZrankIodine
Game version: Zero-K v1.3.12.1
Engine version: 100.0
Battle ID: 397252
Started: 10 years ago
Duration: 42 minutes
Players: 2
Bots: True
Mission: False
Rating: None
Watch Replay Now
Manual download

Team 1 Won!
XP gained: 50
USrankCaptNutbar
UAranklamer
Spectators
CZrankIodine




Preview
Filter:    Player:  
sort
Nice back & forth battle.

Yet striderhub's bug drives me crazy: if strider was damaged and finished then striderhub will continue to track damaged unit instead of building new one despite having such order (south-east corner, ~24th minute)

Reported: https://github.com/ZeroK-RTS/Zero-K/issues/1218
+0 / -0
10 years ago
i think thats normal, all builders will repair stuff they just built.
+0 / -0

10 years ago
I was confused by hub's build order indication. It was probably old order and striderhub never went idle even when dante left its build-radius.
+0 / -0

10 years ago
Actually factories have an option of whether to repair the unit being built before starting the next unit, but since strider hubs are nonstandard I don't know if that option applies to them. Either way it doesn't drop its repair order even if the strider moves out of its build range, which is difficult for an AI to recover from. (at least it requires a bunch of extra crap to track the unit so that unitFinished can be used to signal the next build job)

Also, I think I've seen strider hubs continue repairing the old strider even when there was a visible order for another strider, although that's difficult to confirm.
+1 / -0

10 years ago
AI got nab team.
+0 / -0