Hello,
I found a reproducible issue with GSE keybindings on one character/spec.
Addon version:
GSE 3.3.21
Character / Spec:
Shaman / Elemental
Issue:
When I bind Mouse Button 4 inside the GSE keybinding UI, GSE visually shows the binding correctly:
Button4 (Test)
However, pressing Mouse Button 4 does nothing.
The sequence does not start at all. It does not even execute a simple /targetenemy .
This is not a sequence issue, because the same test sequence works when bound to a keyboard key such as F8.
Test sequence used:
/targetenemy
/cast Stormkeeper
What I tested:
- Mouse Button 4 works normally with regular WoW action bar buttons.
- Mouse Button 4 works with normal WoW macros.
/targetenemyworks with a normal WoW macro.- The same GSE sequence works when bound to F8.
- Other characters/specs, for example BM Hunter, still work correctly with Mouse Button 4 in GSE.
- The issue appears only on this Shaman / Elemental GSE keybind state.
Important verification:
After binding Mouse Button 4 through the GSE UI, I ran:
/run print("B4:", GetBindingAction("BUTTON4"))
Result:
B4:
So WoW has no real binding registered, even though the GSE UI shows:
Button4 (Test)
Manual workaround:
If I manually write the binding with this command:
/run SetBindingClick("BUTTON4","Test","LeftButton"); SaveBindings(GetCurrentBindingSet()); print("B4:",GetBindingAction("BUTTON4"))
then the result becomes:
B4: CLICK Test:LeftButton
After that, Mouse Button 4 works correctly and the GSE sequence executes.
Expected behavior:
When I bind Mouse Button 4 through the GSE UI, GSE should write the same active WoW binding as SetBindingClick() does.
Expected result:
B4: CLICK Test:LeftButton
Actual behavior:
The GSE UI shows the keybind, but WoW’s real binding table remains empty:
B4:
This means the GSE UI displays the binding, but the keybind is not actually active in WoW.
Possible cause:
It looks like the GSE keybind UI creates or displays the Button4 entry internally, but does not always call or persist the real WoW binding via SetBindingClick() / SaveBindings() for this character/spec binding state.
Temporary workaround:
Manually run:
/run SetBindingClick("BUTTON4","EXACT_SEQUENCE_NAME","LeftButton"); SaveBindings(GetCurrentBindingSet()); print("B4:",GetBindingAction("BUTTON4"))
For Mouse Button 5:
/run SetBindingClick("BUTTON5","EXACT_SEQUENCE_NAME","LeftButton"); SaveBindings(GetCurrentBindingSet()); print("B5:",GetBindingAction("BUTTON5"))
Suggested fix:
When saving a mouse button keybind through the GSE keybinding UI, please verify that the binding is actually written to WoW’s binding table.
Example logic:
SetBindingClick("BUTTON4", sequenceButtonName, "LeftButton")
SaveBindings(GetCurrentBindingSet())
Then confirm:
GetBindingAction("BUTTON4")
The key point is:
GSE UI shows the binding, but GetBindingAction("BUTTON4") remains empty.
Manual SetBindingClick() works immediately.
Thank you.