qjlforever
New Member
- Joined
- Sep 6, 2014
- Messages
- 5
- Reaction score
- 0
The tol'vir have knew problem.Last night I died twice(i am 550 warrior) and it just stay outside of instance without rez.
Do you have a log of this?The tol'vir have knew problem.Last night I died twice(i am 550 warrior) and it just stay outside of instance without rez.
The attachments are invalid. : /View attachment 142682View attachment 142683
This is where i get stuck sometimes with lite pull in lost city.
Fixed in the latest SVN update. r.1010
Lol, happens all the time.
The only thing that makes it *fun* is the fact that there's up to 23 variations of a single profile.
Gundrak for example. All the different pull densities, *Extra* versions, Randomizer version - etc.
I've talked with HighVoltz and we determined an issue that was brought up by the latest bot update.
Could you try running it with an older version of the bot?
I appreciate you removing all the 'extra' stuff in the log, but there's a lot of technical information in the log that I need to see such as your DX-API.
I need a full unmodified log to know what's going on.
Yarp, thanks!View attachment 142734
see it now?
Which profile?Mine will not vendor anything. It just keeps running instances and farming while I have a full inventory and doesn't loot anything at that point. How do I fix that?
Make sure you copied over the Quest Behaviors from the SVN/ZIP to your Honorbuddy Quest Behavior folder.hello. im trying to run Karazan endless trash and i keep getting this message on honerbuddy?
can not load profile!
name can not begin with '<' character,
hexadecimal value 0x3c. line 675, position 2.
...wtf?
and b4 you ask me to post a log itsnot even giving me one so idk im stumped..
Check the Solution Center under 'Common Questions.'Chance to banned with farm northend dungeongs with 2 pjs FULL PVP 500+?
The error is expected in some scenarios.[22:05:50.425 D] [DoWhen-v1659(debug)] WaitTimer behavior complete.
[22:05:50.484 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[22:05:50.504 D] [DoWhen-v1659(debug)] Behavior completed in 5s
[22:05:50.757 N] [(error)] For DoWhenActivity CustomMountHook, predicate ((Me.CurrentTarget == null || Me.CurrentTarget.IsDead) && !Me.Combat && !Me.Mounted && !Me.IsIndoors && Me.IsInInstance && !ObjectManager.GetObjectsOfType<WoWUnit>().Any(u => u.Lootable && u.Distance <= 40)) was not reset by execution.
This is a profile problem, and can result in erratic Honorbuddy behavior.
The predicate must return to 'false' after the action has been successfully executed.
View attachment 142799
The above error is being returned in the "Lost City of the Tol'vir" profile.
I don't see any immediate bot-stopping errors.
[22:14:28.396 N] [InteractWith-v1684(warning)] Unable to apply event filter for COMBAT_LOG_EVENT_UNFILTERED
Which profile?
Make sure you copied over the Quest Behaviors from the SVN/ZIP to your Honorbuddy Quest Behavior folder.
Check the Solution Center under 'Common Questions.'
The error is expected in some scenarios.
It shouldn't be preventing the bot from working though - unless your character gets stuck in a location were the mount isn't mountable.
I don't see any immediate bot-stopping errors.
The errors posted in the other reply (above this one) is expected, and this error is expected:
PHP:[22:14:28.396 N] [InteractWith-v1684(warning)] Unable to apply event filter for COMBAT_LOG_EVENT_UNFILTERED
Then it's most-likely an issue in your bot.It is not vendoring on any dungeon profile I run. So far gun drak, pit of saron, shattered halls, ramparts, botanica.
Glad to see they're working out for you! xDJust wanted to say, thanks for the farming profile Azyul! Been farming some Icecrown worldmobs with a 85 pala for a few days now. Great extra gold on the side!
Could you post your log?Hello,
Just downloaded this pack and run it on a 565 retri pala in tol vir.
It dies inside because it keeps targetting dead targets.
I am new to honorbuddy and this kind of profile, is there anything i am doing wrong?
[08:15:21.595 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[08:15:21.881 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
[08:15:22.954 Q] Bot stopping! Reason: User pressed the stop button