And that is exactly why it's in there. Why have TWO different raise macros; one for when I need ballad one for when I don't? No, just have one simple one that states it in ONE line that way the BRD can see what I need without me having to take my keys off of my spells to type out "Hey, ballad pls"XI didn't exactly have a large chat display window or resolution. (Also I personally love seeing people's variants on Raise and Provoke macros)
Also if you dislike unnecessary info in macros we really don't need to know what your MP or HP are on cast unless you're calling for a mana song.
Also, an FC buddy who does Summoner uses this macro:
"{Ressurection} on <t>! Welp, there goes my DPS."
So do you use your Raise macro to call for Manasong if you're not raising? (It still doesn't explain the HP being present either)And that is exactly why it's in there. Why have TWO different raise macros; one for when I need ballad one for when I don't? No, just have one simple one that states it in ONE line that way the BRD can see what I need without me having to take my keys off of my spells to type out "Hey, ballad pls"
I'm kind of genuinely curious here because if a Bard isn't looking at your MP to begin with I doubt throwing two strings of numbers into party chat is actually going to get their attention.
Last edited by Garlyle; 01-06-2015 at 01:48 AM.
Now you're just nitpickingSo do you use your Raise macro to call for Manasong if you're not raising? (It still doesn't explain the HP being present either)
I'm kind of genuinely curious here because if a Bard isn't looking at your MP to begin with I doubt throwing two strings of numbers into party chat is actually going to get their attention.![]()
These are some great and hilarious macros everyone! Keep em it up!
http://www.animeotakus.org/image/anime/1404/because-skill-brings-knife-gun-fight-wins-anyway-blade-and-s-anime-otakus-1398098083.jpg
The one guy in my fc has one that goes something like:
/p I can prove <t> is casual! /ac "Raise" <t>
I honestly don't think most of the raise macro are funny.
First of all, as someone mentioned, commonly used action shouldn't put a macro especially these who spam the button without the <wait.1>. It gets extra annoying with the <se.X>. In the end of event, you just leave the evidence so many lines of people died... Also, why do you need to tell the other people you are raising someone?
I always think if someone die, it is my fault 'cus I didn't keep their HP up. Even if they are the fool who can't dodge, you think if they can't notice the shinny weird-looking indicator on the ground, they will notice you are so busy to keep the pt alive or they are the fool? Of course they will blame you "never" cure them. So, it almost will result to be a jerk healer with these "wake up" "stop being lazy" macro...
I never give commendation to these use these macro users either
|
![]() |
![]() |
![]() |
|
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.