
Originally Posted by Lhivera
Not getting any help on the official forums on this, thought I'd throw it out here and see if anyone has any ideas.
Up until yesterday, I was using a macro, with SuperMacro, that used the following logic:
- Am I mounted? If so, dismount, SetView(2), and stopmacro.
- Am I in a fly zone, and clicking button 1?, If so, use flying mount, CameraZoomOut(8), stopmacro.
- Else use ground mount.
I was doing it like so, using SuperMacro to get around the character limit (I was using one of several random mounts, which beefed up the character count considerably):
/click [mounted] SuperMacroClick_Dismount
/stopmacro [mounted]
/click [flyable,button:1] SuperMacroClick_FlyMount
/stopmacro [flyable,button:1]
/click SuperMacroClick_GroundMount
As of 2.3, the /stopmacro commands fail. When I dismount, I immediately start to mount again. If I mount a flying mount, I get an error that I can't use a ground mount due to another action being in progress.
I've received some tips that help clean up some of these problems, but they rely upon dropping SuperMacro; the result of doing so is that I can no longer limit the CameraZoomOut(8) command to the flying mount action.
Anyone have any suggestions to restore that old behavior?
|
I'd just change the order in which you do things.
/click [nomounted, flyable] SuperMacroClick_FlyMount
/click [nomounted, noflyable] SuperMacroClick_GroundMount
/click [mounted] SuperMacroClick_Dismount
This assumes you have an epic flying mount, if not, you can add further modifiers in there to control which mount you want.
Remember that the mounts each have a cast time, so the [mounted] modifier won't come into play until after the cast is complete.