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

Post edit history

Selection Rank/Hierarchy Feedback

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/31/2017 5:47:18 PMCHrankivand before revert after revert
Before After
1 I have used a homegrown widget called "accidental commands blocker" for at least couple of years and it provides similar functions, yet slightly different function. 1 I have used a homegrown widget called "accidental commands blocker" for at least couple of years and it provides similar functions, yet slightly different.
2 \n 2 \n
3 The issue I was trying to deal with with this widget was that in the heat of combat I often needed all my combat units to make a final push or something similar, so I dragged a selection rectangle over the group of units present on my screen, pressed Ctrl-Z or Ctrl-X and went for the push. More often than I'd like I was accidentally selecting a cons along with the combat units, therefore after I Ctrl-X/Z-ed the selected units all my build orders for the nearby or even all conses got cancelled. It was taking quite an amount of APM to restore the build orders and I was often late to notice conses were part of the combat group. 3 The issue I was trying to deal with with this widget was that in the heat of combat I often needed all my combat units to make a final push or something similar, so I dragged a selection rectangle over the group of units present on my screen, pressed Ctrl-Z or Ctrl-X and went for the push. More often than I'd like I was accidentally selecting a cons along with the combat units, therefore after I Ctrl-X/Z-ed the selected units all my build orders for the nearby or even all conses got cancelled. It was taking quite an amount of APM to restore the build orders and I was often late to notice conses were part of the combat group.
4 \n 4 \n
5 So I made a widget. Basically it tracks if Ctrl-X/Z was pressed recently enough (2 seconds, configurable) and if group was mixed (meaning combat + cons units) and order was to move, fight, attack or stop, then I blocked such order and displayed a huge text warning. 5 So I made a widget. Basically it tracks if Ctrl-X/Z was pressed recently enough (2 seconds, configurable) and if group was mixed (meaning combat + cons units) and order was to move, fight, attack or stop, then I blocked such order and displayed a huge text warning.
6 \n 6 \n
7 Back to the topic, I found the selection rank widget solves similar problem, but in a different way. And I personally found it useful. Having that said it's probably worth placing a button somewhere in UI to disable/enable it globally. 7 Back to the topic, I found the selection rank widget solves similar problem, but in a different way. And I personally found it useful. Having that said it's probably worth placing a button somewhere in UI to disable/enable it globally.