For Xp / rift globes you can change: Plugins/Trinity/Cache/Weighting.cs (Trinity v.24 ... Line ~1234)
Code:
case TrinityObjectType.ProgressionGlobe:
{
//Ignore because we are blocked by objects or mobs.
if (IsNavBlocked(cacheObject))
{
cacheObject.WeightInfo += string.Format("Ignoring {0} - Nav Blocked.",
cacheObject.InternalName);
break;
}
//Ignore because we are TownPortaling
if (TownRun.IsTryingToTownPortal())
{
cacheObject.WeightInfo += string.Format("Ignoring {0} - Town Portal.",
cacheObject.InternalName);
break;
}
if (cacheObject.Distance <= [COLOR="#FF0000"]150[/COLOR]f)
{
cacheObject.WeightInfo += string.Format("Maxxing {0} - Progression Globe.",
cacheObject.InternalName);
cacheObject.Weight += MaxWeight;
break;
}
cacheObject.Weight += ObjectDistanceFormula(cacheObject) +
LastTargetFormula(cacheObject) +
EliteMonsterNearFormula(cacheObject, elites) +
AoENearFormula(cacheObject) +
AoEInPathFormula(cacheObject);
break;
}
Default is 40 (which is way too low for speedy builds). This fix was posted by ridz89 in another thread. Havent noticed my bot miss any globes since making this change.
The running off mid fight isnt related to the crusader CR, its a trinity issue that is being looked into.