Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Improvement for unpathable construction behavior

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
5/1/2020 5:49:58 AMUSrankLegomenon before revert after revert
Before After
1 https://zero-k. info/Battles/Detail/883840 is an artificial demonstration of building radar/wind on the starting hills at around maximum constructor range. Interestingly the third constructor did eventually go idle after around 30 seconds on a clearly impossible build, but the first two never proceeded to move on. 1 https://zero-k. info/Battles/Detail/883840 is an artificial demonstration of building radar/wind on the starting hills at around maximum constructor range. Interestingly the third constructor did eventually go idle after around 30 seconds on a clearly impossible build which I didn't experience before, but the first two never moved on.
2 \n 2 \n
3 https://zero-k. info/Battles/Detail/883843 is another demonstration on water building radar at the edge of the constructor reach, not super interesting though the first constructor remained stuck in place, whereas the second constructor kept trying to move closer to its target. 3 https://zero-k. info/Battles/Detail/883843 is another demonstration on water building radar at the edge of the constructor reach, not super interesting though the first constructor remained stuck in place, whereas the second constructor kept trying to move closer to its target ( not relevant but amusing) .
4 \n 4 \n
5 https://zero-k.info/Battles/Detail/883144 is a real game that mimics the Otago demo. I badly misclicked with my second constructor at 1:10 and put up a radar too far up the hill. This constructor didn't get unstuck for the 80 seconds or so it took me to notice my mistake. (I had another similar constructor incident later on, again this is user error, I'd just appreciate any simple UI tweaks to make it easier to avoid accidentally idling constructors.) 5 https://zero-k.info/Battles/Detail/883144 is a real game that mimics the Otago demo. I badly misclicked with my second constructor at 1:10 and put up a radar too far up the hill. This constructor didn't get unstuck for the 80 seconds or so it took me to notice my mistake. (I had another similar constructor incident later on, again this is user error, I'd just appreciate any simple UI tweaks to make it easier to avoid accidentally idling constructors.)