KeystrokePacket seems to have moved

[StarryWisdom]

KeystrokePacket (valueInt:0x14) seems to have relocated to (valueInt:0x16)
I have slight memory this was the case in 2.6 but do not have the tools to test at the moment
presumably this happened in 2.3/2.4 days given the nearby valueInt renumbering
no idea what valueInt:x14 is currently

[NoseyNick]

Looks like valueInt:0x14 is still used for GM keystrokes, valueInt:0x16 might be used for "other consoles" after 0xf754c8fe:0x11 KeyCaptureToggle? Here's both...

3c1d824c1400000041000000 # payload
3c1d824c16000000410000004100 # payload
3c1d824c1400000042000000 # payload
3c1d824c16000000420000004200 # payload
3c1d824c1400000043000000 # payload
3c1d824c16000000430000004300 # payload

Looks like
valueInt = 0x4c821d3c
subtype = 0x16
int keystroke
short keystroke (WHY?!?)

Researching. My parser currently misinterprets this as an old SetShipSettings, and assumes it should auto-downgrade the protocol version ☹️

[StarryWisdom]

im wondering if one of the keystroke types is raw scancode and one is a conversion to unicode or something like that - I wonder what happens with non ascii symbols