Problem - Kiss not casting 101+ dps spells

[vickvinegar]

Just wondering what's causing this / how to fix.

thanks!

 

[geEQ]

Are you spelling them correctly in kissassist ini you updated? And did you load them on the spell bar?

 

[Maskoi]

please /kisscheck
report back

gratz on 101

 

[vickvinegar]

I guess more specifically since /kisscheck is reporting no problems. My mage will cast the 105 rampage pet (remorseless servant), but not bolt/spear of molten shieldstone (new fire nukes). Shaman will cast sluggishness (upgrade to fatigue), but not talisman of the leopard.

Kissassist reports that it is casting them, but shows Casting ____ as AA (or whatever, with /debug on) and never casts anything.

 

[Maskoi]

Not sure what kind of weirdness this is. I can't test anything because I don't have the new expansions yet. i don't know if its an eq thing or a mq2 thing

 

[vickvinegar]

Anything I can do to help you debug it?

 

[Maskoi]

Unfortunately no. We are getting the new expansion so i can look it at least but it may a week or so. Sorry for the delay.

 

[TreeHuginDruid]

I can confirm .. there are issues casting lvl 101 and greater spells. I'll have the spell defined in dps.. and it wont cast... but the same spell ( exact copy and paste ) works in the BURN section on a named. Looking into it... but it may either be a EQ or MQ2 thing....

 

[vickvinegar]

Awesome, good to know that I'm not crazy. I can also confirm that 101+ spells are working everywhere except in the DPS section.

 

[TreeHuginDruid]

Interesting issue has been observed.... may be the root cause of this issue as well.

New-caster-focus-AA

It appears that for any spell that has a new focus line associated with them.. that spells work find BEFORE puschasing the aa focus for that spell line... but FAIL to cast once the aa focus is purchased.

I'm investigating.

 

[vickvinegar]

Yep. Pretty sure these issues are the same. We can close this one and focus the discussion in the other thread.

 

[TreeHuginDruid]

Hmmm.. trying to look up info if anyway to return the TYPE of aa something is.. as in [General/Archtype/Class/Focus], if there is.. this can be resolved VERY easily with a simple check against aa type.... and conditional coding based upon that.


UPDATE:

Looks like you CAN return the AA type.

/echo ${Me.AltAbility[Banestrike].Type} returns value of 4.. because it is a special aa.. and Special aa is category 4.

General=1
Archtype=2
Class=3
Special=4
Focus=5

So... its a simple fix to resolve this... working on it now... posting asap.

- - - Updated - - -

FIXED will no longer attempt to cast [FOCUS] aa for 101+ spells instead of the actual spell itself.

Macro updated for download link.