Joker76
Member
- Joined
- Feb 8, 2010
- Messages
- 835
Sorry man, but the log file is incomplete. The startup info is missing (version, settings, etc.) and the entire log only contains 5 seconds worth of activity. It should show the HonorBuddy version you are using, the options that are set, and the profile you are using.
Not moving is usually due to one of these things:
1. No profile loaded.
2. Profile loaded doesn't have info for your level character. Since profiles have character level range requirements, your character could be too high or too low for the profile.
3. Navigation was still calculating the best route. While this occurs there is no message in the log file. The status bar will say Moving to Hotspot
4. Navigation couldn't determine a path, so your char would stand still forever. There should be a log file message for this one if that was the case.
My guess on theinfo you provided and the short time represented in the log is #3, the Navigation engine was still calculating the best route from your current location to the first Hotspot in the profile. On my system which is average to slightly below average, I have seen it take as long as 23 seconds on initial startup to calculate the path. That is unusual and was due to me being in the back of Orgrimmar and calculating a path to spot a few zones away. It did however calculate the best route and begin moving, but initially it felt like it wasn't doing anything and there was a problem. This amount of time for route calculation has only occurred for me at startup.
If you still have the issue after waiting longer and can't determine the cause, you'll want to follow the steps I described to create a complete log file for around 3 to 5 minutes and reply with that. This doesn't sound like a CC issue, but to be able to help you further I'll need the log info.
I realize it may take a little while for the bot to get going. The log I attached was for 3-5 minutes, the problem is it just stands there so there's nothing to log. The window shows "Activity: Resting" but he's at full mana and HP.
I have a profile loaded, and it's within my level range.
I got it working for a little while using NB 1.923 ... not really sure how though. It works for a little while, then it stops and stands there. If I restart HB, it works for a little bit again then repeats. Then, I got this message in the window. Full log below.
HB EXCEPTION in ShamanBuffs(): System.Threading.ThreadAbortException: Thread was being aborted. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4241, offset:262 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4290, offset:15 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 3284, offset:18 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 3289, offset:129 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 3288, offset:13
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at Styx.Helpers.Logging.WriteDebug(String format, Object[] args)
at ShamWOW.ShamWOW.Dlog(String msg, Object[] args) in c:\Users\JoKer\Desktop\HB1.923\CustomClasses\Shaman.cs:line 309
at ShamWOW.ShamWOW.GetBestWeaponEnchants(String& enchantMainhand, String& enchantOffhand) in c:\Users\JoKer\Desktop\HB1.923\CustomClasses\Shaman.cs:line 597
at ShamWOW.ShamWOW.ShamanBuffs(Boolean atRest) in c:\Users\JoKer\Desktop\HB1.923\CustomClasses\Shaman.cs:line 1072
>>> REPORT ERROR TO CC DEVELOPER WITH LOG
LOADED: ShamWOW v4.0.4
Your Level 75 Tauren Enhancement Shaman Build is:
Eleme/Enhan/Resto 14/51/0
WARNING: You have 1 UNSPENT Talent Points and you are gimping your Shaman. Please distribute all your talent points!
Max Pull Ranged: 30
HB Pull Distance: 30
Activity: Loading AB profiles.
Activity: Resting
Attachments
Last edited: