if you make any stack with a role action as a base action, this stack will be applied to every single job that can use the role action, when they press that role action.
this causes erratic behaviour by having multiple stacks with eg: swiftcast between multiple jobs, like WHM, SCH, BLM,....
the following pull request https://github.com/attickdoor/MOActionPlugin/pull/95 should fix this issue while maintaining the "accidental" functionality of allowing the baby classes (CNJ, GLA,....) to share their action stacks with the adult classes of (WHM, PLD,....).
if you make any stack with a role action as a base action, this stack will be applied to every single job that can use the role action, when they press that role action.
this causes erratic behaviour by having multiple stacks with eg: swiftcast between multiple jobs, like WHM, SCH, BLM,....
pretty sure this is also what https://github.com/attickdoor/MOActionPlugin/issues/73 experienced.
the following pull request https://github.com/attickdoor/MOActionPlugin/pull/95 should fix this issue while maintaining the "accidental" functionality of allowing the baby classes (CNJ, GLA,....) to share their action stacks with the adult classes of (WHM, PLD,....).