Resurrection Macro Assistance

[Sub-Xero]

I have the exact same macro exept with Raise, it seems to work fine out in the open world, but oftentimes messes up in instances mostly just activating swiftcast and not raise, found that weird but thought that i prob just wrote the macro wrong or something.

Yeah I found that most of my macros weren't working properly while in an instance. I had to change all my Summon macros to /wait 1.5 because they weren't going off.

[Tari-F]

Yeah I found that most of my macros weren't working properly while in an instance. I had to change all my Summon macros to /wait 1.5 because they weren't going off.

Just so you know, the /wait command (unless they changed it recently) only accepts whole numbers, and it rounds up from 0.5 to the next closest whole number. "/wait 1.5" is the same as "/wait 2".


I've been manually casting the Swiftcast + Resurrection combo, and I haven't run into this issue, so I'm pretty curious about it now.

[Sub-Xero]

Just so you know, the /wait command (unless they changed it recently) only accepts whole numbers, and it rounds up from 0.5 to the next closest whole number. "/wait 1.5" is the same as "/wait 2".


I've been manually casting the Swiftcast + Resurrection combo, and I haven't run into this issue, so I'm pretty curious about it now.

Hmm... Well I've seen around the net other people using 2.5+ second /wait(s) in their macros to account for (G)CD and they went back to working just fine after I slapped a .5 in there so I don't know. Really wish SE had detailed instructions about EVERYTHING pertaining to these kinds of things...

[Tari-F]

Hmm... Well I've seen around the net other people using 2.5+ second /wait(s) in their macros to account for (G)CD and they went back to working just fine after I slapped a .5 in there so I don't know. Really wish SE had detailed instructions about EVERYTHING pertaining to these kinds of things...

Yeah, it's pretty silly that they don't have clear documentation on some of their commands. For /wait, though, a number of people have actually spent the time testing the values you can input (mostly for crafting macros), and the .5s all round up to the next closest whole number.

Since the .5 is still adding a full second to the wait timer, anything that needs that extra second to activate will work with the .5. If you put .4, though, it'll probably break again, since that rounds down instead of up.