Problem - Weave and how it works?

[Wolfborn]

Version of KissAssist.mac?

Kiss 11.009

When did your problem start?

Just noticed it on my mage. Seems to work fine on my Wizards.

Character Role?

1. Assist

What class is having this issue?

1. Magician

How often does this issue occur?

Sometimes

My thoughts are that the "|Weave" tag is there to allow AA to be cast during cooldown.
I have my mage setup with a few Weave slots in the INI.
Watching the spam.. all the Weaves are cast first before any spells are cast.
This pulls aggro from the tank every time.

What am I doing wrong?

She's lvl 107 running full suit of Conflagrant with a few baubles and Gold account.
The INI could be better for sure.
I'm happy with it as she pulls a steady 30 to 40K DPS and never needs to med.
(meaning I'm too lazy to try and tweek it)

[DPS]
DPSOn=2
DPSSkip=10
DPSInterval=8
DPS1=Heart of Flames|99|Me
DPS2=Twincast|98|Once
DPS3=Eradicate Magic|97|Once
DPS4=Remorseless servant|96|Once
DPS5=Chaotic Fire|94
DPS6=Summoned: Icebound Sliver|90|weave
DPS7=Spear of Molten Shieldstone|88
DPS8=Force of Elements|86|Weave
DPS9=Spear of Blistersteel|84
DPS10=Firebound Orb|60|weave
DPS11=NULL
DPS12=NULL
DPS13=NULL
DPS14=NULL
DPS15=NULL
DebuffAllOn=0
DPSSize=15
DPSCOn=0

 

[stvski]

merc tank or player tank....

make sure pet taunt is on
I run mages(maxx AA) all day long hitting 100k+ dps and rarely have issues
Your DPSInterval=8 I run mine at 1 or 2

If your running into aggro problems with "real" tank at 30-40k its not your fault

 

[eqtrader74]

So sliver/force/orb are all firing at engage? Like at 98%? Maybe weave ignores percentages, I didn't know it did that. Did you try DPSOn=1 too? That's another option on how KA reads the DPS entry priority.

For now, roll back your engage percentage in Melee, so the mage starts a little later.

As above, I'd also double check your tank's ini for aggro control. Other than a like pulling with a bow and bard song gets aggro, I rarely have aggro issues unless somebody lands a crazy crit at start. If you're using a pet for aggro, make sure to give it the aggro proc weaps.

 

[Wolfborn]

When I view the spam just after she gets aggro, it always shows that, like you said, all the weaves fire one after the other before any other spells are cast.
The wiz is set up with weaves too and I never see him doing that. Could be that High elves are just smarter than Dark elves...

The tank is solid and can hold aggro no problem with my other two DPS.
Zerker and Wiz. Both deal 100K + regularly. Sometimes I run 3 wiz, all max AA with T2 EoK gear or conflagrant. No problems with aggro.
Also, the tank pulls aggro from the mage within seconds but not before the mob gets a couple of good hits in.

My main concern is.. why are all the weaves being fired at once?

I changed engage level to 95% and adjusted the spells to match.
We'll see how it goes now.

 

[Rooster]

For what it's worth, from memory/my log shows my weave stuff in the past i worked correctly. My DPSInterval=0 , DPSSkip=5 , DPSOn=1. that was old Version 11.001, spells otherwise essentially the same as above

 

[Chibz]

I was having the same problem with mage weaves firing before the HP trigger and spamming continuously. I finally removed force of elements and fire bound orb from my ini. Seemed to happen about the same time that burn was changed. I’m using Kiss 11.01. Weave worked fine before that. When I get back home, I will try enabling again later today, but wondering if there has been any reported fixes?

 

[ctaylor22]

Unless your caster is doing melee, then the Weave routine is only called from the CombatCast routine. To get to the CombatCast routine the mob's HP would have to be below your AssistAt entry in your ini file.

I noticed that there is no check in the CastWeave routine for mobs HP, there is a field being used to hold the value from the entry, but it is never compared to the mobs HP to skip/continue.

You just need to add 1 line.

/if (${DPSat1}>${Spawn[${TarID}].PctHPs}) /continue

Find the line in the code below to see where to include it.

    Sub CastWeave(TarID)
        /declare i int local
        /declare DPSat1 int Local 0
        /declare DPSWeaveDelay timer local 2
        /declare DPSWeaveSpell string local
        /declare DPSWeaveArg3 string local         
        /declare DPSWeaveArg4 string local     
        /for i 1 to ${WeaveArray.Size}
            /varset DPSat1 ${Int[${WeaveArray[${i}].Arg[2,|]}]}
            /varset DPSWeaveSpell ${WeaveArray[${i}].Arg[1,|]}
            /if (${Debug}) /echo \at Cast DPSWeaveSpell:(${DPSWeaveSpell}) at (${DPSat1}%) ${i} \agLine#: ${Macro.CurLine}
            /if (${DPSat1}==0 || !${TarID} || ${Spawn[${TarID}].Type.Equal[corpse]}) /return
            /if (${DPSat1}>${Spawn[${TarID}].PctHPs}) /continue
            /if (!${ConOn} || !${WeaveArray[${i}].Find[|cond]} || ${If[${Cond[${WeaveArray[${i}].Mid[${Math.Calc[${WeaveArray[${i}].Find[|cond]}+5]},3]}]},1,0]}) {
            /if (${Me.AltAbilityReady[${WeaveArray[${i}].Arg[1,|]}]} || ${Me.ItemReady[${WeaveArray[${i}].Arg[1,|]}]} || ${Me.CombatAbilityReady[${WeaveArray[${i}].Arg[1,|]}]} || ${Me.AbilityReady[${WeaveArray[${i}].Arg[1,|]}]}) {
                /call CastWhat "${DPSWeaveSpell}" ${TarID} WeaveStuff 0 0
                /while (${DPSWeaveDelay}) {
                    /doevents
                }
                /if (${Macro.Return.Equal[CAST_SUCCESS]})  {
                    /echo -- Weaving: ${DPSWeaveSpell}
                    /return 1
                }
            }
            }
        /next i
    /return 0

Hope this helps.

 

[Chibz]

Thanks!

 

[Chibz]

@ctaylor22 I believe this fixed it, however, I had to change the > to a <. I will keep testing and update if I learn anything else.

 

[ctaylor22]

Your correct. After looking at the logic it should be <. Good catch..