Lightning rod doesn't work on new instances if mounting a rhoa and if weapon set 1 was selected
I have one bow and one quiver, fixed for weapon set 1 and 2.
Lightning rod is set to weapon set 2, the other skills to weapon set 1, and spirit skills to both. If I had weapon set 1 selected when entering a new instance, I can't cast lightning rod. It only happens when I'm mounting the rhoa. I can fix it by unmounting or swapping weapon sets (either with a skill or by pressing "X". summarizing, when entering a new instance: If weapon set 1 was selected and I'm mounted: Bug If weapon set 2 was selected and I'm mounted: Fine If weapon set 1 was selected and I'm not mounted: Fine If weapon set 2 was selected and I'm not mounted: Fine This bug is present in any instance switch without fail. Here's a video showcase of the bug, using on-screen keyboard to show keypresses: https://youtu.be/kVw_T--z-g4 IGN: vieira Last bumped on Sep 22, 2025, 2:07:02 AM
|
![]() |
Also running into this issue when I join an instance. Called Shots also doesn't seem to be active on the weapon swap. Idk what's going on. Makes Rigwald's Ferocity seem like a waste of money.
|
![]() |
I am having the same issue. I plan to do a weapon swap for now, as unmounting a Rhoa causes it to wander off and start pecking mobs.
|
![]() |
Also having same issue.
I noticed that it can be fixed if you remove Rigwald's Ferocity gem. So it's something about Rhoa and Gem. | |
Same issue.
Until this is fixed Rigward's Ferocity cannot be used together with Rhoa Mount. |
![]() |
Having this bug myself, also while using Rigwald's Ferocity (Weapon Slot 2 usage). So far the only 'solution' I've found is starting off (before going into the instance) with my weapon swapped to the slot Lightning Rod is being used in. It seems to function normally after that, but the issue will return if you change instances again without still being in the Lightning Rod weapon slot swap.
So Rigwald's Ferocity is usable with Rhoa Mount, just has some slightly annoying ways you need to handle it that definitely still call for a bugfix in the future so we don't have to deal with it. |
![]() |