im currently writing a free hunter FC based on the lock one i made- however im seeing something that i have never encountered.

 

On every second or third mob the bot will stand there, target selected, in range... and do nothing.  If i hit any spell the client, the bot will spring into life and start fighting the mob with no problems.

 

More often the not the bot will blacklist the mob and turn away, at that point the FC will start , pet will charge in and away it goes.  Is there any way to over-ride the 'check if mob is bugged" and just start the FC rotation?

 

Seen it on both a lvl 56 and lvl 30 hunter.  Fc and logs attached.

 

Thanks

Eeny

 

 

[F] 08:45:33 - [Spell] Cast Aimed Shot (Aimed Shot)
08:45:42 - [Looting] Loot Toxic Horror
[N] 08:45:42 - [Path-Finding] FindPath from 6059.129 ; -1240.89 ; 379.509 ; "None" to 6082.812 ; -1257.756 ; 379.18 ; "None" (Kalimdor)
[N] 08:45:43 - [Path-Finding] Path Count: 2 (29.07626y)
08:45:48 - [Fight] Player Attack Toxic Horror (lvl 54)
[D] 08:45:56 - [Fight] Mob seem bugged
08:45:56 - [Fight] Can't reach Toxic Horror, blacklisting it.
08:45:56 - [Fight] Player Attack Toxic Horror (lvl 54)
[N] 08:45:57 - [Path-Finding] FindPath from 6080.014 ; -1255.763 ; 378.8944 ; "None" to 6082.51 ; -1217.615 ; 369.1263 ; "None" (Kalimdor)
[N] 08:45:57 - [Path-Finding] Path Count: 2 (39.45775y)
[F] 08:46:00 - [Spell] Cast Hunter's Mark (Hunter's Mark)
[F] 08:46:00 - [Spell] Cast Auto Shot (Auto Shot)

 

 

Hunter_by_eeny_2.cs

17 Dec 2017 08H36.log.html

In general settings try to disable option "Calculate interact/combat distance by target size"

3 hours ago, Droidz said:

In general settings try to disable option "Calculate interact/combat distance by target size"

tried this with the same result.  It has to be the FC- tried a different one and i dont get bugged mobs.

Guess il remake it, since i cant figure out whats tripping the bot up with the hunter FC.

You get this problem only when you use this fightclass?

Your code is big to find where is the problem. Do you have try to put  "Range" fix? Try also to add logs to check when WRobot bug.