A Anotherone New Member Joined Aug 24, 2012 Messages 52 Reaction score 0 Sep 25, 2012 #1 Bot just started ignoring this mob, did someone else notice this?
beardi Member Joined Sep 20, 2012 Messages 586 Reaction score 21 Sep 25, 2012 #2 SNO for them is still in the priorities list and I haven't had this issue, try a clean install of DB/Giles see if that sorts it.
SNO for them is still in the priorities list and I haven't had this issue, try a clean install of DB/Giles see if that sorts it.
A Anotherone New Member Joined Aug 24, 2012 Messages 52 Reaction score 0 Sep 25, 2012 #3 what SNO means?
beardi Member Joined Sep 20, 2012 Messages 586 Reaction score 21 Sep 25, 2012 #4 Anotherone said: what SNO means? Click to expand... It's the code that identifies the monster written in GilesTrinity.cs The correct SNO to prioritize Pestilence is still in the priority list, so it shouldn't ignore them at all. Try changing the "Trigger Range for Non-Elite Combat" to 35 if its set at 18 (default) it may not engage them due to that.
Anotherone said: what SNO means? Click to expand... It's the code that identifies the monster written in GilesTrinity.cs The correct SNO to prioritize Pestilence is still in the priority list, so it shouldn't ignore them at all. Try changing the "Trigger Range for Non-Elite Combat" to 35 if its set at 18 (default) it may not engage them due to that.