Question - Is there any way to prioritize a spell over another in a .ini?

[testtube]

Version of KissAssist.mac?

11.004

When did your problem start?

N/A

Character Role?

1. Assist
2. Tank
3. PetTank
4. PullerPetTank
5. Puller
6. PullerTank
7. Hunter
8. Petassist

What class is having this issue?

1. Bard
2. Beastlord
3. Berserker
4. Cleric
5. Druid
6. Enchanter
7. Magician
8. Monk
9. Necromancer
10. Paladin
11. Ranger
12. Rogue
13. Shadow Knight
14. Shaman
15. Warrior
16. Wizard

How often does this issue occur?

Always

Can you reproduce the issue?

Yes...I can reproduce the issue by just typing /mac kissassist (not to be a smartass)

Let's say if I'm playing a Wizard and that Wizard has both Ethereal Skyfire and Ethereal Icefloe up, for example.

Is there any way to get it to always cast Ethereal Skyfire as a priority above Ethereal Icefloe?

 

[Amarth]

dpson=2, set skyfire higher hp than floe

 

[testtube]

dpson=2, set skyfire higher hp than floe

First of all, what does "DPSOn=2" do differently than "DPSOn=1"?...And secondly, is there a different way to do this than to set Skyfire to a higher casting HP than Icefloe? (And if there isn't, will this make it so Skyfire ALWAYS takes priority over Icefloe, even if the fight lasts 4 hours long?)

 

[Many_Whelps]

you can also force it by putting a condition on Ethereal Icefloe such as:

cond#=!${Me.SpellReady[${Spell[Ethereal Skyfire].RankName}]}

 

[testtube]

Ok thanks. How about if they are both up at the same time though?

 

[Many_Whelps]

First of all, what does "DPSOn=2" do differently than "DPSOn=1"?...And secondly, is there a different way to do this than to set Skyfire to a higher casting HP than Icefloe? (And if there isn't, will this make it so Skyfire ALWAYS takes priority over Icefloe, even if the fight lasts 4 hours long?)

DPSOn=2 fundamentally changes the way the "HP" numbers work. In fact, with DPSOn=2 it's not even based on mob HP, it's a priority ranking number. If spell1 is set to 99 and spell2 is set to 98, spell1 takes priority and KA will try to use it before moving to spell2. This way you don't have to reorder your DPS#'s if, say, you want DPS21 to be cast before DPS5.

From my Magician ini:

DPS1=Force of Elements|90|weave
DPS2=Firebound Orb II|90|weave
DPS3=Heart of Flames|90|weave|cond10
DPS4=Twincast|99|cond6
DPS5=Spear of Molten Arcronite|98
DPS6=Spear of Molten Shieldstone|98|cond8
DPS7=Chaotic Inferno|98|cond4

What this will tell KA to do is to first try to cast Twincast, it's highest priority but has a condition. If we can't cast Twincast, we move to priority 98 spells. Because I use the |weave tag, DPS1, 2 and 3 will be used between GCD refreshes (they're AAs and not locked out like your spell bar is). I set them at a lower priority because I only want them saved for when spells can't be cast.

 

[ctaylor22]

Another difference between DPSOn=1 and DPSOn=2 is:

Note: The DPS Array is sorted using the attack at % of each entry, in descending order.

DPSOn=1 - Cast whatever is ready and don't wait for anything keep looping through the DPS entries and cast it if it is ready. The mob HP% is checked based on the individual DPS entry HP %.
DPSOn=2 - Waits on Global cooldowns between each cast, but does NOT wait on SpellReady. The DPS Entrys HP % is NOT used but the AssistAt entry in the [Melee] section is used, when comparing to the mobs HP %.