Problem - Chain Pull Probs

[ycleptjah]

Hey all,

So I'm having trouble getting my monk to chain pull. I've tried setting the mob hp % at different %s, sometimes he'll chain pull, sometimes he'll completely ignore it. Maybe 1 mob out of 5 he'll actually split off at the designated HP and go find another mob, seems totally random.

Anyone have any ideas for this? Thanks.

 

[( @ )( @ )]

I found chain pull to be more annoying than valuable. They will not group watch, if they chain pull. I set my group watch according to what zone I am in and needs at the time. XP still rolls.

 

[ctaylor22]

The next time you think you puller should pull a mob and doesn't then use the /debugchainpull command the combat routine will start spaming you with information on why it is not pulling the next mob. If you don't care about the puller getting experience for kills, you can edit the macro and search for PullXPCheck and where PullXPCheck is being /declared turn it off by changing it from 1 to 0.

Groupwatch works fine with chainpulling, you only need to have it turned on, on the puller and turned off on all other characters.

 

[ycleptjah]

Hi ctaylor,

I tried your suggestions. I'm getting a lot of error messages in /debugchainpull. Here's one: PULL L: 12270 T: 122 Sub: Chain Pull Failed 3 29020 0 279.23 < 670.00.00 (My Tank's Name) (Ascending Chain of Numbers from 1 - 110, going up with each error)

Sometimes it works perfectly...when it isn't working, that's probably the most common message I get. Any suggestions for this? Thanks a ton.

 

[ctaylor22]

Hi ctaylor,

I tried your suggestions. I'm getting a lot of error messages in /debugchainpull. Here's one: PULL L: 12270 T: 122 Sub: Chain Pull Failed 3 29020 0 279.23 < 670.00.00 (My Tank's Name) (Ascending Chain of Numbers from 1 - 110, going up with each error)

Sometimes it works perfectly...when it isn't working, that's probably the most common message I get. Any suggestions for this? Thanks a ton.

That number that is increasing is important because if that number is above 50, then the puller will NOT pull the next mob, you need to add some entries in your aggro section to decrease and keep your aggro % below 50% or the puller will not leave camp. That debug message is not showing errors it is just spamming the info you need to determine why the puller is doing what they are doing. The only thing you didn't provide is the last number on that debug line. Everything else looked fine and the puller should of went and pulled another mob, but the thing that caused the puller to stay in camp and not pull, was your aggro% was NOT less than 50%. If the puller runs out of camp while having more than 50% aggro, the mob has a tendency of following the puller.

 

[ycleptjah]

That number that is increasing is important because if that number is above 50, then the puller will NOT pull the next mob, you need to add some entries in your aggro section to decrease and keep your aggro % below 50% or the puller will not leave camp. That debug message is not showing errors it is just spamming the info you need to determine why the puller is doing what they are doing. The only thing you didn't provide is the last number on that debug line. Everything else looked fine and the puller should of went and pulled another mob, but the thing that caused the puller to stay in camp and not pull, was your aggro% was NOT less than 50%. If the puller runs out of camp while having more than 50% aggro, the mob has a tendency of following the puller.

Ahhh that makes perfect sense, thank you.

So I've got that problem sorted, now I'm running into a new one...it looks like chain pulling isn't occurring with 1 mob in camp sometimes because 2 mobs are being registered somehow. Chain Pulled Failed 2<2 FALSE , basically the new debug message.

Why isn't it registering as one mob in camp sometimes when there's only one mob in camp?

And again, thanks a lot, I really appreciate the help.

 

[ycleptjah]

Alright new problem...my rogue, who I'm using to chain pull, will randomly stop sometimes and will not continue until I reset the macro. Doesn't matter if I let him sit there for an hour. He hasn't exceeded camp radius or anything like that, he just returns to camp and then completely stops pulling. Any idea how to troubleshoot that?

 

[eqtrader74]

"/debug on" to see what KA is doing when he stops.

If it's spammy and you need to record it, "/plugin mq2log load" & "/mlog on" Logs will be in your mq2 folders. You can share the part where he's stuck on here, though remove toon names.

 

[ycleptjah]

Thanks! Certainly something going on.

Here's the repeating debug message:

[2020/01/31 12:54:29] [MQ2] DEBUG L:6235 T:15923 Sub: MobRadar 30 Enter (CheckForCombat)

[2020/01/31 12:54:29] [MQ2] DEBUG L:6261 T:15923 Sub: MobRadar Leave 0

[2020/01/31 12:54:29] [MQ2] DEBUG L:6235 T:15923 Sub: MobRadar 30 Enter (CheckForCombat)

[2020/01/31 12:54:29] [MQ2] DEBUG L:6261 T:15923 Sub: MobRadar Leave 0

[2020/01/31 12:54:29] [MQ2] DEBUG L:6235 T:15924 Sub: MobRadar 30 Enter (CheckForCombat)

[2020/01/31 12:54:29] [MQ2] DEBUG L:6261 T:15924 Sub: MobRadar Leave 0

[2020/01/31 12:54:29] [MQ2] DEBUG L:6235 T:15924 Sub: MobRadar 30 Enter (CheckForCombat)

Goes on ad nauseam. Any ideas?

 

[ctaylor22]

@ycleptjah Try /debugall the normal /debug won't spew out enough info.

 

[ycleptjah]

Migrated everything to a new comp, manually moved every file I could think of to the new comp and got group set back up...now my puller is ignoring a lot of close mobs, running through them to pull further range mobs and dying often. /debugchainpull comes back as "not a valid command" now. What do you guys think?

 

[ycleptjah]

Zradius is set pretty high too...not idea why he isn't picking up close mobs.

 

[ycleptjah]

Got MQ2Nav loaded as well...but he will just run straight through mobs, pretty odd. Nothing ignored in the zone ini.

 

[ctaylor22]

I use chain pulling as well and have noticed since the last few patches that my puller will go for mobs farther out while leaving closer mobs he has to run past, but after testing, the mobs he did not select either had a longer Nav path, even though they were LOS closer than the selected mob, or there was NO nav path to the closer mob.

 

[ctaylor22]

To fix the /debugchainpull you might want to edit your ini file and change the KissAssistVer=0 and save the ini file and restart kiss to fix the aliases..