Update extensions TrackMobLogic to exclude Captured Beasts

[amarketkindaguy]

Noticed while implementing some beast catching logic that when the beast is captured ("killed" by our standards but netted) that the bot will stand around waiting for the mob to disappear because of track mob task in extensions. Might I suggest updating Extensions TrackMobLogic.cs on line 62 to something like this, or an alternative if there is a better means for doing so:

            if (monsterObj == null || monsterObj.IsDead || monsterObj.HasBestiaryCapturedAura || monsterObj.HasBestiaryDisappearingAura)

This can also be done from the combat routine on targeting inclusion, though it seems more appropriate in my opinion to have it in the default libraries, plus for some reason I was causing a nullreference exception with it in my CR, but probably in error as others have mentioned that they don't see any issues by implementing it in the CR.

 

[pushedx]

This is planned soon as those properties were just added to help avoid issues when people start capturing beasts.