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

[Driskus]

Just curious as the whether this is a problem for anyone who uses a simple Raise macro (not the annoying or berating ones). The reason I'm asking is because I stopped using them shortly after SB was released. PUGs were complaining about it constantly. A simple message the way we used to do it in the XI days: "<Raise> -> <t>" with no sound alarm got me multiple complaints from several groups since SB released.

I don't know why anyone would complain about it, but it happened before. I totally get someone getting flak for the more "questionable" or annoying Raise macros out there, but not for a very simple one unless they're spamming it like 10 times in a row to get it to work.

I want to start using one again to help with the overlap that tends to happen in newer trials, but I don't want to do it if it still annoys too many people.

[Wyvernheart]

I thought everyone hated raise macros. Like the blm that thinks he's Harry Potter or the drk who thinks he's playing Berserk.

[swiss_Momo]

just tell them to stop giving you a reason to use it then :^)

[sweetstack]

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, or just time casting. It depends on the healer in each instance, of course, but if someone dies, I try to Raise them as soon as possible to lessen the burden on the healer.

I have admittedly seen the really long Raise macros that take up the length of about two or more of my chatboxes, have sound effects, and get spammed in 24 player content. Perhaps the experience with such macros has soured some people on any Raise macro; I\\'m not sure. I find the short ones helpful, and if you do, too, I would keep using them.

[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.

[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?

[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.

[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.

[HyoMinPark]

I’ve had Raise macros for a long time to alert co-healers of whom I’m raising. Never had anyone complain about it; they tend to more so ignore it and Raise the same person I’m already casting a Raise on. ._.