Tamahawk
New Member
- Joined
- Aug 2, 2012
- Messages
- 108
- Reaction score
- 6
What's the problem that you're having?: Bot doesn't actually seem to be able to forget an evade bugged mob and eventually dies
Windows version?: Win 7 64bit
What bot are you having problems with? (Grind, Quest, BGBuddy etc): Questing + Fpsware Paladin(0.1.2)
What profile are you running?: [Fly][A - Quest] LK 68-80 [Kick] updated daily by SVN
Location: Grizzly Hills, Forest's Edge Post
[11:23:57 AM:405] Loading Northrend_37_26
[11:23:57 AM:688] Loading Northrend_37_25
[11:23:58 AM:022] Loading Northrend_38_26
[11:23:58 AM:276] Loading Northrend_36_26
[11:28:44 AM:085] Unloading tiles!
[11:28:44 AM:093] Loading Northrend_37_26
I just watched my toon die fighting an "Evade Bugged" mob. Despite saying it would blacklist it and move on, it re-selected the same mob. This happens all the time. The bot doesn't seem capable of "just walking away" from a mob, especially an evade bugged one. What lead me to post this question is that this time it was combined with some sort of FPSware error, I think. See the log at 11:21:38 through 11:22:09. The whole log is of course attached but here are those specific lines:
[11:21:38 AM:955] My target is Evade bugged, blacking Silverbrook Hunter
[11:21:39 AM:031] Bad pull target blacklisting and finding another target.
[11:21:39 AM:844] New combat target Silverbrook Hunter, resetting combat timer. <= In fact, it stayed with the same target as I watched.
[11:22:09 AM:858] System.NullReferenceException: Object reference not set to an instance of an object.
at Hera.Fpsware.LOSCheck.Run(Object context) in c:\Users\WPS3\Desktop\Testing\CustomClasses\Fpsware Paladin\Class Specific\Behaviours\Common.cs:line 391
That said, the reason for this post is what seems to be an FPSware error? As it happened in the middle of the Evade Bugged combat, I thought I'd post this message to see what any of you think. My toon has since moved on but I hope this can be helpful in getting these toons to actually forget about attacking the mobs buried in the ground and other similar f'ed up places.
Here is the complete log: View attachment 51423
Windows version?: Win 7 64bit
What bot are you having problems with? (Grind, Quest, BGBuddy etc): Questing + Fpsware Paladin(0.1.2)
What profile are you running?: [Fly][A - Quest] LK 68-80 [Kick] updated daily by SVN
Location: Grizzly Hills, Forest's Edge Post
[11:23:57 AM:405] Loading Northrend_37_26
[11:23:57 AM:688] Loading Northrend_37_25
[11:23:58 AM:022] Loading Northrend_38_26
[11:23:58 AM:276] Loading Northrend_36_26
[11:28:44 AM:085] Unloading tiles!
[11:28:44 AM:093] Loading Northrend_37_26
I just watched my toon die fighting an "Evade Bugged" mob. Despite saying it would blacklist it and move on, it re-selected the same mob. This happens all the time. The bot doesn't seem capable of "just walking away" from a mob, especially an evade bugged one. What lead me to post this question is that this time it was combined with some sort of FPSware error, I think. See the log at 11:21:38 through 11:22:09. The whole log is of course attached but here are those specific lines:
[11:21:38 AM:955] My target is Evade bugged, blacking Silverbrook Hunter
[11:21:39 AM:031] Bad pull target blacklisting and finding another target.
[11:21:39 AM:844] New combat target Silverbrook Hunter, resetting combat timer. <= In fact, it stayed with the same target as I watched.
[11:22:09 AM:858] System.NullReferenceException: Object reference not set to an instance of an object.
at Hera.Fpsware.LOSCheck.Run(Object context) in c:\Users\WPS3\Desktop\Testing\CustomClasses\Fpsware Paladin\Class Specific\Behaviours\Common.cs:line 391
That said, the reason for this post is what seems to be an FPSware error? As it happened in the middle of the Evade Bugged combat, I thought I'd post this message to see what any of you think. My toon has since moved on but I hope this can be helpful in getting these toons to actually forget about attacking the mobs buried in the ground and other similar f'ed up places.
Here is the complete log: View attachment 51423
