What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Bugged] Honorbuddy 1.9.6.3

New release is constantly crashing on my system. I'm running 1.9.6.3, default CC's, no plugins. Seems to be the same as other user reports. I've tried rebooting, re-downloading, re-installing .NET, nothing has worked so far. Questing bugs out on mobs, doesn't dismount or fight back, tons of POI switching and refuses to harvest. Runs up to nodes, stands there, times out and moves on. Logs attached
 

Attachments

Last edited:
New release is constantly crashing on my system. I'm running 1.9.6.3, default CC's, no plugins. Seems to be the same as other user reports. I've tried rebooting, re-downloading, re-installing .NET, nothing has worked so far. Questing bugs out on mobs, doesn't dismount or fight back, tons of POI switching and refuses to harvest. Runs up to nodes, stands there, times out and moves on. Logs attached

mine doing the same
 

Attachments

grinding with a stock cc, no plugins and all looting (herbs/skinning/mines/chests) turned off works ok
 
Crashes

Ok. I've crashed three times. All three times were in three different instances. All three times I crashed exactly 3 seconds after hitting water.

This one is from Spider Heroic Instance in Passage of Lost Fiends, Azjol-Nerub, when you drop down hole in water. It crashes WoW with a Memory Access Violation.

Also spams TONS of this crap to log before WoW Crashes.

http://www.pastie.org/private/1zm1t3vktnel4jovbbgra

The 9999,9999,9999 makes me think it may be click to move crashing in water with instance buddy. I know it doesn't use the navigator in water. Anyways heres my crash log as well.
 

Attachments

grinding with a stock cc, no plugins and all looting (herbs/skinning/mines/chests) turned off works ok

Ya know that's great Mezz0 but isn't the point of the plugins to work...? LOL
 
Ya know that's great Mezz0 but isn't the point of the plugins to work...? LOL
you're nitpicking :)

Nah, you're absolutely right, mate. Just saying that if you switch everything off, it will run..
it's not ideal, but for those who are only leveling it will work... I can bare to lose the leather and drops until the crew makes a new release.
 
I'm still getting this error:
Code:
System.Threading.ThreadAbortException: Thread was being aborted.
   at BlueMagic.Memory.Write[T](UInt32 address, T value)
   at Styx.Helpers.AllocatedMemory.Write[T](String allocatedName, T value)
   at Styx.WoWInternals.WoWMovement.(ClickToMoveType clickToMoveType, UInt64 guid, WoWPoint clickPos, Single facing)
   at Styx.WoWInternals.WoWMovement.ClickToMove(WoWPoint point)
   at Styx.Logic.Pathing.Interop.LocalPlayerMover.MoveTowards(Vector3 point)
   at Tripper.Navigation.PathFollowing.TripperNav.()
   at Tripper.Navigation.PathFollowing.TripperNav.()
   at Tripper.Navigation.PathFollowing.TripperNav.MoveAlongPath()
   at Tripper.Navigation.PathFollowing.TripperNav.MoveTowards(Vector3 point)
   at Styx.Logic.Pathing.Navigator.MoveTo(WoWPoint destination)
   at CommonBehaviors.Actions.NavigationAction.Run(Object context)
   at CommonBehaviors.Actions.ActionMoveToPoi.Run(Object context)
   at TreeSharp.Action.RunAction(Object context)
   at TreeSharp.Action..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.Decorator..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at QuestBot.Actions.PerformQuestObjectiveOrdered..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.Decorator..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at TreeSharp.Composite.Tick(Object context)
   at Styx.Logic.BehaviorTree.TreeRoot.()

That's not really a bug, that exception is raised whenever you Abort a thread happens evry time you press Stop

I know this is relatively minor but is anyone else experiencing the START button not changing state to STOP when you start a profile up?

edit: apparently it is a common problem. (read deeper)

Download it again
 
works really well without looting with mephiles 3.1..
thanks.. ! :>
 
OMFG you fixed the auth for 1.9.6.0 finaly, the botting can continue! Thanks guys
 
Still Getting Auth Error.
Re downloaded Mulitple Times.
Code:
Authenticating..
Authentication failed.
 
Hmm, my bot is still running, but the addon that manages lua errors is trapping multiple hax.lua errors :(
(Can blizzard see those ??)
 
Oops Whats going on?

Please help. I'm getting multi errors. this profile was running fine before I installed the new 1.9.6.3
 

Attachments

it dosent attack( just running aside)

too much loot failure

too much skinning failure

much crash

------------------

**Death Grip**
#Opener was successfull!#
**Death Coil**
**Icy Touch**
**Plague Strike**
**Blood Strike**
**Death Coil**
LOOT_CLOSED wait timed out!
Looting failed. Blacklisting it!
#Killing Gundrak Raptor Distance : 20 yards.#
#Within range of target for Death Grip#
#Casting Opener : Death Grip#
**Death Grip**
#Opener was successfull!#
**Icy Touch**
**Plague Strike**
**Blood Strike**
**Death Coil**
**Scourge Strike**
LOOT_CLOSED wait timed out!
Looting failed. Blacklisting it!
**Horn of Winter**
#Killing Gundrak Raptor Distance : 18 yards.#
#Opener(s) is on Cooldown. Moving to within 3 yards of current target for melee attack#
#Combat Stance Enabled#
**Death Coil**
**Icy Touch**
**Plague Strike**
**Blood Strike**
**Death Coil**
LOOT_CLOSED wait timed out!
Looting failed. Blacklisting it!
 
Last edited:
Back
Top