Thoughts?
Changing "S" hotkey to Hold position
Forum Index > StarCraft 2 Strategy |
kccc
Canada32 Posts
Thoughts? | ||
CatNzHat
United States1599 Posts
| ||
kccc
Canada32 Posts
| ||
CompanionQue
United States59 Posts
| ||
RM_12
201 Posts
| ||
zhurai
United States5660 Posts
On June 07 2011 13:35 RM_12 wrote: Why wouldn't you change all your hotkeys to comfortable positions? For example i have control groups 7-10 on [T, G, V, C] and all spells on [Q, W, E] regardless of unit, with the most used being on the easiest to spam for me hotkey. You should be able to design comfortable setup of hotkeys with any race, there really isn't that much to bind and you can use keys like space, alt, tilda, capslock. patrol to like, (For me), D is pretty useful too | ||
Reason.SC2
Canada1047 Posts
It took a little while to get used to but its much much easier to micro like this imo | ||
GhostFall
United States830 Posts
after you unit reaches its destination, it'll naturally go into stop state. stutterstep works identically with stop and hold. So again what situation would you ever need to press the stop button. | ||
Chocolate
United States2350 Posts
On June 07 2011 14:00 GhostFall wrote: what situation would you ever hit stop over hold command??? after you unit reaches its destination, it'll naturally go into stop state. stutterstep works identically with stop and hold. So again what situation would you ever need to press the stop button. If you have a non attack unit in an area where it could be attacked then you want to tell it to stop (scouting ovies, workers, warprisms, etc.). This way when it is attacked it doesn't just stay there and instead will move a little bit before you can pay attention to it again (if a warp prism is on a terran's third you want to get it out of there as soon as possible before marines come). Edit: but I still think it would be better to remap hold to S even thought it is a tad counter intuitive | ||
Soluhwin
United States1287 Posts
On June 07 2011 11:59 kccc wrote: I was wondering if any pro's or anyone have done this yet but changed there "S" hotkey which is defualted to stop to Hold position instead for the obvious reasons of being closer to your hand. It just seems like a logical thing to do because you never really use your Stop command anyways. Thoughts? First of all: http://www.teamliquid.net/forum/viewmessage.php?topic_id=187808 hate to be the police here, but there is a sticky thread where this belongs. Second: stop is used for proper studder step micro as it is less actions than a+click, and H isn't a hard reach. | ||
GhostFall
United States830 Posts
On June 07 2011 14:03 Chocolate wrote: If you have a non attack unit in an area where it could be attacked then you want to tell it to stop (scouting ovies, workers, warprisms, etc.). This way when it is attacked it doesn't just stay there and instead will move a little bit before you can pay attention to it again (if a warp prism is on a terran's third you want to get it out of there as soon as possible before marines come). Edit: but I still think it would be better to remap hold to S even thought it is a tad counter intuitive But why would you ever press the stop button? When you right click to move the scouting ovy, worker, or warpprism to its desire location, it'll automatically enter the stop state. In fact pressing S to stop here would be a wasted action. And again, stutter step micro works identically with hold position as with stop. | ||
Soluhwin
United States1287 Posts
On June 07 2011 14:25 GhostFall wrote: But why would you ever press the stop button? When you right click to move the scouting ovy, worker, or warpprism to its desire location, it'll automatically enter the stop state. In fact pressing S to stop here would be a wasted action. And again, stutter step micro works identically with hold position as with stop. Stop works better with melee units, because units will still aggro to things out of range but still in vision with stop rather than hold position. I guess as a zerg stop is just more useful for studder step simply because of less range, but I can see that being different for other races. | ||
Havefa1th
United States245 Posts
On June 07 2011 14:25 GhostFall wrote: But why would you ever press the stop button? When you right click to move the scouting ovy, worker, or warpprism to its desire location, it'll automatically enter the stop state. In fact pressing S to stop here would be a wasted action. And again, stutter step micro works identically with hold position as with stop. Anti hellion micro: select all works, hit STOP, hold F1 and spam click around your base. Doesn't work with hold position. Stop is more versatile than Hold Position because you still have mobility with Stop. For example, 2 roaches versus 1 zealot. You want one roach kiting the zealot while the other stands still and shoots it. Having that standing roach on hold position can lose potential dps in case you micro out of it's range... if it's on stop command it'll move to the zealot. Little things like that. The point of Hold Position is the "STAY FUCKING THERE" button. Generally I use stop for everything unless I'm making a wall of roaches or something, idk. I can find more uses for stop than hold position, but that's just me personally. | ||
GhostFall
United States830 Posts
Anti hellion micro: select all works, hit STOP, hold F1 and spam click around your base. Doesn't work with hold position. ok thats a really good one. In your other example again, why would you waste time pressing s. Both your roaches will already be in the stop mode and attacking the zealot automatically without you having to press stop. You would issue a command to the kiting roach, and you wouldnt have to do anything with the other roach. If you were going to attack the zealot, you would use a move or right click the unit. If a zealot approaches the 2 roaches and they're standing idle, they'll automatically already be in the stop state and attack him normally. Selecting the roach and pressing S is wasting your apm. | ||
tuestresfat
2555 Posts
| ||
W2
United States1177 Posts
On June 07 2011 14:25 GhostFall wrote: But why would you ever press the stop button? When you right click to move the scouting ovy, worker, or warpprism to its desire location, it'll automatically enter the stop state. In fact pressing S to stop here would be a wasted action. And again, stutter step micro works identically with hold position as with stop. Only time I ever use stop is when I accidentally target my own units with my photon cannon and I want it to stop ![]() | ||
TzTz
Germany511 Posts
![]() | ||
manicshock
Canada741 Posts
| ||
GhostFall
United States830 Posts
On June 07 2011 15:51 W2 wrote: Only time I ever use stop is when I accidentally target my own units with my photon cannon and I want it to stop ![]() But hold position would do the same thing ![]() | ||
Jawa~
United States291 Posts
If you get use to this it could be good for you personally, but it is not a "this is simply better" type of change. | ||
alokin
Canada269 Posts
| ||
| ||