[00:50:05.228 N] (Singular) (Singular) Pull More: disabled automatically for Context = 'Instances'
[00:49:44.398 N] (Singular) (Singular) Pull More: disabled automatically for Context = 'Instances'
Looks to be hard coded within Singular to disable the Pull More function within an instance. Perhaps someone could look into it or ask Bobby53 if it even would be a smart thing to change. Seeing how certain mechanics work in instances.
Code:
if (SingularSettings.Instance.UsePullMore == PullMoreUsageType.None)
{
allow = false;
Logger.WriteDiagnostic("Pull More: disabled by user configuration (use:{0}, target:{1}, count:{2}",
SingularSettings.Instance.UsePullMore,
SingularSettings.Instance.PullMoreTargetType,
SingularSettings.Instance.PullMoreMobCount
);
}
[B] else if (SingularSettings.Instance.UsePullMore == PullMoreUsageType.Auto && !(SingularRoutine.IsGrindBotActive || SingularRoutine.IsQuestBotActive))
{
allow = false;
BotBase b = SingularRoutine.GetCurrentBotBase();
Logger.WriteDiagnostic("Pull More: disabled because use:{0} and botbase:{1} in use",
SingularSettings.Instance.UsePullMore,
b == null ? "(null)" : b.Name
);
}[/B]
else if (SingularSettings.Instance.PullMoreTargetType == PullMoreTargetType.None || SingularSettings.Instance.PullMoreMobCount <= 1)
{
allow = false;
Logger.WriteDiagnostic("Pull More: disabled by user configuration (use:{0}, target:{1}, count:{2}",
SingularSettings.Instance.UsePullMore,
SingularSettings.Instance.PullMoreTargetType,
SingularSettings.Instance.PullMoreMobCount
);
}
[B] else if (SingularRoutine.CurrentWoWContext != WoWContext.Normal)
{
allow = false;
Logger.WriteDiagnostic("Pull More: disabled automatically for Context = '{0}'", SingularRoutine.CurrentWoWContext);
}[/B]
else if (!SpellManager.HasSpell(needSpell))
{
allow = false;
Logger.WriteDiagnostic("Pull More: disabled for{0} characters until [{1}] is learned", TalentManager.CurrentSpec.ToString().CamelToSpaced(), needSpell);
}
return allow;
}
The first bolded part shows that the AUTO pull more function only works with grind bot. (questbot doesn't seem to support Pull More with either "auto" or "always")
And the second bolded part shows that the pull more function automatically disables itself when singular detects it is running in an instance or BG. It doesn't matter if "always" or "auto" is used.
Unless I am mistaken, because I know jack about this.
Ok, I just tested the following:
Tank in party with 4 others, without queued for or joined an instance. Settings set to "always" and running dungeonbuddy at start-up
[01:24:41.603 N] [Singular] ... in a group as NONE role with 5 of 5 players
[01:24:41.980 N] [Singular] Pull More: will pull up to 9 from mob types=[All] within 35 yds during Combat
Tank in party with 4 others, joined an instance. Settings set to "always" and running dungeonbuddy at start-up
[01:28:05.609 N] (Singular) (Singular) Pull More: disabled automatically for Context = 'Instances'
So I am 51% certain that unless those people got drunk/high and changed the code in SingularRoutine.Behaviors without them remembering, they are trolling, mistaken or just mean people.