Hey!
A little bit weird to write an issue to a project that im working on solving or making the bugs on it
I'm using Fedora KDE (yes, Linux) on the latest commit for CC and whenever I'm trying to use GUI Cursor > cursor-action > HOVER_TOTEM the mouse doesn't move to the totem
Steps to reproduce:
- Enable
GUI Cursor module
- Set cursor action to
HOVER_TOTEM
- Open the inventory with a totem in it
- Mouse doesn't move/select the totem
Expected behavior:
Mouse should automatically move to the totem slot while HOVER_TOTEM is active
Possible cause:
This is likely a Wayland compatibility issue. The module uses GLFW.glfwSetCursorPos() in setCursor() to programmatically move the mouse - this is a known limitation on Wayland, where glfwSetCursorPos is only guaranteed to work if the cursor is in disabled/captured mode (e.g. in-game with locked cursor). When the inventory is open the cursor is in normal mode, and Wayland's security model explicitly blocks applications from repositioning it, causing the call to silently fail. This works fine on X11 and Windows where no such restriction exists.
Environment:
- OS: Fedora KDE (Linux) — Wayland session
- ClickCrystals version: latest commit — bdafa34
Hey!
A little bit weird to write an issue to a project that im working on solving
or makingthe bugs on itI'm using Fedora KDE (yes, Linux) on the latest commit for CC and whenever I'm trying to use
GUI Cursor>cursor-action>HOVER_TOTEMthe mouse doesn't move to the totemSteps to reproduce:
GUI CursormoduleHOVER_TOTEMExpected behavior:
Mouse should automatically move to the totem slot while
HOVER_TOTEMis activePossible cause:
This is likely a Wayland compatibility issue. The module uses
GLFW.glfwSetCursorPos()insetCursor()to programmatically move the mouse - this is a known limitation on Wayland, whereglfwSetCursorPosis only guaranteed to work if the cursor is in disabled/captured mode (e.g. in-game with locked cursor). When the inventory is open the cursor is in normal mode, and Wayland's security model explicitly blocks applications from repositioning it, causing the call to silently fail. This works fine on X11 and Windows where no such restriction exists.Environment: