Question - Ranger ini

[Berkz]

Version of KissAssist.mac?

12.002

When did your problem start?

10/30

Character Role?

1. Assist

What class is having this issue?

1. Ranger

How often does this issue occur?

Always

Can you reproduce the issue?

Yes - start KA and engage mob. Ranger does not back up to use ranged

I updated my KA ini so I can have my ranger step back to a good distance to use range, but he stays in the middle of the fight just spamming "too close to use a ranged weapon". Do you see why this is happening? I can't figure it out

[General]
KissAssistVer=12.002
Role=Assist
CampRadius=100
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=1
ChaseDistance=25
MedOn=1
MedStart=20
MedStop=100
MedCombat=0
LootOn=0
RezAcceptOn=1|90
AcceptInvitesOn=1
GroupWatchOn=0
GroupWatchCheck=FALSE
CorpseRecoveryOn=0
EQBCOn=0
DanNetOn=1
DanNetDelay=20
IRCOn=0
CampfireOn=0
CharInfo=Ranger|109|GOLD
DPSMeter=0
ScatterOn=0
LOSBeforeCombat=1
XTSlot=1
[SpellS]
Gem1=Cloudfont
Gem2=Summer's Cyclone
Gem3=Wildfire Ash
Gem4=Wildfire Boon
Gem5=Desperate Dousing
Gem6=Blisterbeetle Swarm
Gem7=Shimmering Veil
Gem8=Swarm of Glistenwings
Gem9=Heartsplit
Gem10=Focused Arrowrain
Gem11=Kromtus
Gem12=Anticipated Shots
Gem13=NULL
MiscGem=8
MiscGemLW=0
MiscGemRemem=1
LoadSpellSet=0
SpellSetName=KissAssist
CastingInterruptOn=1
CheckStuckGem=1
[Buffs]
BuffsOn=1
BuffsSize=14
Buffs1=Shimmering Veil|Me
Buffs2=Strength of the Copsestalker|Melee
Buffs3=Protection of the Forest
Buffs4=Nettlespear Coat
Buffs5=Roaring Weapons
Buffs6=Bellow of the Predator|Melee
Buffs7=Energized by the Hunt
Buffs8=Flaming Arrows
Buffs9=Anticipated Shots
Buffs10=NULL
Buffs11=Cloak of Nettlespears|MA
Buffs12=Shield of Nettlespears|MA
RebuffOn=1
CheckBuffsTimer=3
Buffs13=NULL
Buffs14=NULL
PowerSource=NULL
[Melee]
AssistAt=98
MeleeOn=0
FaceMobOn=1
MeleeDistance=75
StickHow=off
AutoFireOn=0
UseMQ2Melee=0
DismountDurningFights=0
MeleeTwistOn=0
TargetSwitchingOn=0
PetTauntOverride=0
[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSize=3
GoMSpell1=NULL
GoMSpell2=NULL
GoMSpell3=NULL
[GMail]
GMailHelp=Events currently support - Dead,Drag,GM,Level,Named,Leftgroup,Tells
GMailOn=0
GMailSize=5
GMail1=NULL
GMail2=NULL
GMail3=NULL
GMail4=NULL
GMail5=NULL
[AE]
AEOn=0
AESize=10
AERadius=50
AE1=NULL
AE2=NULL
AE3=NULL
AE4=NULL
AE5=NULL
AE6=NULL
AE7=NULL
AE8=NULL
AE9=NULL
AE10=NULL
[DPS]
DPSOn=2
DPSSize=21
DPSSkip=5
DPSInterval=1
DPS1=command:/autofire|100|Once
DPS2=Anticipated Shots|99|Cond7
DPS3=Elemental Arrow|99
DPS4=Focused Arrowrain|99|Cond7
DPS5=Summer's Cyclone|99|Mash|Cond7
DPS6=Wildfire Boon|99|Cond7
DPS7=Wildfire Ash|99|Cond7
DPS9=Pack Hunt|99|cond1
DPS10=NULL
DPS11=Outrider's Accuracy|99|cond1
DPS12=Group Guardian of the Forest|99
DPS13=Auspice of the Hunter|99
DPS14=NULL
DPS15=NULL
DPS16=Entrap|99|cond4
DPS17=Heartsplit|99|cond5
DPS18=Guardian of the Forest|99
DPS19=${InvSlot[Chest].Item.Name}|80|weave|cond1
DPS20=command:/stick moveback 35 uw|100|cond8
DPS21=Spire of the Pathfinders|99|cond1
DPS22=Swarm of Glistenwings|99|cond1
DPS23=Blisterbeetle Swarm|99|cond1
DebuffAllOn=0
DPS8=NULL
[Aggro]
AggroOn=1
AggroSize=1
Aggro1=Jolting Cut Kicks|30|
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
HealInterval=0
AutoRezOn=0
HealsSize=4
Heals1=Cloudfont|40
Heals2=Protection of the Spirit Wolf|50
Heals3=Outrider's Evasion|50|Me
Heals4=Desperate Dousing|40
XTarHeal=0
XTarHealList=Xtar slots here Example: 5|6|7
HealGroupPetsOn=0
RezMeLast=0
[Cures]
CuresOn=1
CuresSize=5
Cures1=Kromtus Balm
Cures2=NULL
Cures3=NULL
Cures4=NULL
Cures5=NULL
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=92
[Burn]
BurnAllNamed=0
UseTribute=0
BurnSize=1
Burn1=Empowered Blades
[Pull]
PullWith=Melee
PullMeleeStick=0
MaxRadius=350
MaxZRange=50
UseWayPointZ=0
PullWait=5
PullRadiusToUse=90
PullRoleToggle=0
ChainPull=0
ChainPullHP=90
PullPause=30|2
PullLevel=0|0
PullArcWidth=0
PullOnReturn=0
[PullAdvanced]
PullLocsOn=0
[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=1
AFKGMAction=1
AFKPCRadius=500
CampOnDeath=0
ClickBacktoCamp=0
[KConditions]
ConOn=1
CondSize=7
Cond1=${Target.Named}
Cond2=${Target.ID} && ${Target.BuffsPopulated} && !${Target.Buff[Dreadbeetle Swarm].ID} && ${Range.Between[50,99:${Target.PctHPs}]}
Cond3=${Me.PctAggro} > 40
Cond4=!${Target.Snared.ID}
Cond5=${Target.Body.Name.Equal[Humanoid]} || ${Target.Body.Name.Equal[Animal]}
Cond6=${Me.Endurance} < 11
Cond7=${Me.PctMana}>50 || ${Target.Named}
Cond8=${Target.Distance} < 30 || ${Target.Distance} > 50

 

[Rare Spawn]

I am not a KA user yet, so just an outsider looking in, sharing my observations, trying to help.




[General]
ChaseDistance=25

[Melee]
MeleeOn=0 <-----
MeleeDistance=75 <---- find the sweet spot where you are in range of bow AND also the kick discipline attacks.
AutoFireOn=0 <-----

[DPS]
DPS1=command:/autofire|100|Once <----- If melee is off, what distance does it use? Maybe its the chase distance?

 

[Berkz]

Thank you Rare. She is not having an issue with autofire, just not stepping back as stated in Cond 8, which relates to DPS20 where I am instructing to move to distance 35.

MeleeDistance=75 <---- find the sweet spot where you are in range of bow AND also the kick discipline attacks.

Yeah, that is what I am trying to accomplish with distance 35. I have melee off as I read on another post it wouldn't conflict with having it autofire as stated in DPS1, and should replace the autofireon.

I am thinking that the post where I read all this may be on an older KA version and some things may have changed, which is why it doesn't work.

Hopefully one of the KA brains can see this and give me some guidance.

 

[Rare Spawn]

Thank you Rare. She is not having an issue with autofire, just not stepping back as stated in Cond 8, which relates to DPS20 where I am instructing to move to distance 35.


Yeah, that is what I am trying to accomplish with distance 35. I have melee off as I read on another post it wouldn't conflict with having it autofire as stated in DPS1, and should replace the autofireon.

I am thinking that the post where I read all this may be on an older KA version and some things may have changed, which is why it doesn't work.

Hopefully one of the KA brains can see this and give me some guidance.

Ahh I see what you got cooking with the conditions and stick commands. Thanks for the KA education.

 

[naamloseeen]

I use almost identical setup with my ranger and he moves correctly 95% of the time.

There are two difference with my setup:

I don't have the stickhow=none in my melee section. Here is mine:

[Melee]
AssistAt=99
MeleeOn=0
FaceMobOn=1
MeleeDistance=75
StickHow=moveback 35 uw
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=0
PetTauntOverride=0

I also put the stick command as the first entry in my dps section:

[DPS]
DPSOn=2
DPSSize=20
DPSSkip=20
DPSInterval=2
DPS1=command:/stick moveback 35 uw|99|cond1
DPS2=command:/autofire on|99

And my condition:

[KConditions]
ConOn=1
CondSize=5
Cond1=${Target.Distance} < 30 || ${Target.Distance} > 50

I wonder if there's a conflict with stick=none and the stick command in the dps section? I don't really know, but this works for me most of the time.

On occasion, he'll still end up not moving, so it's not perfect.

 

[ctaylor22]

There is actually a solution to this issue. Take a look: Ranger control

 

[Berkz]

There is actually a solution to this issue. Take a look: Ranger control

I like that! I am gonna try it tomorrow because half of it is going over my head right now LOL

 

[ctaylor22]

Yea. It is a little on the advanced side. But it opens a door to many possibilities.

 

[Berkz]

Yea. It is a little on the advanced side. But it opens a door to many possibilities.

So I started using this method as you suggested, and it works nicely most of the time. Once in a while, however, the ranger decides to run in the opposite direction of the mob being pulled. Usually, I catch her in the act and stop her. Some other times though, like today, she ran into a group of mobs and was dead in a nanosecond flat (ranger gate anyone?)

Not sure if this is due to something in the code or something in the ini. Have you seen this behavior before?