Problem - Need help on ChainPull

[Qnome]

Version of KissAssist.mac?

12.002

When did your problem start?

2022/Nov/23, 14:30 (GMT+8)

Character Role?

1. Puller

What class is having this issue?

1. Bard

How often does this issue occur?

Always

Can you reproduce the issue?

Yes, set ChainPull=1 and run /mac KissAssist.

Greetings,

I can't make ChainPull work, my bard(Toon1|Puller) won't pull next mob until current one is dead, need some help on settings.

1. I read related posts between Y2017/2018, so I set MeleeOn=0, UseMQ2Melee=0, ChainPull=1, ChainPullHP=60, and watched Toon1|Puller aggro never go over 20%.

KissAssist_Toon1.ini
[General]
KissAssistVer=12.002
TwistOn=1
TwistMed=8 7
TwistWhat=8 7 6 5
Role=Puller
CampRadius=30
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=0
ChaseDistance=25
MedOn=1
MedStart=10
MedStop=90
MedCombat=0
SitToMed=1
LootOn=0
RezAcceptOn=1|90
AcceptInvitesOn=1
GroupWatchOn=1
GroupWatchCheck=FALSE
CorpseRecoveryOn=1
EQBCOn=0
DanNetOn=1
DanNetDelay=20
IRCOn=0
CampfireOn=1
CharInfo=Bard|65
DPSMeter=0
ScatterOn=0
LOSBeforeCombat=0
XTSlot=0
DefaultUI=TRUE

[Melee]
MeleeTwistOn=1
MeleeTwistWhat=1 2 5 6 7
AssistAt=99
MeleeOn=0
FaceMobOn=2
MeleeDistance=75
StickHow=snaproll
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=0
PetTauntOverride=0

[Pull]
PullWith=Sonic Disturbance
PullMeleeStick=0
MaxRadius=400
MaxZRange=200
UseWayPointZ=0
PullWait=5
PullRadiusToUse=100
PullRoleToggle=0
ChainPull=1
ChainPullHP=60
PullPause=2
PullLevel=50|68
PullArcWidth=360
PullTwistOn=0
PullOnReturn=1

2. I read Wiki Manual, so load up default UI trying to debug, but MQ echo <DebugChainP Off> either I do /debug ChainP 1 or /debug ChainP 0

 

[Sic]

Please repost your image without character names

 

[Qnome]

Please repost your image without character names

Hi Sic, MA = TankMerc name, so I didn't hide it, it's done now.

 

[ctaylor22]

try using /debug ChainP on and /debug ChainP off. I think there is an issue with using 0 or 1.

 

[Qnome]

try using /debug ChainP on and /debug ChainP off. I think there is an issue with using 0 or 1.

Greetings @ctaylor22 , thank you for the info.

1. Yes, /debug chainp on/off works, 0 or 1 not.


2. So I test with my SK + TankMerc with /debug chainp on, SK pure pull ( Role=Puller, ChainPull=1, ChainPullHP=50, MeleeOn=0, DPSOn=0, UI=Default )
SK still pull next mob when current one is dead, with no debug message shown.

3. I read Wiki Manual about Chain Pull Debug, which is beyond my current knowledge, so I'll skip /ChainPull function for now.

 

[ctaylor22]

I am working on fixing the 0/1 not working. After turning on ChainP you will get messages as the Puller starts checking for the next mob to pull. You will also see a message "Checking for Close Range Mobs" when the puller is trying to find the next mob to pull. The puller will start checking when there is 1 mob left in camp and the current mobs HP gets below ChainPullHP.

 

[Qnome]

Hi @ctaylor22 ,

Finally got some debug messages, Zulsharn=TankMerc
I understand Failed 2, current mob HP not < /ChainPullHP=50 yet.
but no idea on numbers in Failed 3.

 

[ctaylor22]

I would set the ChainPullHP closer to 90. According to the above Chain Pull Failed 3 message you have 51% of the mobs aggro. You have to have less than 50% or the puller will not run off and grab the next mob. Try setting up some aggro section entries to get the pullers aggro down. I use to use FD with a condition, so my puller would FD when aggro was above 50% and the mobs HP was less than ChainPullHP.

 

[Qnome]

Hi @ctaylor22 ,

1. Revised ChainPullHP=90, what's the meaning of PullChecknavPullToTNotMyMerc ?


2. And I am curious on [add #### into ignore pull list], I do set PullLevel=50|70, but mobs around puller are all 50+.

 

[ctaylor22]

PullToTNotMyMerc is when the mob you are pulling is validated and is validated for the mobs Target being a Mercenary and the Mercenary is NOT a member of your group. That check is so you don't attack a mob that some other group has aggroed. The Added #### to ignore Pull List if a list of mobs that you try and pull, that for some reason or another when validated, as a valid target to pull/attack fails the test. like a wondering mob that wonders out of range before the puller can get to the mob, or a mob that gets aggroed by another group before the puller is able to pull the mob.