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

[Test] Honorbuddy 2.0.0.3059 for WoW 4.0.1.13205 - Auth serverlist updated.

Status
Not open for further replies.
I have one Problem.
Questing is working fine.. He accepts Quests.. but if HB will turn in a Quest, the Questframe get open, close, open, close again and again.
I must manually click on it, to finish the quest.
There are no errors @ debug
 
Willox said:
I have one Problem.
Questing is working fine.. He accepts Quests.. but if HB will turn in a Quest, the Questframe get open, close, open, close again and again.
I must manually click on it, to finish the quest.
There are no errors @ debug
Click to expand...

so you know exactly how to analyze debug logs ? Why do you need us then ?
 
flexkres said:
i did but nesox removed it cause he thought that i was dumb -.-" i aborted due to inifinte error loop below the health...

maybe nesox shouldnt remove logs -.-"

adding it to this post in 10 sec
Click to expand...

CC error - we will have a fix tomorrow.
 
We just want full logs, that way we can fix anything very fast, snippets don't help at all.
 
uhuh, there was one in my first post that "dissapeared" i always add them after i posted cause im used to it, was up about 10 sec after it was posted;P
 
Authenticating..
Could not connect to the authentication server. It may be too busy to process your request. Please wait a few minutes and try again!
Authentication failed.

SESSION LIMIT on http://hb.buddyauth.com
 
flexkres said:
since nesox only insulted me i dont care anymore... anyhow the problem in my log occurs below eat health, and goes into infinite loop till ur above the health where it wants to eat... hope it helps u to fix it for other members...
Click to expand...

I got mad because the wall of text almost killed me didn't bother to read the log.
Sorry if you felt like i insulted you.
 
nesox said:
I got mad because the wall of text almost killed me didn't bother to read the log.
Sorry if you felt like i insulted you.
Click to expand...

Suppose i should have figured by ur little image there^^, stacktrace or gtfo... :P <3
 
flexkres said:
i did but nesox removed it cause he thought that i was dumb -.-" i aborted due to inifinte error loop below the health...

maybe nesox shouldnt remove logs -.-"

adding it to this post in 10 sec
Click to expand...


Look at this log now, some errors have been fixed in the CC. Working on the others.

EDIT: One of the errors is because you don't have food/water
 
Last edited:
My druid isnt attacking anything in PvP mode now. SO sad to watch...lol.
Watching the log, seems to be an error with the CC
 
Last edited:
Same error as before.....

The type initializer for 'Styx.Helpers.CharacterSettings' threw an exception

Then after that it is nothing but continuous crashes with other errors.

Here is the log:

[6:59:38 PM:230] Error - Endscene hook failed: Value cannot be null.
Parameter name: EndSceneProc passed to Executor constructor was invalid.
[6:59:38 PM:264] Attached to WoW with ID 4216
[6:59:38 PM:264] Loading Honorbuddy 2.0.0.3059 settings.
[6:59:47 PM:334] Error - Endscene hook failed: Value cannot be null.
Parameter name: EndSceneProc passed to Executor constructor was invalid.
[6:59:47 PM:369] Attached to WoW with ID 4216
[6:59:47 PM:369] Loading Honorbuddy 2.0.0.3059 settings.
[7:02:45 PM:768] Authenticating..
[7:02:47 PM:267] Authentication successful.
[7:02:47 PM:334] New bot added!: Grind bot
[7:02:47 PM:337] New bot added!: PvP
[7:02:47 PM:338] New bot added!: Mixed
[7:02:47 PM:339] New bot added!: RaF - Combat Assist
[7:02:47 PM:342] New bot added!: Questing - Beta

Can anyone tell me what this might be? Would greatly appreciate it.......

Edit: Sorry for not posting the Log but I had posted it before on page 6 of v2.0.0.0.3013 and didn't think it would be necessary. Posted it now.
 

Attachments

Last edited:
Revs9k01 i assume you didnt read in here that we need full LOGS ...

we need PLEASE a full uploaded log file


However i assume its the DX11 issue, go to your WOW install ans start the wow.exe from there this should work

your shortcut has maybe this -d3d11 added after updating wow
 
Status
Not open for further replies.
Back
Top