Loading...
  OR  Zero-K Name:    Password:   
Title: MatchMaker 3123
Host: Nobody
Game version: Zero-K v1.6.5.1
Engine version: 104.0.1-287-gf7b0fcc
Started: 5 years ago
Duration: 15 minutes
Players: 2
Bots: False
Mission: False
Watch Replay Now
Manual download

Team 1
Chance of victory: 91.6%

USrankStuart98
Team 2
Chance of victory: 8.4%

USrankVLCPlayer
Spectators

Show winners



Preview
Filter:    Player:  
sort
By far the worst unit AI I have EVER seen in Zero-K. This pissed me off.

Ducks not shooting at mexes they're right next to, archers getting hit by ronin rockets that they shouldn't, com letting a factory get killed when it was barely out of range of the offending glaive. What the fuck. I'm mad.
+0 / -0
I couldn't find anything unexpected here:

Duck had no line of sight of mex, that is why it didn't fire: a fern was blocking it with its collision volume. Would it be nice if it tried to move somewhere to attack - certainly. I'm almost certain it would have tried if it was given a direct attack command. Perhaps Maneuver move type prevent this duck to do so, not sure.

"Projectile dodging" is imperfect, but cheap. Units don't actually take into account enemy projectiles, rather just try to move in a pattern that would cause unguided rockets to miss. Sometimes it works, sometimes it doesn't.

As far as factory loss, that glaive kept shooting for like half a minute. You should have reacted yourself. Maybe if you had changed the commander move state to Roam, it would have reacted: worth testing.

Note that I used word "unexpected" in my first paragraph. Both cases with Duck and Commander are obviously not great, to say the least, but it's a behavior implemented by engine and not related to Zero-K Unit AI.
+0 / -0