Unbinding the Quiver Key causes Invalid Key GL Errors to spam the log
gliscowo opened this issue ยท 2 comments
By directly checking the Quiver keybind against InputConstants.isKeyDown (at least on Fabric), there is no handling for unbound keys (represented as Keycode -1) and the log gets spammed with the game reporting the resulting GLFW errors every tick
To alleviate this, it should first be verified that the binding is actually bound using KeyMapping.isUnbound
Cheers
