What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Build 513 - Aweful - REALLY JUST AWEFUL

Status
Not open for further replies.
T

Tankpal0207

New Member
Joined
Feb 9, 2011
Messages
63
Reaction score
0
Attacks dead mobs
Attacks NPCs
Ignores mobs right next to the toon and PULLS mobs that are 20-25 yards away. Hell - if one mob beating on you is good - certainly having 4 or 5 on you must be better.

Moving from point A to point B - what a mess -
-jumps off cliffs and dies
-tries to run up cliffs and gets stuck
-oh - and I love this new feature - when you stop the bot to take control and manually move it to the next location -
the damn thing keeps running - you actually have to shut down the bot to stop it

I'm not including a log because I'm not sure how it would help in these cases - and because I've already seen most of these issues reported elsewhere - except for the pathing mess. However, if one of the devs really thinks it will help - I'll try to grab one.

So it's bad enough I can't really level toon with BGbuddy or Dungeonbuddy - because they're being re-written - or because they act so stupid in BGs you're just BEGGING to be reported. Now I have to sit there and constantly babysit the Questing bot because of the pathing issue.

Adding new features - like the native flying - is great and all - but when you have basic features that still aren't working - or a feature that was working and is now broke (pathing again) - I could really care less about flying in Outlands.

Seems like we're stuck in this 1-step forward, 2-steps back pattern - and it's a little discouraging.

Please excuse me now - my toon just took another flying leap off a cliff in Townlong Steppes and if I don't intervene, it will just sit there for the next hour trying to walk up a vertical rock face.
 
Yes I have definitely noticed the trying to climb vertical mountains and cliffs, the keeps running also, but he doesn't just run forward, he runs backwards WTF? I'm discouraged also, but what can we really do but sit and wait, I used to love this honorbuddy, and for the most part it seems to do the job pretty good, point is the wording pretty good, not Good! before MOP we used to have so many combat routines for almost any class, now were pretty much forced to buy one or use clu or singular
 
Tankpal0207 said:
Attacks dead mobs
Attacks NPCs
Ignores mobs right next to the toon and PULLS mobs that are 20-25 yards away. Hell - if one mob beating on you is good - certainly having 4 or 5 on you must be better.

Moving from point A to point B - what a mess -
-jumps off cliffs and dies
-tries to run up cliffs and gets stuck
-oh - and I love this new feature - when you stop the bot to take control and manually move it to the next location -
the damn thing keeps running - you actually have to shut down the bot to stop it

I'm not including a log because I'm not sure how it would help in these cases - and because I've already seen most of these issues reported elsewhere - except for the pathing mess. However, if one of the devs really thinks it will help - I'll try to grab one.

So it's bad enough I can't really level toon with BGbuddy or Dungeonbuddy - because they're being re-written - or because they act so stupid in BGs you're just BEGGING to be reported. Now I have to sit there and constantly babysit the Questing bot because of the pathing issue.

Adding new features - like the native flying - is great and all - but when you have basic features that still aren't working - or a feature that was working and is now broke (pathing again) - I could really care less about flying in Outlands.

Seems like we're stuck in this 1-step forward, 2-steps back pattern - and it's a little discouraging.

Please excuse me now - my toon just took another flying leap off a cliff in Townlong Steppes and if I don't intervene, it will just sit there for the next hour trying to walk up a vertical rock face.
Click to expand...

:cool:http://www.thebuddyforum.com/honorb...31-reminder-asking-support-reporting-bug.html:cool:
 
Tankpal0207 said:
Attacks dead mobs
Attacks NPCs
Ignores mobs right next to the toon and PULLS mobs that are 20-25 yards away. Hell - if one mob beating on you is good - certainly having 4 or 5 on you must be better.

Moving from point A to point B - what a mess -
-jumps off cliffs and dies
-tries to run up cliffs and gets stuck
-oh - and I love this new feature - when you stop the bot to take control and manually move it to the next location -
the damn thing keeps running - you actually have to shut down the bot to stop it

I'm not including a log because I'm not sure how it would help in these cases - and because I've already seen most of these issues reported elsewhere - except for the pathing mess. However, if one of the devs really thinks it will help - I'll try to grab one.

So it's bad enough I can't really level toon with BGbuddy or Dungeonbuddy - because they're being re-written - or because they act so stupid in BGs you're just BEGGING to be reported. Now I have to sit there and constantly babysit the Questing bot because of the pathing issue.

Adding new features - like the native flying - is great and all - but when you have basic features that still aren't working - or a feature that was working and is now broke (pathing again) - I could really care less about flying in Outlands.

Seems like we're stuck in this 1-step forward, 2-steps back pattern - and it's a little discouraging.

Please excuse me now - my toon just took another flying leap off a cliff in Townlong Steppes and if I don't intervene, it will just sit there for the next hour trying to walk up a vertical rock face.
Click to expand...

Nice being a druid, just pop flight form if bot does this shit.
 
Let's not forget going to harvest right in the middle of a quest, lol. I watched it in Valley of the Four Winds trying to kill a quest target elite, then it will just wander off while fighting to collect ore and herbs, then come back to killing the elite. I was like, "Really? Was the harvest that important?" then I laugh. .513 is like a petulant child that's still learning right from wrong, but I'm glad to see it's being worked on, even if it does go backwards more than forwards sometimes. It's technology. It's going to have its ups and downs.
 
So here's an example:

[07:47:58.416 D] Compiling expression 'HasQuest(29883) && !IsObjectiveComplete(3, 29883)' @ line 1114
[07:47:59.061 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[07:47:59.169 D] Goal: Interacting with Instructor Sharpfin
[07:47:59.282 D] [InteractWith-v249(debug) @line 1115]: Instructor Sharpfin
[07:47:59.290 D] Activity: Moving to interact with "Instructor Sharpfin"
[07:47:59.294 D] [InteractWith-v249(debug) @line 1115]: Instructor Sharpfin
[07:48:07.936 D] Activity: Interacting with - Instructor Sharpfin
[07:48:07.938 D] [InteractWith-v249(debug) @line 1115]: Instructor Sharpfin
[07:48:07.985 D] InteractDebug:575745880
[07:48:08.034 D] Interact Done:575745880
[07:48:08.038 D] [InteractWith-v249(debug) @line 1115]: Instructor Sharpfin
[07:48:14.764 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[07:48:15.436 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedWhile.
[07:48:15.601 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[07:48:15.602 D] [QDBG] Starting behavior [ForcedQuestObjective Objective: [CollectItemObjective ItemID: 73368, Count: 6]].
[07:48:15.603 D] Goal: Goal: Collect Tortoise Flank x 6
[07:48:15.647 D] Changed POI to:Type: Kill, Name: Instructor Sharpfin
[07:48:16.042 D] Dismount to kill in patrol area.
[07:48:16.042 D] Stop and dismount... Reason: Combat
[07:48:16.751 D] Activity: Moving towards Pearly Tortoise
[07:48:21.178 N] [Singular] Current target is not the best target. Switching to Instructor Sharpfin!
[07:48:21.787 D] Activity: Moving towards Instructor Sharpfin
[07:48:33.597 N] Stopping the bot!
[07:48:33.597 D] Stop called!
[07:48:33.597 Q] Bot Stopped! Reason: User pressed the Stop button!
[07:48:33.627 D] Activity: Honorbuddy Stopped
[07:48:34.652 D] System.Threading.ThreadAbortException: Thread was being aborted.
at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Delegate.DynamicInvoke(Object[] args)
at Styx.CommonBot.Targeting.(Delegate , Object[] )
[07:48:34.661 D] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.Targeting.(Delegate , Object[] )
at Styx.CommonBot.Targeting.Pulse()
[07:48:34.670 D] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.Targeting.Pulse()
at Styx.Pulsator.Pulse(PulseFlags flags)
at Styx.CommonBot.TreeRoot.()
at Styx.CommonBot.TreeRoot.()
[07:48:34.672 D] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.TreeRoot.()
[07:48:34.652 D] System.Threading.ThreadAbortException: Thread was being aborted.
at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Delegate.DynamicInvoke(Object[] args)
at Styx.CommonBot.Targeting.(Delegate , Object[] )
[07:48:34.661 D] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.Targeting.(Delegate , Object[] )
at Styx.CommonBot.Targeting.Pulse()
[07:48:34.670 D] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.Targeting.Pulse()
at Styx.Pulsator.Pulse(PulseFlags flags)
at Styx.CommonBot.TreeRoot.()
at Styx.CommonBot.TreeRoot.()
[07:48:34.672 D] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.CommonBot.TreeRoot.()

So my question is- what the hell do you guys have against Instructor Sharpfin? He seems like a decent enough fellow - and here you are trying to kill him.
 
All I see there is a wall of text, and not an uploaded log.

Sharpfin is weak. The hozen are vastly superior.
 
Good thing the bot makes logs, apparently 500 complaints about the same problems isn't helping.
 
guys we are aware of the issues and they should be fixed in the next build, i understand your frustration yea, it sucks that these issues exist, but our developers are working hard to get them all resolved for the next release. so please be patient.


im going to lock this thread now, and if you have a real support issue then please make another thread with a log as an attachment and a detailed description of the issue, and we will help you out.
 
Status
Not open for further replies.
Back
Top