On August 31 2014 03:10 Arnovic wrote: Is it possible to change the keys for Ctrl + LeftMouseButton for select every same unit on the screen? Having it be MiddleMouseButton would be glorious in my position.
Bind Unit Management//Selection to MiddleMouseButton?
The basic functionality of ctrl (=select unit type) and shift (=add to selection) can not be changed as far as I know. You can only change the mouse button you want to use together with ctrl/shift to select units (like velvex already mentioned).
Rebinding 'Selection' to another mouse button doesn't give you full functionality, because you still have to left-click to select units in the selection screen (lower center of your screen). That part is hard-coded to left-click, just like buttons on menues and in the command card are hard-coded to left-click.
Why can't "unload all" (medivac ability) conflict with stim pack? You can't stim in a medivac,
EDIT: Then again, in some cases the "select builder" or "halt construction" abilities cannot conflict with hotkeys that the building would use after completion. So, it seems SC2 hotkey conflict laws make no sense at times.
@skern49 Unload All and Stimpack are both found on the Bunker, and the abilities are shared with respectively the Medivac and Marine/Marauder
Select Builder and in some cases Halt Construction will be found on the Command Card of a completed structure, because a constructing building has been selected at the same time.
You can't, but if you were to, for example, bind Stim and Unload to the same key by manually editing your hotkey file, it work on every unit, but the bunker. On the Bunker, Stim takes priority, so Unload will be unavailable on the Bunker, unless you bind an alternate to Unload. Also, if you ever reload your hotkey file (makes a change ingame, loads it on a different computer, swaps hotkeys, etc.) Stim and Unload won't be on the same key anymore.
Coming back to SC2 after a long absence, and I'm going to start with TheCore 2.0 PRL (from github). Questions:
Why are cameras and group keys "rotated" by one? And why is there an inversion between the keys for Cam 6/7 and CGs 7/8? Obviously these numbers are arbitrary, but seems like unnecessary cognitive overhead.
Also, are the suggested cameras and CG allocations for Protoss on the Core Master Spreadsheet (P. Overview) up-to-date with respect to Core 2.0?
@skern49 I do not know if it is looked down upon or not. Not many people know about it, so not a lot have had the chance to voice their opinions about it. 1 key = 1 action is still true, so personally I don't see the big deal, but I'm sure some would, since you're not supposed to ignore conflicts like that.
Remapping keys using AutoHotkey and similair programs is tournament legal. Using macros made by AutoHotkey, or any other program is not.
@instinctive The cams are 'rotated' for the suggested base cameras for your main, nat through 5th (possibly up to 7th) are bound to camera 1-7. But it's definitely something to reconsider. The inversion has been caused by how we care about alternating fingers for base cameras. It's not a big deal though, so it's totally something to fix for the next update
@Cybersage For the layout I'm assuming that you're using (PRM 2.0), MSC and everything else on Key/oem8 is meant for the key to the left of shift. I wouldn't be able to know if the file with the information for translating USQwerty to all other languages has an error particularly for your layout. But if you would like to help out clarifying this, it would be a big help if you bound the key left of shift to MSC and saved your hotkey file. Then, opened that hotkey file from the same place that you saved it using a text editor and found "MothershipCore/Nexus=" and what's after "=".
I just re-joined THECORE and I noticed that the set rally point hotkey isn't bound in a reachable spot (TRM: bound to R(standard keyboard layout)), with the previous hotkey profile I was using, when taking my third base as terran I used to rally the ccs that weren't in the air with that command, just right clicking would make you have to reissue the land/move command of the flying CC.
TheCore PRM 2.0 (github) has: Cancel=N; Stop=Y; various=Slash TheCore Master Spreadsheet P.Ability has: Cancel=Slash; Stop=N; various now on other keys Is this a change in the works?
@nQL: In TheCore TRM 2.0 it is planned to bind Rally to "." . I do not know, if 1.0 is still optimized or changed at all, so you might have to take care of it yourself and find an appropriate key for the rally command. Maybe "." is also viable in TRM 1.0
@pixodes: try this folder: Macintosh HD (or whatever your hard drive is called) Users [username] Library Application Support Blizzard Starcraft II Accounts