Anyone else ever gotten complained at for using a simple Raise macro in PUGs?

[Rongway]

I like the simple ones. As a SMN main, it\\'s helpful in case I\\'m about to Swiftcast + Raise someone, so that both the healer and I won\\'t waste our Swiftcasts

Swiftcast makes a very distinct sound, though, so a raise notification is really not necessary on WHM SCH AST SMN. Everyone in the arena will easily recognize that Swiftcast has been used as soon as it's used.

However, RDM rarely uses Swiftcast before Verraise, so if anybody should have a raise macro, it's us.
But even then, just "(Verraise) (Just used it.)" should be sufficient.

[Cidel]

But even then, just "(Verraise) (Just used it.)" should be sufficient.

There's something that already fulfills that purpose.


The Raised icon on the dead person's status.

[LeoLupinos]

I hate text macro, that's super childish.

Once a bard used macro for every song he used...

I would like to "block" macro from other players without the need to blacklist them someday...

[Sieben79]

I think people hate the Raise-macro if it has the <t> funktion in it, because everybody sees that this person died (and maybe it's the only person who died 10+ times before in one fight).

It's helpful for other jobs who can raise dead people to see: ah yes, this person is in good care now, then i'll raise another one.

For players who dies in content more often it is a pillory (?). They only see: Look at him/her this looser died again, lol.

[Driskus]

Swiftcast makes a very distinct sound, though, so a raise notification is really not necessary on WHM SCH AST SMN. Everyone in the arena will easily recognize that Swiftcast has been used as soon as it's used.

However, RDM rarely uses Swiftcast before Verraise, so if anybody should have a raise macro, it's us.
But even then, just "(Verraise) (Just used it.)" should be sufficient.

It'd still be useful on other classes if multiple people are dead and I have to hard-cast Raise on someone. I can't count the number of times I've had overlapped hard-casted Raises because someone else decided to swift Raise half a second before my cast finishes. Going back to using a simple text macro would at least have a chance at stopping some of the waste.

[Sieben79]

There's something that already fulfills that purpose.


The Raised icon on the dead person's status.

Scenario: 4 DD are dead. Healer 1 is hard raising without text macro, which one of the 4 DDs get your swiftcast raise?

[Cidel]

Scenario: 4 DD are dead. Healer 1 is hard raising without text macro, which one of the 4 DDs get your swiftcast raise?

And "(Verraise) (Just used it.)" provides an answer to that dilemma how?

Quite frankly if you just used any raise, I can tell which person got the raise with or without a macro saying so.

And to answer your question (though I'm not sure why you're asking me), I'd target the hardcasting healer to see who he or she has targeted. If it's not a dead DPS, then you either wait for like 4 seconds for the Raise to go off and find out, or you take a chance and hope for the best. If you're advocating for a macro that specifically says who you're in the process of raising, then by all means, go for it.

[HyoMinPark]

There's something that already fulfills that purpose.


The Raised icon on the dead person's status.

You'd be amazed as the amount of people who ignore that tiny status icon and re-raise someone you just raised, macro or no.

[Maeka]

I've seen Raise macros and I generally don't mind (and rarely see people saying anything about it), but really I wish people would use two buttons... I hate seeing

"RAISING BLAH BLAH (callx)"
"RAISING BLAH BLAH (callx)"
"RAISING BLAH BLAH (callx)"

Because they hit the button 2-3 times to try to time it precisely when their GCD or what-not was ready.

Maybe.... use the /p macro once, and then if it doesn't work because of a GCD or you had to move or what-not, use the silent one after.

[Tint]

a simple raise macro without sound is fine.

however, it still gets reeeaaaally annoying when your healer is using it every few seconds in a 24 man raid >.>