Ensiform
Ensiform
SHIFT requirement was removed. ~~Which keyboard layout are you using?~~ We haven't fully gotten around to the best way to solve universal console key support. And the situation is even...
@Caelish How about with a freshly compiled version with cl_consoleUseScanCode now implemented and default to 1? Should be fixed with https://github.com/JACoders/OpenJK/commit/0a65fd6a7237f66369e2b3a339b633e0e5f42be3
I have a feeling the last Windows build was before the fix though. Indeed. Was fixed in September, last build was August 22 then Stoiss' windows box was shut down....
If the original client had a key that wasn't to the left of the 1 then it's going to be even more corner case because that is how they handled...
The key you identify as ***1*** is what is considered to be the console key in baseJKA (with Shift) and now in OpenJK with `cl_consoleUseScanCode 1` regardless of the language....
Thought NPC_ChoosePainAnimation issue was fixed already :s
The person in the discussion on the forums claims may need more??
It already has been.
I don't see how that works with chunkids though. Or how to serialize character arrays. Since they seem to just store the max size of the array in bytes but...
If new format: https://google.github.io/flatbuffers/ ?