RIGHT. The forums is full of babies and snowflakes lately. It's pathetic. This is not something to be offended over. It's quite laughable to me.I’ve never had someone spam a Raise macro multiple times outside of them raising several people back to back—which isn’t their fault. Maybe 5/8 people shouldn’t have died. Maybe on occasion it will misfire and post twice, but that’s not “spam”. I doubt a GM would consider a raise macro spam either. A lot of the ones I see on Aether are also just one sound effect or none; the latter has been far more common in my recent play.
People are way too sensitive about this.

My issue is the chat spam with them. Long winded stories about someone being rezd with sound effects on that spam multiple times because people can't set macros correctly or they miss their target and have the sound effect playing before the rez takes place. A simple I'm raising <t> is all you need, and you don't even need that if you just agree beforehand who you are raising. Top down or bottom up. FFXIV automatically sorts everyones party list in the exact same way so unless you go out of your way to change it then it's always the same.
If you want to do it then do it, but like I said, personally it's the most cringe thing in the game.



Changing a setting in-game isn't "going out of your way" imho. Some people let themselves be #1 in their list, other's don't and let them be sorted by the normal order.
If you wanna talk about annoying chat macros i must say that moogle wall spam is far worse than rez macros. Especially if players try to discuss mechs.
Will put you on ignore if you can't form a logical argument but argue nonetheless


In random teams that is never happening. People just rez whenever they like.
And such macro barely helps at it. Since when a teammate dies, and you press the button, the other might already have pressed quickcast anyway. Negating any advantage the mention would have given. Sure, he might not use it for the rez then, but its still a wasted cast. And the macro ignores limitation by range. Often enough i have seen someone use a macro, but because he was out of range it didnt even reach the target.
The only real solution here would be if it would be displayed in the HUD. And idealy as a status effect on the player. For quick casts those icons obviously wont be shown (and timing mess can still happen), but on slow casting it would (even in alliance raids), making it clear to other teams that a target is already being rezzed instead of having 3 players targeting the same player without anyone being able to know about it.
Arent those numbers defined before the sorting? So even if you change the sorting, the numbers are still displayed diffirent (for example if you put the tanks last, they still have the lower digits).



Is yourself always "1" then? If so, then the numbers are different for other people or is the rest the same?
Will put you on ignore if you can't form a logical argument but argue nonetheless





Maybe I'm just the odd one here, but I always preferred to use a macro that lets my party know when Swiftcast will come off cooldown, it at least lets my co-healer know that I'm not going to suddenly Swiftcast rez the same person if they have it available.
Something like "Swiftcast available in <recast.Swiftcast>, will rez soon."



The rez macros are just fun. Although "I'm not your mother but i will raise you" lost it's appeal somewhere between seeing it the 2nd and 2192912th time.
Will put you on ignore if you can't form a logical argument but argue nonetheless
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote



