Problem - Waiting on spell refresh when swapping spells and AA funkyness.

[virtuoso65]

Version of KissAssist.mac?

11.001

When did your problem start?

Since last patch

Character Role?

1. Assist

What class is having this issue?

1. Shaman

How often does this issue occur?

Always

Can you reproduce the issue?

Yes

So I think I have found another issue for spell swapping.
My shaman has a spell loaded in slot 13, long refresh slot. She un-mems savage growth, to load responsive spirit, casts it, waits for it to refresh before unloading it, loads savage growth, waits for it to refresh, unloads it and loads up talisman of wul, casts it, waits for refresh than reloads savage growth back up.


/edit
I have also noticed my shaman now chain casts the AA Turgur's Swarm, I think this is due to a change in how AA's work in that they cast the highest rank of the spell line you have memorized instead of an AA specific spell. My shaman Casts the AA Turgur's Swarm but the debuff that lands is Turgur's Insects.


/edit2
I tried this but didn't work.

DPS1=Turgur's Swarm|99|debuffall|slow|always|dual|Turgur's Insects

[2019/01/27 11:00:26] [MQ2] ** Debuffing: ==> Turgur's Swarm on >> a slag golem << DebuffTargetID: 28400 Target: 28400 DBOList:
[2019/01/27 11:00:35] [MQ2] ** Debuffing: ==> Turgur's Swarm on >> a slag golem << DebuffTargetID: 28400 Target: 28400 DBOList: |28400
[2019/01/27 11:00:42] [MQ2] ** Debuffing: ==> Turgur's Swarm on >> a slag golem << DebuffTargetID: 28400 Target: 28400 DBOList: |28400
[2019/01/27 11:00:47] [MQ2] ** Debuffing: ==> Turgur's Swarm on >> a slag golem << DebuffTargetID: 28400 Target: 28400 DBOList: |28400
[2019/01/27 11:00:53] [MQ2] ** Debuffing: ==> Turgur's Swarm on >> a slag golem << DebuffTargetID: 28400 Target: 28400 DBOList: |28400

/edit3
Ok this did work, kinda, still cast 2 times in a few fights even when Turgur's Swarm was on the target.

DPS1=Turgur's Swarm|99|debuffall|slow|always|Cond8

Cond8=!${Target.Buff[Turgur's Insects].ID}

 

[ctaylor22]

The Tugur's swarm issue, has to do with the AA's triggering a spell with a different name than the AA itself. We are working on a fix for this at the moment. The condition is the only fix for this at this time.