Macros... Help!

Hello there! I was trying to use this macro:

/micon Raise
/p *raising* <t> <se.10>
/ac Swiftcast
/wait 2
/ac Raise
/ac Resurrection
/ac Ascend
/wait 60
/echo Swiftcast Raise is ready! <se.10>

What I want is to raise someone and announce it in the chat. I would like to make sure I have swiftcast first, and also add Lucid Dreaming at the end. The problem I'm having is that I use Razer Macro keyboard and no matter how I program it, I can't seem to make it work. My screen just "blinks" and it looks like a "reverse camera view" for a split second and then nothing happens.

Please help :)

You can reduce the wait to 1 and you need have the player targeted until you see the skill get used. I dunno about what happens with camera. Might wanna check your key binds, sounds like it has something else on it.

Macros are very fragile and break when you breathe their way. More lines you have the easier it breaks. It's all to discourage any form of automation.
At most your macro should look like
/ac "Raise"
/wait 1
/p Raising <t>

Swiftcast and especially Lucid you should be pressing yourself and should not be limited to res situations.

Having Swiftcast in your raising macro works just fine. I have it in all of my raising abilities for my healers. Having it there doesn't limit someone to use it just for Raise.

This is how I use mine, and works fine:

/macroicon "Ascend"
/ac "Swiftcast"
/wait 0.5
/ac "Ascend"
/p Attempting to cure <t> from an unknown infection, stand-by. Recovery successful! <se.9>

Just make sure you keep the person targeted until your Raise fires off, or it wont go and your Swiftcast will continue to count down. If you are fast enough, you can reselect the target and use the same macro - it will still fire your Raise ability. If you want to add Lucid Dreaming to it at the end, I would use at least a /wait 1 before the ability - lag will kill the macro.

You might be having problems with running all three of those abilities as well at the same time, which might be your issue. I've tried that in the past and it's just been a nightmare because of how it works. Crafting macros can sometimes lag behind and mess up your usual HQ run on items too - lost some essential things doing that, lol. Keep it simple. If it's important, do it yourself.

Having the announce macro, and then pressing raise manually is likely safer.

That gives you the freedom to save your swiftcast if you know you could need it for an upcoming mechanic, and ensures that a little targetting mistake won't end up announcing without the rez triggering.

Quote:

---

Originally Posted by Greyhawk

Having Swiftcast in your raising macro works just fine. I have it in all of my raising abilities for my healers. Having it there doesn't limit someone to use it just for Raise.

This is how I use mine, and works fine:

/macroicon "Ascend"
/ac "Swiftcast"
/wait 0.5
/ac "Ascend"
/p Attempting to cure <t> from an unknown infection, stand-by. Recovery successful! <se.9>

Just make sure you keep the person targeted until your Raise fires off, or it wont go and your Swiftcast will continue to count down. If you are fast enough, you can reselect the target and use the same macro - it will still fire your Raise ability. If you want to add Lucid Dreaming to it at the end, I would use at least a /wait 1 before the ability - lag will kill the macro.

You might be having problems with running all three of those abilities as well at the same time, which might be your issue. I've tried that in the past and it's just been a nightmare because of it works. Crafting macros can sometimes lag behind and mess up your usual HQ run on items too - lost some essential things doing that, lol. Keep it simple. If it's important, do it yourself.

---

Nope, mine works just fine and has since I made it and it nice to add on PS4. Also the 0.5 got change to 1 so they are same, its all whole seconds every time. Server side lag does and could mess up Marcos on occasions. But that doesn't seem like their problem. Its worth Getting a friend or someone off of PF to test marcos before using in combat.

I personally avoid Swift+Raise, it's very clunky and has that 1 second delay on top on not being able to queue. Ideally healers communicate and you don't need a macro, but if you have to announce it keep Swiftcast separate and simply use:

/macroicon "Raise"
/p Raising <t>
/ac "Raise"
/ac "Raise"
/ac "Raise"
/ac "Raise"
/ac "Raise"
...repeating.

The reason for filling the rest of your macro with /ac Raise is that it attempts it multiple times in quick succession, which can sometimes avoid the macro failing from being pressed a half-second too early. The same is true for basically any macro action.

I'd also recommend

/micon Swiftcast
/p Swiftcast ready in <recast.Swiftcast> <se.2>

...to communicate to your group if Swiftcast is unavailable and when you can Raise.

Quote:

---

Originally Posted by Greyhawk

/wait 0.5

---

That's not a real thing. Waits always round to the nearest whole second. Run this macro:

Code:

---

/cd 6
/wait 5.5
/e <se.9>
/wait 3
/cd 6
/wait 6.4
/e <se.9> <wait.3>
/cd 6 <wait.5.5>
/e <se.9> <wait.3>
/cd 6 <wait.6.4>
/e <se.9>

---

All the dings happen at the same times that the 6s countdowns finish.

Quote:

---

Originally Posted by Bsrking5

Nope, mine works just fine and has since I made it and it nice to add on PS4. Also the 0.5 got change to 1 so they are same, its all whole seconds every time. Server side lag does and could mess up Marcos on occasions. But that doesn't seem like their problem. Its worth Getting a friend or someone off of PF to test marcos before using in combat.

---

Quote:

---

Originally Posted by Rongway

That's not a real thing. Waits always round to the nearest whole second. Run this macro:

Code:

---

/cd 6
/wait 5.5
/e <se.9>
/wait 3
/cd 6
/wait 6.4
/e <se.9> <wait.3>
/cd 6 <wait.5.5>
/e <se.9> <wait.3>
/cd 6 <wait.6.4>
/e <se.9>

---

All the dings happen at the same times that the 6s countdowns finish.

---

Yeah, I'm aware that changed to /wait 1. I never changed it from what I had a long time ago and just left it in. It treats it as /wait 1 anyways. I'm going through all my macros again around this time, deleting and changing things. I might get around to that one.

Quote:

---

Originally Posted by Liam_Harper

I'd also recommend

/micon Swiftcast
/p Swiftcast ready in <recast.Swiftcast> <se.2>

...to communicate to your group if Swiftcast is unavailable and when you can Raise.

---

I dont, few party chat macros the better. They get annoying real fast