error on load says that when I start the build error has no guardian and provides the bot. deleted the old folder and then put the new routine. follows attached the log. And grateful thanks for the great service and hours of dedication to the community. (sorry for my bad english, is nowhere near my native language)
Update 4.1.5 1. New Balance single rotation added. 2. New Balance multi rotation added. 3. New mushroom placement system for both Restoration & Balance. 4. More talents spells added for use with all specs. 5. Balance druid will now switch to moving rotation if moving during combat. 6. Slight bug fix with Restoration rotation. 7. WARNING added to remind players to restart Honorbuddy if changing spec settings. Now to work on the new battlegrounds assistance system!
Just tested this out in Feral and from what I can tell it just spammed faerie fire or something along those lines. Attached a log for your viewing pleasure Cheers, Steve
After changing your settings and selecting the right spec in the CC settings did you restart Honorbuddy?
trying on my 55 balance druid and i cant get it to do anything goes mookin then cast moonfire 1 time then nothing else tryed in questing then combat bot any help what am i doing wrong thanks. View attachment 59934
hazard, I'm using your Routine on Battlegrounds. There's any way to make it use Lifebloom? I think it only uses it on Tanks in dungeons, but lifebloom on BG's are very important to make clearcast procs.
Update 4.1.6 1. New automatic talent and level detection system added. (Upon loading it will automatically set your preferences to the current spec rotation.) 2. New automatic talent switch detection system added. (If you change your talents wise HazzDruid is loaded it will automatically switch and use the new spec rotation. RESTART OR STOP NOT REQUIRED!) 3. GUI cleaned up a little bit and removed warning message upon saving settings. 4. HazzDruid should only load if your using a Druid.
*sigh* if you used the search feature you would see a number of classes are not working with GB2. no log = no support!