Quest Book Open Keybind
nucruh opened this issue · 9 comments
Your GTNH Discord Username
123mrk123
Your Pack Version
2.6.0-beta-3
Your Server
SP
Java Version
Java 21
Type of Server
Single Player
Your Expectation
Press grave key once and the quest book opens.
The Reality
Press grave key once, nothing happens, press it a second time and then it opens.
Your Proposal
Open the questbook upon one press of the grave key.
Final Checklist
- I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
- I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
- I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
see #99
I'm definetely on 2.6.0 beta3, and for me it wasn't ever a problem in 2.5.1 but now it is.
The issue still happens if I switch it to another key.
include non-deadkeys? (grave being a deadkey is not a pun and just means you gotta press it twice on some layouts for stuff to happen)
you should also list your OS and keyboard layout.
Some observations:
in 2.5.1 the key is marked as GRAVE, in 2.6.0-beta-3 it's marked as ¸
I also switched launchers, Technic -> Prism.
Perhaps this is happening because its registering the typing off ¸¸ and not just the press of GRAVE key, (¸¸ requires 2 presses for me to be typed out).
Does the issue still happens if you switch the keybind to a different key? Try a simple letter key, just to make sure this is a problem with the mod, and not your OS/HW's special character recognition.
Press grave key once, nothing happens, press it a second time and then it opens.
Are you sure you are on 2.6.0 beta3?
Because this was a problem in 2.5.1 and other earlier versions. And its very much fixed on my end in lwjgl3ify 2.0.0alpha7+
(Ill try again on beta3 to be sure)
hmm. I dont know what happened. as you can see in the other ticket I tested it and found it working. Must have done something different. :(
Because now I am trying and its not.
