Loading...
  OR  Zero-K Name:    Password:   
Title: MM 358: 1v1 Wide, Rank Neutron Star
Host: Nobody
Game version: Zero-K v1.13.9.5
Engine version: 2025.04.11
Battle ID: 2288385
Started: 30 hours ago
Duration: 5 minutes
Players: 2
Bots: False
Mission: False
Rating: Competitive
Watch Replay Now
Manual download

Team 1
Chance of victory: 97.9%

DErankSkel
Team 2
Chance of victory: 2.1%

USrankKnightshade
Spectators
DErankexploit
unknownrankmanero

Show winners



Preview
Filter:    Player:  
sort
29 hours ago
1. Allocation: Tank fac probably not a strong choice on a map with this many ramps. Consider Cloaks, shields, or possibly amphs? Additional familiarity with factory not sufficient to offset terrain disadvantage.
2. Allocation: Strike commander inefficient choice and instance of lack of planning. Econ commander for defensive play
3. Strategy: Initial kodachi + rear side cmdr deployment unwise. Most facs can deploy more, cheaper scouting assets faster. Terrain prevents exploitation with kodachi aggression, provides multiple angles for flanking glaives. NOTE: This is factory agnostic, any bot factory could have done this- it's a structural weakness of the opening fac + com + map.
4. Strategy: Deploying second kodachi aggressively was a mistake. Defensive kodachi could have significantly impaired offensive efforts
5. Scouting: Lack of initial radar tower prevents interception/elimination of forward glaive groups.
6. Tactics: Initial kodachi pressure was good, but after the imp died I got greedy. Despite strength in retreating, kodachi has a delay before it can retreat while it turns around.
7?. Strategy: Failure to sweep backline. (This would be redundant by correcting 5.)
8. Allocation: Failure to anticipate escalation. Third kodachi assumed opponent would continue skirmishing with glaives, when in practice a riot transition makes more sense. (I would have escalated to ogres if I had him on the backfoot). That kodachi should have been a blitz.
9. Tactics: Avoid conga lines, avoid leading with damaged units. Loss of kodachi was avoidable.
10. Tactics: Kodachi eats shit to reaver. This is a pattern- I consistently underestimate reaver's range- It's slow, but it's range is considerable as it's designed to punish diving raiders.
11. Strategy: Kodachis should have been deployed as flank guards against runbys once reaver spotted. The above fight was dumb twice- once because it was engaging a hard counter to kodachis, once because that then denies me defensive assets to block the second glaive backstab.
12. Allocation/Activity: Built 2 constructors, basically built a radar tower and a lotus with them and then nothing else. Those could have been building defenses and expanding eco (I had the money).
13. Economy: default W-alt command builds solars. Consider turbines when wind >.5 base.



New mental model: Assume typical odds of minimum 3-4:1 for determining map presence
Analysis: Tanks seem particularly reliant on good map awareness due to limited QRF assets. Forward radar is NOT OPTIONAL.
Analysis: Cloakbots in particular emulate fighting drop terran in SC2- any time opponent is under pressure, assume they will backstab to relieve pressure.
+1 / -0