Remapping

remappings are defined at the beginning of a script and must be done before the main procedure they cannot be executed during run time command name description remap assigns the value of the controller input to the output unmap disconnects an input from the output report remap remap assigns the value of the input identifier to the output identifier gpc remap ps4 cross > ps4 square; although you define remaps at the beginning of a script, the virtual machine does not execute the remaps until the main second has finished the current iteration this means that any scripting operations on the remapped entries for inputs should be programmed for the original buttons without considering the remapped item 🔴 syntax remap < input identifier > > < output identifier >; ⚪ parameters \<input identifier> any defined variable \<output identifer> index point of the bit to be set with a range of 0 to 15 🔵 returns nothing unmap unmap disconnects an input from the output report this means that although the virtual machine can still see the value of the button/axis on the input report, it will not pass its value onto the console in the output report you can therefore still use an unmapped button to run code or start combos in your gpc script without worrying about its original function being sent to the console unmap ps4 triangle; // unmaps the ps4 triangle identifier; unmap all remaps; // unmaps all controller identifiers which have been remapped; 🔴 syntax unmap \<output identifier>; ⚪ parameters \<output identifier> any defined variable 🔵 returns nothing