Just play that fight by hand until it gets fixed and you won't get booted, have we all really grown that dependent on our routines? It's a convenience yes, but you should learn your class regardless.
How much emitting info to wow chat is dangerous? There are so many settings - is rotation active/paused (envy pushed this info by default to chat) is aoe active/inactive is burst active/inactive (and is cooldowns active/inactive)........ is it possible to render some mini bar (for example, in top left screen), and show current state i don't even know is it possible to do with honorbuddy (via plugins or so)
39 is up, but still same behavior, tried with force combat in Enyo, but that doesn't work either. So far only YRB2 is working for me on this boss.
I feel like routine is doing less DPS now than before. Was pulling 30k consistently now only like 27-29k
Guys you were warned about this previously, it's disrespectful to suggest another routine in a thread for a paid routine.
I feel like you are using cra-cked honorbuddy with a cra-cked Stars. You won't get the new updates as soon. Just a assumption.
Does anyone have logs/rankings of their BRF fights using this CR? I just want to see how well it is pulling so I can determine whether to buy it. Also, do you follow icey veins or anything in particular for the routine? Have you had a look a Cyrous's indepth Boomkin guide Mirabis? Moonfarespam: The Moonkin Guide (6.0.x) - Forums - World of Warcraft
With 682 ilvl, I was generally ranking around 50-60th percentile on most fights. I think 80ish on Iron Maiden. (On BRF Heroic)
I'm in 90th percentile on most fights as 680 with multiple top50's in heroic (except kromog, haven't done it since the update though)
freezing on kromog randomly. sometimes at the start of the fight, sometimes after grasp, always freezes during grasp with the error that i'm mounted (search attached log for [11:00:28.191 N] [28:191]: Pause: I'm Mounted) View attachment 31816 2015-02-11 19.01.txt edit: sorry if this is a hb issue just saying that it's still happening even with the routine update