FelisMalum
Well-known member
- Commits
- 4
It seems to be only an issue with ToB zones but often when I have dopulls=true it will start spamming NoTarget even if there are mobs around to pull. No clue why. Noticed it for some time now.
-
Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
Problem - ToB Pulling
- Thread starter FelisMalum
- Start date
FelisMalum
Well-known member
- Commits
- 4
Sweet I like updates. Admittedly I finally got around to installing 6.01. Noticed the buffing while dopulls=true is improved. Still doesnt rebuff if theres stuff around to pull but at least will do it if they run out.
Also noticed there seems to be a 50 rang swap in melee messages. if rng<=50 the event msg is "Your target is too far away#*#", Sub Event_MobProb runs and the toon moves in. If rng>50 the event msg is "Your target is out of range#*#", which isnt a MobProb event. Adding it causes the sub to run but since the toon isnt in combat or atk hasnt activated /if (!${Melee.Combat} && !${Me.Combat}) /return evaluates to true and the toon never moves in. Just commented the /if for now as im sure it will cause some issues w ranged melee which I rarely use.
Also noticed there seems to be a 50 rang swap in melee messages. if rng<=50 the event msg is "Your target is too far away#*#", Sub Event_MobProb runs and the toon moves in. If rng>50 the event msg is "Your target is out of range#*#", which isnt a MobProb event. Adding it causes the sub to run but since the toon isnt in combat or atk hasnt activated /if (!${Melee.Combat} && !${Me.Combat}) /return evaluates to true and the toon never moves in. Just commented the /if for now as im sure it will cause some issues w ranged melee which I rarely use.
FelisMalum
Well-known member
- Commits
- 4
Fixed the problem, big surprise it was a Z-axis issue. ${NearestSpawn[${a},npc].ID} was picking up mobs on different floor. ToB is allot of stacked zones is why the issue. We havent gotten many of those in quite some time. Since it was an invalid target /if (${NearestSpawn[${a},npc].ID}==${ADMobList[${b}]}) would never evaluate to true, ${ADMobMax} would get reached in the loop since too many were on different floors and the pull would fail. Was an easy patch, corrected with:
Code:
/for a 1 to ${ADMobMax}
/if (${NearestSpawn[${a},npc radius ${Radius} zradius ${ZRadius}].ID}) {
/for b 1 to ${ADMobMax}
/if (${ADMobList[${b}]}) {
/if (${NearestSpawn[${a},npc radius ${Radius} zradius ${ZRadius}].ID}==${ADMobList[${b}]}) {
/varset tTargetID ${ADMobList[${b}]}
/goto :tGotTarget
}
}
/next b
}