Is there a way to add an Xtarget check to the Kissassist puller? My puller frequently just runs up to the target, and then runs back to camp with no aggro and nothing on xtarget. Then he just stands there waiting for the mob to come to the camp but of course it will never come because it wasn't aggroed.
-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
Question - Puller Xtarget
- Thread starter Jetanroth
- Start date
mikeraylittle
Member
- Joined
- May 4, 2020
- RedCents
- 110¢
Quite frankly the puller software sucks. My puller keeps running right past mobs to get other mobs then training the entire group. One would think it would calculate distance to the mob but apparently it does not. Useless.
@mikeraylittle are you using kiss 12? I have not noticed that, maybe a mob spawns on the way to the target, or the two mobs are close together.
@Jetanroth I have noticed this when my pulling ability is not available. Like if I am using a bow and arrow, and I do not have any arrows.
Other than that I have never had a problem with my puller using kiss12.
@Jetanroth I have noticed this when my pulling ability is not available. Like if I am using a bow and arrow, and I do not have any arrows.
Other than that I have never had a problem with my puller using kiss12.
mikeraylittle
Member
- Joined
- May 4, 2020
- RedCents
- 110¢
I'll check the version but I would assume it is the latest as I only started using it a month ago. No the mob didn't spawn. When he took off I assumed the mob he ran past was the one he was going after. Sure the mobs are close, every expansion since HoT the mobs have been close, I think it was to nerf necros (no room to kite anymore), but the two or three times I'm thinking of the closest mob was easily single pulled but he ran past him. I know this because later when I manually pulled using the ranger it was not an issue.
He is melee pulling as I have not the experience with the software yet do anything but the default. He is a ranger with endless quiver so he would not run out of arrows, just adding because I have had the same issue as Jetanroth. Also, for some reason he will pull two or three then say he is waiting for respawns though there are clearly mobs in range.
Bottom line is I'm spending far too much time atm chasing corpse than playing. After posting this tonight I went back on and played the ranger manually and things worked out well. Got two of the merc quest in GD done in about an hour for my emerging box group. I would like to have the opportunity to run the grp in full auto at some point though just to say I did.
mikeraylittle
Member
- Joined
- May 4, 2020
- RedCents
- 110¢
What settings should I be looking at? I'm looking at the KissAssist_info.ini and there just isn't a lot in there.
If my tank happens to get to far away and not returning to rest of the group after a kill, my puller will start spamming 'waiting for respawn'. If I manually return him to rest of the group, the puller will set off grabbing mobs to camp again. Usually do a new '/camphere' when that happens
And the 'running right past mobs to get other mobs' I also get that, sometimes and sometimes not. Z axis and other stuff probably what messes things up.
And the 'running right past mobs to get other mobs' I also get that, sometimes and sometimes not. Z axis and other stuff probably what messes things up.
I have noticed when I first start pulling a camp there is an issue, but after you have cleared the area, and wait and start pulling again everything works fine. From what I have been able to determine, is if a spawn is up and exists when you load into the zone, there is something off about the spawn table, but once you kill everything in the area the new spawns track fine. I don't know what the problem is, but I have spent significant time trying to figure out this issue and it is not the macro. After pulling for a while and you start running past mobs you think you should be pulling, then check and see what you have on your pull ignore list(s).
mikeraylittle
Member
- Joined
- May 4, 2020
- RedCents
- 110¢
I swear I posted this the other day but apparently did not update/post it or something. I currently am in EW ToV and my puller simply pulls the three in front of the grp then stops saying it's waiting for response. Mobs in very close proximity that I believe are WELL inside the range. Below is my pull section. I am getting better at this but this issue makes auto group fairly useless. I'm sure there is a simple explanation. Any issue you can assist with would be appreciated.
[Pull]
PullWith=Ice Burrower Swarm
PullMeleeStick=0
MaxRadius=350
MaxZRange=50
UseWayPointZ=0
PullWait=5
PullRadiusToUse=150
PullRoleToggle=0
ChainPull=1
ChainPullHP=90
ChainPullPause=30|2
PullPause=30|2
PullLevel=0|0
PullArcWidth=0
Two things I see:
MaxRadius is the distance you want your puller to pull from camp.
PullRadiusToUse: The percentage, of the items range you want to use when determining when to stop and pull a mob. Basically you can use this to determine how close you want to get to mobs when pulling. (range: 0-100)
I know the second one seems kind of silly, I don't know why I would only want to use 75% of my bows range.
This is my Pull setup:
[Pull]
PullWith=Elegant Defiant Bow|Summoned: Arrow of Marr
PullMeleeStick=0
MaxRadius=600
MaxZRange=350
UseWayPointZ=0
PullWait=5
PullRadiusToUse=99
PullRoleToggle=0
ChainPull=0
ChainPullHP=90
ChainPullPause=30|2
PullPause=30|2
PullLevel=50|80
PullArcWidth=0
MaxRadius is the distance you want your puller to pull from camp.
PullRadiusToUse: The percentage, of the items range you want to use when determining when to stop and pull a mob. Basically you can use this to determine how close you want to get to mobs when pulling. (range: 0-100)
I know the second one seems kind of silly, I don't know why I would only want to use 75% of my bows range.
This is my Pull setup:
[Pull]
PullWith=Elegant Defiant Bow|Summoned: Arrow of Marr
PullMeleeStick=0
MaxRadius=600
MaxZRange=350
UseWayPointZ=0
PullWait=5
PullRadiusToUse=99
PullRoleToggle=0
ChainPull=0
ChainPullHP=90
ChainPullPause=30|2
PullPause=30|2
PullLevel=50|80
PullArcWidth=0
Last edited:
mikeraylittle
Member
- Joined
- May 4, 2020
- RedCents
- 110¢
Thanks, not completely satisfied with what I have now but using your guidance I am MUCH closer.
This can be a problem too. 50 is not very far at all. So if a mob is right beside your camp but Up the top of a hill - you wont pull it.
If you are in GD which is very Up and Down....I would set this to 500.
You can change some of these settings as your playing too.
Try typing these as you are about to go pull.
/maxZrange=500
/maxradius=600
You will see a confirmation echo in the mq2 window to let you know it has been changed.
mikeraylittle
Member
- Joined
- May 4, 2020
- RedCents
- 110¢
I had actually changed those settings and did see quite a bit of difference. I had Maxradius set to 600 oddly enough and had to set it back to 350. Puller was trying to pull tarznak's in the cave but would not navigate into the cave. Thank you for your response though as it seems I can make those changes "in game" rather than using Notepad+
This page almost explains each entry in the KissAssist .ini.
www.redguides.com
Guide - - KissAssist Instructions & Settings Info
See something out of date? Level 2 users can edit this wikipost, so give us a hand! KissAssist requires plugins and features for use: MQ2Cast, MQ2Exchange, MQ2Melee, MQ2MoveUtils, MQ2Rez, MQ2Twist, and MQ2Gmail, Extended Target Window and ninjadvloot.inc file. * All plugins and files are...
www.redguides.com