<st> not working with sets.

Platform:PC
ISP:AT&T Uverse
Type of Internet Connection:
DSL/Broadband
Internet Connection Speed:
15mbps dl/2k mbps ul
Date & Time:
Sept. 14, 2014 about 9ish EST

Frequency:
Always

Character Name:
Elizara

Race:Mithra


World:Quetzalcoatl

Main Job:99 WHM
Support Job:SCH

Area and Coordinates:Not relavant

Party or Solo: party

NPC Name:None

Monster Name:None

Steps: 1. Make a cure macro with sets and make sure the equip set switches are before /ma "Cure" <st>.
2. Notice that <st> does not work anymore, for cures at least in that particular situation. The cursor disappears before you can cure, leaving you with a non-working macro. <stal> and <stpt> still work however.

Please fix this, it's worse than annoying; I have used <st> so I can cure mission npcs as well as my party in the past. Being stuck with <stal> does not cut the mustard..I'll add a video later to show what I mean if this isn't enough information.

Put the <st> before the equip change. It should still work for everything aside from fast cast gear. If there is fast cast gear, it probably wasn't taking effect if you're equipping it with no wait before the casting anyway.

I'll switch controllers and try that cat. Still annoying; and the set I'm swapping to btw is basically a base set with some fast cast in it, then I swap to idle. ^^

[Edit] Thank you cat. I had to add a wait to get the idle set to swap in (<wait3>) but it now works the way it should, I'll swap the rest of my cure macros to match so I can cure a certain princess in the current Seekers final fight without cursing.

I'm glad it worked for you. I don't think it should have to work that way though. There's no reason we should break target just by changing gear.

Amen Cat. I hope they fix that, breaking target sucks and I couldn't figure out WHY it was doing that, to the utter failure of me trying that mission with my static twice >.<. It sucks when you can't cure people when you're the whm. I'll edit the first post to make that clear to the moderators since this has been sorta solved, but not really.