Input is handled by checking bitflags on PlayerVars.scannedButtonsDirect
if bit.band( PlayerVars.scannedButtonsDirect, PlayerPad.EVADE ) == PlayerPad.EVADE then
Bitflags for PlayerPad
ESCAPE=23,--tex Not in PlayerPad, own name
dash,hold,fire,subject and cqc aren't listed in exe for whatever reason but are used at different points in script. I worked through it all manually anyway back when, both printing out the value of the flags and testing flags that would fall in the gaps.
The numbers on the list are the pow values, so do 2^flag index (except for ALL obviously) if for whatever reason you want to use a direct value, though not much use since they mostly seem accounted for.
ESCAPE (my naming) is a bit odd, figured it out manually from the next logical value/outputting scannedbuttons, but there's no actual matching use of it I could see in the scripts, it's not strictly the Pause binding since it's still set on press even if Pause is rebound.
2^24 is set on both quick dive and RS click, which has so much bound to it that I can't really figure out what it's supposed to signify.
Testing 2^25 to 2^32(assuming uint) didn't come up with anything further, though it can't remember how exhaustively I tested those (it's been a while)
You'll see a bunch of the flags use the same values, which means there's no way to differentiate on those when pressed.
The naming of the functions band/bor/bxor and the rest in the exe suggest fox engine is using an implementation of bitops http://bitop.luajit.org
STICK_L STICK_R TRIGGER_L TRIGGER_R TRIGGER_ACCEL TRIGGER_BREAK are used with other functions/variables/not used with scannedButtons