



bPrimaryBinding/bSecondaryBinding - Boolean, if the key is primary/secondary key, can be omitted.Alt - Boolean, modifier key (other modifiers are Control and Shift), can be omitted if not required.- String, mapped key's name, can be alias like MyName (MyName is then used as command).Bindings=(Name="", Command="", Alt=True, bPrimaryBinding=True) In case a key has multiple bindings, the game executes only the last valid entry, so there's no need to edit old bindings. It is absolutely possible to add new lines at the end of the file, but always precede them with correct section name in brackets.Bindings for tactical are in section (lines 201-330 in XCOM EU).Bindings for strategy are in section (lines 18-200 in XCOM EU).General commands may be in both sections, but should be in the section regarding the layer of execution. It is necessary to put the command into correct section of DefaultInput.ini, because some commands work only in specific layer of the game - strategy or tactical. MAC users can find DefaultInput.ini in /XCom-Enemy-Unknown/XCOMData/XComGame/Config. This also include descriptions and other examples of features such as key bind aliasing, chaining, the onrelease modifier, use of variables, toggles, and binding functions. See Patches to identify which patch level you are currently on.įor a list of valid keys and gamepad buttons that can be bound, see UDN Three - Key Binds article. Update: EW patch 3 has fixed the in-game key binding "save bug". Direct DefaultGame.ini editing seem like only workaround for now. They actually added functions for implementing the Hunker Down hotkey (K_Key_Press, K_Key_Release) and it can be assigned in-game, but it gets discarded after you exit the game. However, DefaultGame is still used for some things (such as MobilePlayerInput), so both still need to be checked.ĮW patch 2 has a bug: it doesn't save any in-game key bindings. Update: EW patch 3 has restored the previous DefaultInput functionality. This is an exact duplicate of the bindings found in DefaultInput.ini This is necessary because XComTacticalInput now extends MobilePlayerInput, which loads its configs from DefaultGame.ini.ĭefaultInput is now ignored in favor of DefaultGame for some things (confirmed specifics not yet determined) but is still read for others, so just remember to apply to both file names throughout the rest of the article if you have EW patch 2 or later installed. NOTE: Since Patch 2 for EW, the exact same settings must be applied to the DefaultGame.INI file instead in order to work correctly.
