projektt
Active Member
- Joined
- Sep 21, 2010
- Messages
- 1,424
- Reaction score
- 8
Projektt, I appreciate you taking the time to post regarding your experience. Quick reminder: don't modify log files. Hate for you to go to the trouble of posting and data being missing. If they are too large compress Log file as a .ZIP before attaching. This is covered in the FAQ. For this run, it appears the problems began after the point where some party members were resurrected and the tank changed from Paladin.0E3E to DeathKnight.70DE. The problems however don't appear to be related to these events because the issue is that your targets are being reported by HB at this point forward as not being in line of sight. For example:
That debug output indicates that when ShamWOW asks if the target is in line of sight, the response from HB is "No" so it doesn't proceed attacking. You'll notice that some instant casts are still occurring (Unleash Weapon, Flame Shock, etc.) This is occurring in a piece of code normally used while the Shaman is trying to chase or move towards the target (in this case to get into line of sight since HB says you are out of it.) Since the casts are successful then clearly as far as WOW is concerned you are within range and in line of sight, but ShamWOW can only react to the info it is provided which says that you aren't.Code:[8:03:37 PM:975] % Exit COMBAT [target]: Molten Erupter.112C th:68.6%, tdist:28.6 [COLOR=red]tlos:N tlosocd:N[/COLOR] tcombat:Y ttarget:-TANK- taggro:N tpetaggro:N
So... what does this mean for you? I can't debug HonorBuddy and since its providing incorrect data your only option is to close it and restart. You should not have to exit WOW (unless its in turn providing the bad data to HonorBuddy.) Note: Pressing STOP then START does not clear any memory.
I'll look at disabling line of sight checks for LazyRaider usage only, but this needs to be done carefully to make sure it doesn't break ShamWOW for everyone else. Note that I don't see this as a fix since HB may return other incorrect values next time that some hack hasn't been made for. This is the best I'll be able to do for you however.
Thanks and good luck with your Shaman, Bobby53
BOBBY53, thank you so much for the explanation. I exited out of HB and re opened it and it still had that problem during that raid. Next time should I completely exit out of wow AND HB and see if that works? Should it work or will I still have this problem?