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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[Azyul Project] Dungeon Farming, Gold Farming, Mount Farming, Transmog Farming, and more!

HTML:
Changing current profile to [SK-Heavy]Sra'Vess [$Rev$]
2 compiler errors encountered in profile '[SK-Heavy]Sra'Vess [$Rev$]'
'If' xml element on line number 321 has following errors
	1) The name 'HasAura' does not exist in the current context at offset 0

'If' xml element on line number 324 has following errors
	1) The name 'HasAura' does not exist in the current context at offset 0
HTML:
[DoWhen-v1974(error)] For DoWhenActivity ActivityName(Open_PChests), predicate (() => HasItem(87391)) 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.
[DoWhen-v1974(error)] For DoWhenActivity ActivityName(Open_PChests), predicate (() => HasItem(87391)) 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.
I get this on [Heavy]Sra'Vess.xml

Same problem with

<CustomBehavior File="Hooks\DoWhen" ActivityName="Open_SBloated" UseWhen="HasItem(67495)" AllowUseDuringCombat="true" > <!-- Strange Bloated Stomach -->
<CustomBehavior File="RunCode" Code="Logging.Write(System.Windows.Media.Colors.DeepSkyBlue, &quot;[Azyul]: Opening Strange Bloated Stomach.&quot;);" />
<CustomBehavior File="UseItem" ItemId="67495" NumOfTimes="500" TerminateWhen="!HasItem(67495)" />
</CustomBehavior>

Opening strange bloated stomach blocks the script.
 
When i complete a dung it goes out and back in and it says dung completed means no mobs inside.

What should i do leave running until they respawn or its a bug?
Sounds like a bug to me.
Could you post a log?





HTML:
Changing current profile to [SK-Heavy]Sra'Vess [$Rev$]
2 compiler errors encountered in profile '[SK-Heavy]Sra'Vess [$Rev$]'
'If' xml element on line number 321 has following errors
	1) The name 'HasAura' does not exist in the current context at offset 0

'If' xml element on line number 324 has following errors
	1) The name 'HasAura' does not exist in the current context at offset 0
HTML:
[DoWhen-v1974(error)] For DoWhenActivity ActivityName(Open_PChests), predicate (() => HasItem(87391)) 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.
[DoWhen-v1974(error)] For DoWhenActivity ActivityName(Open_PChests), predicate (() => HasItem(87391)) 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.
I get this on [Heavy]Sra'Vess.xml
Make sure your bot is running the latest version.
If it is, reinstall it.





Yes, exactly. Character is stuck at the main pedestal that Laj stands on.

Edit: Not always, sometimes bot is stuck at the edge of the biggest platform in Laj's room.

Edit2: Added two screenshots with exact locations where the bot gets stuck.
Hrrm,
Stuff like this is unpredictable and pretty hard to avoid.

A coordinate could be added that pulls Laj away from the pedistals after combat starts -
But during his encounter I believe he teleports onto the pedistal unless you kill him fast enough.

This has been a bug for a while, I haven't really been able to look into a reliable solution.
Perhaps blackspotting the pedistals would work - if the bot actually "uses" the blackspots. 9/10 it doesn't seem to. Lol





Having same problem as pateutz. New clean HB installed.
The only thing I could suggest is to report it to the support thread.




Same problem with

<CustomBehavior File="Hooks\DoWhen" ActivityName="Open_SBloated" UseWhen="HasItem(67495)" AllowUseDuringCombat="true" > <!-- Strange Bloated Stomach -->
<CustomBehavior File="RunCode" Code="Logging.Write(System.Windows.Media.Colors.DeepSkyBlue, "[Azyul]: Opening Strange Bloated Stomach.");" />
<CustomBehavior File="UseItem" ItemId="67495" NumOfTimes="500" TerminateWhen="!HasItem(67495)" />
</CustomBehavior>

Opening strange bloated stomach blocks the script.
Which of the two errors are you getting?
 
Sounds like a bug to me.
Could you post a log?






Make sure your bot is running the latest version.
If it is, reinstall it.






Hrrm,
Stuff like this is unpredictable and pretty hard to avoid.

A coordinate could be added that pulls Laj away from the pedistals after combat starts -
But during his encounter I believe he teleports onto the pedistal unless you kill him fast enough.

This has been a bug for a while, I haven't really been able to look into a reliable solution.
Perhaps blackspotting the pedistals would work - if the bot actually "uses" the blackspots. 9/10 it doesn't seem to. Lol






The only thing I could suggest is to report it to the support thread.





Which of the two errors are you getting?

[DoWhen-v1974(error)] For DoWhenActivity ActivityName(CustomDeathHook), predicate (() => Me.IsGhost) 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.
 
It says this when i load your profile

2 compiler errors encountered in profile 'Deathcharger's Reins Farm [$Rev$]'
'If' xml element on line number 335 has following errors
1) Operator '!' cannot be applied to operand of type 'Styx.WoWClass' at offset 0

2) Operator '!' cannot be applied to operand of type 'Styx.WoWClass' at offset 0
 
Ashes of alar doesn't work? I can't load it on my HB

EDIT: It works with an older version of HB.
EDIT2: Why does the bot wait 8min infront of the last boss?
 
Last edited:
Please help me. Profile Halls of Lightning

Between profiles heavy and lite no not some differences
in Lite pulls as much exactly as mobs and heavy.
 
Changing current profile to [SK-Lite]Shao-Tien Moguls [$Rev: 1132 $]
2 compiler errors encountered in profile '[SK-Lite]Shao-Tien Moguls [$Rev: 1132 $]'
'If' xml element on line number 283 has following errors
1) The name 'HasAura' does not exist in the current context at offset 0

'If' xml element on line number 286 has following errors
1) The name 'HasAura' does not exist in the current context at offset 0



this is the errors i am getting
 
It says this when i load your profile

2 compiler errors encountered in profile 'Deathcharger's Reins Farm [$Rev$]'
'If' xml element on line number 335 has following errors
1) Operator '!' cannot be applied to operand of type 'Styx.WoWClass' at offset 0

2) Operator '!' cannot be applied to operand of type 'Styx.WoWClass' at offset 0
Bot issue.
It should be fixed with the latest versions.





Ashes of alar doesn't work? I can't load it on my HB

EDIT: It works with an older version of HB.
EDIT2: Why does the bot wait 8min infront of the last boss?
Once the timer starts, does the boss not aggro?
It waits 8 minutes for his *RP* event.
 
reinstalled and same thing
'Same thing' being that you're getting both of the errors you reported?
The DoWhen error is common, it shouldn't be breaking anything unless something changed in the latest updates.





[DoWhen-v1974(error)] For DoWhenActivity ActivityName(CustomDeathHook), predicate (() => Me.IsGhost) 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.
This issue is common, however its never been known to actually stop the bot - or cause it to break.

Is it stopping the bot?





https://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-support/208147-hb-update-crashes.html
Here a thread in support section by pateutz. Admin said there is profile problem not hb.
In most situations it is a profile issue, but I know how DoWhen behaves more-so than the admins do.
This error will pop up even if the predicate is false.





Please help me. Profile Halls of Lightning

Between profiles heavy and lite no not some differences
in Lite pulls as much exactly as mobs and heavy.
If this is happening, then your bot is ignoring the <EnableBehavior Name="Combat" /> lines for whatever reason.
The only thing I could suggest is you put wait timers between each pull, and have them terminate when combat isn't detected.

If you don't know how to do this tell me and I'll make an edit for you.





Changing current profile to [SK-Lite]Shao-Tien Moguls [$Rev: 1132 $]
2 compiler errors encountered in profile '[SK-Lite]Shao-Tien Moguls [$Rev: 1132 $]'
'If' xml element on line number 283 has following errors
1) The name 'HasAura' does not exist in the current context at offset 0

'If' xml element on line number 286 has following errors
1) The name 'HasAura' does not exist in the current context at offset 0



this is the errors i am getting
Can you post a full log?
This isn't typically a profile error - but and error in the bot that was supposidely fixed.
 
im getting the [DoWhen-v1974(error)] aswell and it doesnt stop the honorbuddy just stop in ghost form next to the angel not moving at all.
it happens a lot since the last 2 updates from honorbuddy.
 
there is no log as it isnt letting the bot start sorry that is all it is giving
A log should be generated regardless.
If you bot is crashing on startup, then that's a bot issue.

Delete the "Settings" file in your Honorbuddy folder.
Note: this will remove your key from the login screen, so make sure you have it saved somewhere.
 
im getting the [DoWhen-v1974(error)] aswell and it doesnt stop the honorbuddy just stop in ghost form next to the angel not moving at all.
it happens a lot since the last 2 updates from honorbuddy.
Could you post a log of it?
I have no information on this error at all.
 
Back
Top