anyone have a decent macro for BRD?
Id like to get a basis and work from there as I am a total noob on macros.
Printable View
anyone have a decent macro for BRD?
Id like to get a basis and work from there as I am a total noob on macros.
try this one /ac "forum search" <Jotunhammer>
i sense Thailere post will be delete and he will be banned
also, dont use macro it gimps your dps
Banned? Riiight for directing him to use the Search function rather then create the 100th new post on this? Macros are pretty sufficient if utilized correctly and in no way a "gimp"
yes speaking from my own experience.Quote:
Banned? Riiight for directing him to use the Search function rather then create the 100th new post on this?
please enlighten me with macro that does not waste off GCD skillQuote:
Macros are pretty sufficient if utilized correctly and in no way a "gimp"
Don't use macros.
Outside utility macros, for shouting to your party etc, they only reduce DPS.
Don't put your GCD abilities on a macro.
For your oGCDs, use the following macro:
/action "Misery's End"
/action "Bloodletter"
/action "Hawkeye"
/action "Raging Strikes"
/action "Blood for Blood"
/action "Internal Release"
/action "Barrage"
/action "Quelling Strikes"
Note: The order of the buffs is not 100% optimized.
Note2: Depending on mechanics, you may want to separate all your damage buffs into a second macro, leaving your first for "just ME and BL".
Note3: Highly recommend [PC] that you place the individual buffs elsewhere on your UI so you can track all their cooldowns, while using the macro to actually execute most of them.
Note4: You press the macro once between each GCD ability.
Don't use a macro. It really isn't that much of a help.
How does placing bloodletter on a heavy/straight shot, "reduce" DPS? If you're not using that every time it is up you're wrong.
/macroicon "Heavy Shot"
/ac "Heavy Shot" <t>
/ac "Bloodletter" <t>
You can spam the macro and get bloodletter off anytime it is up.
I don't recommend macroing buffs, but Bloodletter shouldn't be used if your GCD is up. Also, with how often it procs and the no TP cost, you should be using it anytime it is up between GCDs buffs or not. I can't see how this would reduce your DPS.
Because any on-GCD ability in a macro disables ability queuing [or seems to, by all signs]. As a result there's a typical 0.1-0.6s delay on using the Heavy Shot (or Straight Shot) depending on how hard you're spamming the button.
For oGCD buffs, you generally want to stack them anyways, so there's little general reason not to use them on macro together.
The only case where this is not true is:
1. Using BFB because of incoming damage.
2. Saving cooldowns, in which case you can still have all your damage buffs together (you can just not press the button), but you don't want Bloodletter combined with them. So you'd have:
1 - ME + BL
2 - ME + BL + all buffs except BFB
3 - ME + BL + BFB
You'd use #2 in a generic situation. Use #1 when saving cooldowns. Use #3 when the boss won't gib you from unavoidable damage.
Assuming ME = Misery's End, that only applies post 20%. In 2.6 seconds, you get off Heavy Shot, Bloodletter, Heavy Shot. That's 450 potency as opposed to 300. Any way you slice it, with Bloodletter being off your Global and BARELY causing a delay, which I have yet to see where a heavy shot doesn't proc when my GCD completes, it's more beneficial to weave it in between your cooldown every time it is up. Not to mention, it's free TP-wise.
I've never noticed a delay from seeing my other non macroed GCD timers and the macroed ones. They shoot when I click it, and the spam makes bloodletter proc about halfway which allows another Heavy right after.
I don't think you really understand the concepts being discussed.
Any way you slice it, 450 potency in 2.7 seconds is less dps than 450 potency in 2.5 seconds.
There's not really much to discuss, except for the reality of the ability queue (or lack thereof).
In which case, the discussion boils down to:
1. Roll a PGL.
2. Get your 3 abilities.
3. Write a macro for "Snap Punch, True Strike, Bootshine", and go kill something. Observe how much you now hate life compared to manually using Bootshine, True Strike, Snap Punch.
If your abilities are actually "shooting when you click it", then you are pressing the button late and I should revise the above number to "450 potency in 2.8 seconds" or something else abhorrent.
You are comparing apples and oranges there.... FOR BRD, macros are fine.... your BL should never be off CD, it is the main damage skill and when its up you should use it, but ya just macro BL and ME to everything, well your 4 damage skills, the 2 dots, HS and SS, make ME 1st, BL 2nd and 3rd is w/e skill you are macroing to... Other classes like MNK and DRG are very hard to make macros for because of their combos... BRD doesn't have any cept for the AOE crap that hardly ever procs.
This is a bad macro and I am going to explain why, and then give you an example of the 1 macro I use on bard, which is 100% more effective than the one you just listed. The reason this macro sucks is because heavy shot is on the GCD, and BL is not. What can happen with this macro is you press it > Heavy shot fires > BL is currently off CD (was used lets say 5 seconds ago, and you have not gotten a proc yet) > Your GCD Comes up again and you fire Heavy shot, at the same time, BL Procs. Depending on timing, this can cause either A) your BL to be delayed due to the animation lock of Heavy Shot or worse, B) Blood Letter procs RIGHT before GCD comes back up and you're spamming the macro. Due to the ability to que up your next GCD ability during the last .2sec during GCD, this can cause the BL to fire before the heavy shot (thus locking out your heavy shot for a second due to blood letters animation lock).
I recommend using a different macro if you insist on using one, and I've gotten much better results in testing mine. A better HS/BL/ME Macro would look like:
/ac "Heavy Shot" <t>
/ac "Misery's End" <t>
/ac "Blood Letter" <t>
/wait
/ac "Misery's End <t>
/ac "Blood Letter" <t>
What results is a macro that FEELS a lot more responsive. Your heavy shot will ALWAYS fire assuming the GCD is up, and mashing the button will subsequently fire ME THEN BL (which is the correct priority for these skills). Should either ME/BL come off CD or proc during the GCD cool down between button presses, they will fire automatically with that 1 second wait, should you have say, moved your finger to another button to fire another skill. It's not 100% perfect, but it is better than the original macro I saw posted everywhere.
So why not
/ac "misery's shot" <t>
/ac "Blood letter" <t>
/ac "Heavy shot" <t>
Because then mashing your heavy shot macro will cause heavy shots to be delayed by the animation of ME/BL everytime they go off, instead of being weaved inbetween GCD's. This is a DPS loss.
How delayed because testing on the striking dummy it appears to cut BL animation off a little. I'm not noticing any difference
If you have problems keeping up with your rotations: OCDs, GCDs, DoTs, then macros will be of benefit to you. They take some of the thought process out of managing your skills, and decrease the buttons you have to press.
If you do not have problems manually keeping up your rotations with efficiency and you don't mind pressing lots of buttons, you will achieve higher DPS than with many of the "One Button Macros" you see floating around.
ah yes, I should have been more specific I guess... I was not very toughtful...
The reason I ask is this...
I am trying to optimise my dps.... ofc
so after I hit the 2 dots, I was thinking heavy shot and other things, and just have one button to watch while I move and wait for the dots to tick down.
so what is the "optimal" skill to use for maximum dps while waiting for the dots to tick down?
winbite is damage potency 60 so spamming that wont do
heavy shot is 150
straight shot it 140
VB is 100
and blodletter is 150
so here is my thinking and it might be wrong... Hit the SS(for the crit) -> VB -> winbiter and then spam heavy shot and straight shot? and then rinse and repeat is that it?
There will be times that you want to save off-GCD abilities; and when managing buffs, there will be even more times that you'll want to save them or use different timings. It's better to just use every skill manually.
No, it's not.
I wish there was a way to sticky discussions.
Regardless of GCD, it is completely impossible to miss a BL proc if you use it only on oGCD.
Thus, just follow these rules
- You shouldn't macro oGCD abilities onto a GCD ability. Simply because spamming will occasionally trigger an ability you did not want. This is a dps loss
- You shouldn't macro CDs onto BL/ME, for the same reason
- BL always has priority over CDs, unless you need to refresh DoTs and a CD just came up. Even then...its debatable.
- It is a TINY dps increase to prioritize ME ahead of BL, which is why people put it that way
- You should have a separate button for BfB, so you don't kill yourself. Don't say I didn't warn you.
- Put goddamn quelling on your bars, and don't revel that you were able to pull threat because you popped everything on pull. Just don't do it.
- There is no reason to stack any cooldowns aside from waiting for Barrage for BfB.
I don't think that's correct is it?
[Raging Strikes], [Blood for Blood], and [Internal Release] all interact with each other in an additive manner, so stacking those three alone doesn't do you any good.
However, [Barrage] interacts with the above three buffs (and [Hawk's Eye] as well) in a multiplicative manner, does it not?
So any time you pop [Barrage] you want to have as many of your other buffs up as you can... correct?
But what about [Hawk's Eye] together with [Raging Strikes], [Blood for Blood], and [Internal Release]?
Do they interact in an additive manner or are they multiplicative?
That's sort of all wrong.
Old testing has all separate buffs stacking multiplicatively, because SE is cool like that.
Does need to be confirmed though.
That said, even if similar buffs are additive, IR should obviously still be used with the others because a higher chance to crit on attacks that have a 20% damage buff is good. The only buffs that you could possibly argue "don't need to be stacked" are BFB and Raging Strikes, which is still incorrect since you want both of them to synergize with IR/Barrage/Hawkeye, even if those two don't synergize with each other. Net result is that you're still using them all at the same time when feasible.
The only note is that you do not want to hold any buff for later for the sheer purpose of stacking them.
If they're all mutiplicative, then it sounds like it's best to:
Raging Strikes (every other buff cycle)
Internal Release (pop every time it's off GCD and you'll hit every Raging Strikes buff cycle with the third cast)
Hawk's Eye
Blood 4 Blood (must pop before Barrage, but want it to be the last buff before Barrage so that the activation time of your other buffs causes you to "waste" less than the full 10 sec when it will be back up before the others)
Barrage
^^^ Every 90 seconds unless you're waiting on a burst phase.
Don't bard macro.. Just don't...
If you HAVE to have macros simply use them for your cool downs, ie: 1 macro for your offensive 4 and 1 macro for your defensive 3..
Just don't macro please. :)
Not macroing at all is pretty stupid.
Sorry, what I meant by that line is it is not necessary to save cooldowns to stack.
You will lose dps that way.
This is why I don't use them. Even if it was better than having each ability on it's own on the action bar (which it's not) it just feels clunky and slow. In order to make it not be a dps loss you literally have to just sit there and mash that one button as fast as physically possible to make use of it. What it does do for sure however, is give you less control over your actions and when you use them.
BRD doesn't have so many abilities that it would warrant sticking a bunch of them together into a single button.
What?
We have just as many as any other Job...
If you use no macros, you need a minimum of 27 buttons to be effective (not even counting the typical things every other class has such as potions, food, mount, sprint, limit break, etc...)Code:ON GCD OFF GCD Situational
Straight Shot Misery's End Ballad
Windbite Bloodletter Foe Req
Venomous Bite Flaming Arrow Paeon
Heavy Shot Blunt Arrow Battle Voice
Quick Nock Repelling Shot Shadowbind
Rain of Death Raging Strikes Invigorate
Wide Volley Hawk's Eye Second Wind
Barrage Featherfoot
Blood for Blood Swiftsong
Internal Release
Quelling Strikes
Even ignoring the situationals, 18 buttons is a LOT when you're having to make decisions 2 (or more) times per GCD about which to press.
So I agree with EasymodeX here that telling people not to macro anything is silly.
The 11 Off GCD skills can be turned into 3 or 4 with little to no detriment to your dps.
With mod keys, it wasn't difficult for me to set up intuitive bindings that don't extend past 5RGB.
Depending on the group and encounter, the timings you want on buffs can vary greatly. For instance, on Titan I can only use Raging Strikes once to ensure it's up in time for the heart. If my group is on the slower end, I can get up to two uses of Hawk's Eye and Blood for Blood, and sometimes even three uses of Internal Release. Sometimes DPS is fast enough that I can only afford to use Hawk's Eye at the pull, but slow enough that I can use Blood for Blood twice. Or it's so blindingly fast that I can only afford to use Internal Release twice and have to hold everything else.
When heart phase hits and my FC is carrying 3-4 other players, I usually hold Barrage until closer to the first gaol spawn to get my people out of it quicker. I may even hold a Heavier Shot proc and a Bloodletter for it, depending on who's in the gaol, the speeds at which I anticipate the heart and gaol to drop, and the availability of other off-GCD abilities. And proper timing for Blood for Blood post heart is a given.
I get small decisions like these everywhere, whether it's Wanderer's Palace or Binding Coil of Bahamut, and forcing a bunch of skills into macros only makes things less flexible and less interesting. With the presence of a spell queue, having to press more buttons to get the job done is a non-issue. Most people who actually play a Bard at a high level see multi-skill macros as not much more than a liability.
i have 2 macros. the 1 and only reason i do so is because of the limited space on my crossbar. i cant tell you how many times i have been on the wrong crossbar, not realize it, and hit the LB or something unwanted.
anyways...
1) buff macro. all attack buffs in one button. i have them staggered by length of effect greatest-->shortest. by the end i have 10-15(??) sec window of burst dmg. (cant remember)
2) the 2 bites. just makes life easy.
I personally like to use HS, SS, VB and WB as plain skills (no ME/BL macro'd to them) and then spam a ME/BL/HS macro in between the skills. I tinkered with having ME/BL macro'd to the GCD skills before but I found it somehow very clunky, might have been because of the nonexistant skill queue. I'm having an easier time now using 1234 for the 4 basic skills and then spamming the Bloodletter macro on my mouse between GCDs.
The only macros I use regularly are the BL macro and one that chains all DPS cooldowns apart from BfB. I've also got a couple situational ones I swap into my bars depending on the fight, the most used one probably being this:
Code:/micon "Blunt Arrow"
/ac "Blunt Arrow" <t>
/wait
/p [Blunt Arrow] interrupt used! <se.3>
I macro Misery's End onto Heavy Shot because it only affects the last 20% of the battle. However I keep Bloodletter separate. I prefer the control to react to it separately rather than having to mash the one button and wait for animation. I play with controller so I have one macro for all the buffs to save some room (I have a horizontal bar below the cross bar with all the macroed skills so i can see the individual CD. I also macro Internal Release in front of both bites (on separate buttons) as it has the fastest CD and I particularily want the crit boost on the dots for RoB procs.
Apart from that I only have macro for Blunt Arrow with a line for /p chat to indicate I have silenced for things like ADS. When I don't need to use communicate i switch the macro for the plain skill to weave inbetween GCD
I use this macro as brd:
/ac "Venomous Bite" <t>
/wait 2.5
/ac "Windbite" <t>
/wait 2.5
/ac "Bloodletter" <t>
/wait 2.5
/ac "Feint" <t>
/wait 2.5
/ac "Heavy Shot" <t>
/wait 2.5
/ac "Heavy Shot" <t>
Heavy Shots until VP drops and repeat.
Then I use the buffs between those /wait 2.5 since it ignores the GCD. Same with Feint, ME and Flaming Arrow.
I mix a standard macro with custom buffs/actions as I see fit. I think we can agree not to auto everything but smashing buttons to every skill isn t the best way or at least that s how I see it.
To those who say don't use Macros for Bard.... seriously just go play another class cause you are giving bad advice on a class you are playing.
Bards don't use 1 they don't use 2 macros. A perfect bard puts Misery's End and Bloodletter on almost every GCD skill from Heavy Shot, Straight Shot, Venomous Bite and Windbite. You're just gimping yourself for not doing it. Everytime I go up against another bard and If i hear my Misery's End sound effect going off faster and more often than "THAT" other bard I know they are not using macros.
DO not freaking use /wait 2.5 on a macro geez more freaking bad advice. There is no need to!
Also who says you can't macro Monk Combos? You just put them in a reverse combo and it works 100% of the time so you can focus on positioning only. But that is another debate for another thread.
OP, to answer your question, yes you can use macros for a BRD. Use the ones posted earlier in the thread that assigned bloodletter and miserys end to heavy, straight, venomous, and wind. I have tested it multiple times on dummies manual and with macros and I literally see no difference aside from RNG. I've also cleared BC using these macros and the only time I have ever had any issue with a macro was getting animation locked and missing a silence like 1 time on turn 2. I also have all my hot keys on my naga set to repeat at their max speed while being pressed so I don't see how a "delay" would even be a problem.