Amazing, actually eating the food you specify in the settings now, OMG. All my raid food won't get eaten anymore.
G
Nope.. HB 407 is still rather stubborn and tries to be smart by determining whether an item is for "drinking" or "eating-only".
E.g. put item 82451 in both fields (Frybread - simple 300,000/20 health food) and HB still "magically" uses item 81414 (Pearl Milk Tea - health+mana) all the time, effectively wasting my buff food.
I only started using HB yesterday, so I am sure that I have clicked something I probably shouldn't have but GB2 is not fighting back when she pulls npcs enroute for mining.. This only started happening after I updated.. Is anyone else having this issue or know what I can try to resolve it?![]()
repeat mount and dismount still not fix.
Hi,
in order to analyze your issue we need more details in form of a log file.
Please attach a log file. Here is how this works: http://www.thebuddyforum.com/honorb...945-guide-how-attach-your-log.html#post378165
Kind regards
BotOperator
2 years of posting logs with no real results from it, I don't see why my log is important now. The problems I have everyone else has, log in yourself, have a play on timeless Isle, see how bad HB is there, but thats where the action is these days.
The chance my character name has been left in a logfile by a dev or profile writer because of sloppy coding, about 25%, not worth the risk if Blizz are on these forums, another reason I don't post logs.
HB has been bad since 5.4, there is about 10 fundamental flaws, well documented in this forum, how about they get tackled first without adding new stuff, this has always been HB"s problem, add new stuff before fixing old stuff, the errors just keep compounding. There are guys on this forum who have been around longer than me who have stopped writing plugins and profiles because HB is not great at this moment and are sick to death of writing patches to make HB do what it supposed to do, hopefully improvement is on it's way.
The time I spent beta testing was interesting indeed, it seemed like a whole lot of collaboration went on and things were fixed almost immediately, I am not sure what is different now since the beta testing was abandoned because some asshole was leaking betas.
G
2 years of posting logs with no real results from it, I don't see why my log is important now. The problems I have everyone else has, log in yourself, have a play on timeless Isle, see how bad HB is there, but thats where the action is these days.
The chance my character name has been left in a logfile by a dev or profile writer because of sloppy coding, about 25%, not worth the risk if Blizz are on these forums, another reason I don't post logs.
HB has been bad since 5.4, there is about 10 fundamental flaws, well documented in this forum, how about they get tackled first without adding new stuff, this has always been HB"s problem, add new stuff before fixing old stuff, the errors just keep compounding. There are guys on this forum who have been around longer than me who have stopped writing plugins and profiles because HB is not great at this moment and are sick to death of writing patches to make HB do what it supposed to do, hopefully improvement is on it's way.
The time I spent beta testing was interesting indeed, it seemed like a whole lot of collaboration went on and things were fixed almost immediately, I am not sure what is different now since the beta testing was abandoned because some asshole was leaking betas.
G
This is not the reason why beta groups were disbanded. Internal betas were leaked when everyone involved was explicitly told not to share it.leaking betas? wasnt the Beta after a short time spread in the beta thread from the devs? and there is really really nothing special in the "Beta" as it called "Beta". no one will really use it if the chance is high to get caught because its a "Beta". Just People who dont care to lose a Toon or some Bucks.
Ok the Testing Group was abandoned and now the devs have to test and code... looks like they got enough time.
[10:38:25.537 D] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Failed to generate path ---> System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
at dtNavMeshQuery.updateSlicedFindPath(dtNavMeshQuery* , Int32 maxIter)
at Tripper.RecastManaged.Detour.NavMeshQuery.UpdateSlicedFindPath(Int32 maxIter)
at Tripper.Navigation.WowNavigator.FindPath(Vector3 start, Vector3 end)
at Styx.Pathing.MeshNavigator..()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---