disasteroid
New member
- Joined
- May 18, 2015
- RedCents
- 35¢
I've got a bard pulling for my group who, every once in a while after tagging the mob, stops running back to camp. After watching the script run for a bit I believe I've narrowed down the offending code to that below on line 4078:
Which is returning true because AggroTargetIDhas been populated by the code on line 504. I'm getting the message on almost every pull, and what happens is the puller (RIP bard) gets eaten. Order of events:
1. Looking for close range mobs
2. Pulling -> mob (tosses a bellow at it)
3. "Looks like mobs in camp aborting pull."
4. Puller dies because it doesn't move back to camp/tank.
My puller's camp radius has been set between 20 and 40, with the same results. The tank is at 50. I've tried toggling the puller role on and off, same results. I added this snippet to line 4083 at the end of the conditional:
but it doesn't really fix the problem, but helps maybe 1/3 of the time . It's the fix I need but not the one you all deserve so I thought I'd report here for the code overlords to take a look at. Any advice to keep this poor sucker alive?
Rich (BB code):
/if ((${AggroTargetID} && !${ChainPull}) || (${Me.XTarget[${XTSlot2}].ID} && ${ChainPull}) && ${Math.Distance[${CampYLoc},${CampXLoc}]} < ${CampRadius}) {Which is returning true because AggroTargetIDhas been populated by the code on line 504. I'm getting the message on almost every pull, and what happens is the puller (RIP bard) gets eaten. Order of events:
1. Looking for close range mobs
2. Pulling -> mob (tosses a bellow at it)
3. "Looks like mobs in camp aborting pull."
4. Puller dies because it doesn't move back to camp/tank.
My puller's camp radius has been set between 20 and 40, with the same results. The tank is at 50. I've tried toggling the puller role on and off, same results. I added this snippet to line 4083 at the end of the conditional:
Rich (BB code):
/moveto loc ${CampXLoc} ${CampYLoc} ${CampZLoc}
