I encountered a few issues with interacting with death gate, I would say it's unstable to run the profile with death gate. But you said before that the first thing the bot did was creating a death gate outside the entrance? That should never happen.
ok, continue to use the profile without death gate, I need to find a more reliable way for the bot to use it.
always "ForcedMount-Forced: In Progress (no associated quest) Mounting for Ground travel [Ref: "[Fandig2] Everbloom Farm" @line 194]" I am crazy.
I have already replied to your problem. "The log says that you don't have a mount when trying to mount up.. try uninstalling HB and delete the whole folder where HB was in (save important profiles/plugins if you have them there) then install a new HB in a new folder."
Update: Version 1.6.5 Fixed problem with death gate, added death gate support for legion DK's. Fixed a problem some people had which caused to bot to stop before moving to the right side of the dungeon. You only need to download this version if you use death gate or had a problem when the bot stopped in the middle of the dungeon.
I used the normal one I think cant remember, but I used this profile before the HB3 update, and the Death Gate was working all the time there. https://www.thebuddyforum.com/honor...erbloom-farming-2000-3000gph-raw-gold-16.html Edit: Then I try to load profile now I get this error: Code: Changing current profile to [Fandig2] Everbloom Farm 8 compiler errors encountered in profile '[Fandig2] Everbloom Farm' 'CustomBehavior' xml element on line number 356 has following errors with code: public System.Threading.Tasks.Task __ExpressionFunc__106() { return new System.Func<System.Threading.Tasks.Task>(async () =>{Move = rnd(6);})(); } 1) The name 'Move' does not exist in the current context at line 0 2) The name 'rnd' does not exist in the current context at line 0 'If' xml element on line number 357 has following errors with code: public System.Boolean __ExpressionFunc__35() { return new System.Func<System.Boolean>(() => Move == 1)(); } 1) The name 'Move' does not exist in the current context at line 0 'ElseIf' xml element on line number 359 has following errors with code: public System.Boolean __ExpressionFunc__36() { return new System.Func<System.Boolean>(() => Move == 2)(); } 1) The name 'Move' does not exist in the current context at line 0 'ElseIf' xml element on line number 362 has following errors with code: public System.Boolean __ExpressionFunc__37() { return new System.Func<System.Boolean>(() => Move == 3)(); } 1) The name 'Move' does not exist in the current context at line 0 'ElseIf' xml element on line number 365 has following errors with code: public System.Boolean __ExpressionFunc__38() { return new System.Func<System.Boolean>(() => Move == 4)(); } 1) The name 'Move' does not exist in the current context at line 0 'ElseIf' xml element on line number 368 has following errors with code: public System.Boolean __ExpressionFunc__39() { return new System.Func<System.Boolean>(() => Move == 5)(); } 1) The name 'Move' does not exist in the current context at line 0 'ElseIf' xml element on line number 371 has following errors with code: public System.Boolean __ExpressionFunc__40() { return new System.Func<System.Boolean>(() => Move == 6)(); } 1) The name 'Move' does not exist in the current context at line 0
So I fixed it. Sorry about that, I just copied over working code from a test profile and forgot to add an variable. Try it now.
Hmm, when I first tried it worked and now it's stuck on interacting with portal... seems like interacting is really unreliable
The spot got nerfed? Farmed it for 2h, the droprate got so small. Tried to switch to heroic, did a manual run, still a small droprate.... Is it my luck or the spot got nerfhammered?
I had it yesterday, droprate was fine. Tried normal today, droprate was fine until this point. How are mythics? I guess its just bad luck.