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

Honorbuddy Beta Builds

Status
Not open for further replies.
Can't seem to DL the beta build. Servers just getting hammered or what? I get "Oops! Google Chrome could not connect to updates.buddyauth.com" constantly.
 
Still getting behavior error.

Also getting a crash when loading a new profile.


delete your behavior folder and open a fresh zip of honorbuddy and take the quest behaviors out and move it into your folder.
 
Can someone post newest beta to a decent filehost? honorbuddy server just not doing it for me tonight
 
I Have this error

Honorbuddy v2.5.6948.210 started.
This is a BETA build of Honorbuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums.
This build may have bugs, and new features which may not be fully tested. Use at your own risk!
Logging in...
Attached to WoW with ID 2728
New bot added!: ArchaeologyBuddy
New bot added!: BGBuddy
New bot added!: DungeonBuddy
New bot added!: Gatherbuddy2
New bot added!: Grind Bot
New bot added!: Questing
New bot added!: Mixed Mode
New bot added!: PartyBot
New bot added!: [BETA] GrindBuddy
New bot added!: Combat Bot
New bot added!: Raid Bot
Honorbuddy v2.5.6948.210 started!
Character is a level 90 Draenei Shaman
Current zone is Valley of the Four Winds
RecentProfiles:
Please wait a few seconds while Honorbuddy initializes.
ItemForAura - Questhelper - Version 2.0 Loaded.
[Singular] Starting Singular v3.0.0.2223
[Singular] Installation: integrity verified for 3.0.0.2223
[Singular] Determining talent spec.
[Singular] TalentManager - looks like a ShamanElemental
[Singular] Current spec is Shaman Elemental
[Singular] Building method list
[Singular] GCD check fix spell set to: Lightning Shield
[Singular] Initialization complete!
Initialization complete.
Starting the bot!
Currently Using BotBase : DungeonBuddy
Se produjo una excepci?n en el inicializador de tipo de 'Bots.DungeonBuddy.DungeonManager'.
Bot Stopped! Reason: Se produjo una excepci?n en el inicializador de tipo de 'Bots.DungeonBuddy.DungeonManager'.
 
Something is wrong i get this error:
Fehler ? Anschli?en der Beendigungsscene fehlgeschlagen: Could not setup Executor; unknown func passed to hook: EB F9 55 8B EC 83 E4 F8 83 EC
An WoW mit der ID 9500 angeheftet

Restarted WoW 2 times... now working -.-
 
Last edited:
Endscene Hook failed, happens if either a diffrent tool (graphic card driver on notebooks, Xfire , Teamspeak, Fraps and the like, tldr, tools that draw overlay menus ingame) mess with directx, or it is a dx version that isn't properly handled yet.
Switching between DX11 and DX9 often does the trick, if it is still an issue, we for sure need more details on OS, hardware, drivers and directx version and any possible software that might interfere with dx.
 
Im having a problem with the beta and the release of doing a few quest then just stoping at a "Way-point" and sitting till it logs out. I have done fresh installs cache wipes in wow and in HB and the progam data file folder and still no go same thing. Its always a different spot it stops at the bot keeps running but the char just won't move and you try to manualy move him he runs back to the spot he was at here is the log.
 

Attachments

Im having a problem with the beta and the release of doing a few quest then just stoping at a "Way-point" and sitting till it logs out. I have done fresh installs cache wipes in wow and in HB and the progam data file folder and still no go same thing. Its always a different spot it stops at the bot keeps running but the char just won't move and you try to manualy move him he runs back to the spot he was at here is the log.

looks like a cc issue. Use Singular
 
Actually i fixed it i noticed my "Mesh folder" wasn't in my HB folder so i re-routed it to my HB folder and its been working fine ever since.
Is it work?I have the same problem,seems the bot cant check if the char had arrived the point where he want the cahr to go,it happens when the questbot use the "run to x,y,z".
 
Have some really nice updates that speed up questing in 215. I am sure it's an easy fix. Could you clarify the update to Autoequip. Removing weights? Does that mean it will use some kind of other way of rating items?
 
How is it possible to release a beta without checking for questing ? I understand that bugs in some minor areas can occur but questing being totaly unable to work really?? I am having the same problems as the above.
 
Getting this error. Fresh folder install not an update.

Currently Using BotBase : Questing
[Compiler Error]: c:\Users\temp\Desktop\Beta\Quest Behaviors\Misc\SafeQuestTurnin.cs(159,31) : error CS1729: 'Bots.Quest.QuestOrder.ForcedQuestTurnIn' does not contain a constructor that takes 4 arguments
Errors in quest behaviors!
 
Status
Not open for further replies.
Back
Top