Question - What's the point of sorting the dps section by hp ?

[eqholic]

What's the point of sorting the dps section by hp ?
Wouldn't it be much simpler to treat it like a multikey on steroids and just try to apply the first dps action that fullfils all conditions (recasttime, gcd, mobhp <= hp, usercond) on each iteration of the mainloop ? Then users could prioritize by ordering the dpssection and no need for weave. Do I miss something ?

 

[surfdog21]

Ironically mobs only last about 20 seconds give or take when Im grinding EoK trash, so the hp cast timers go out the window in my crews. Probably the timers are meant more for longer fights.

 

[TreeHuginDruid]

What's the point of sorting the dps section by hp ?
Wouldn't it be much simpler to treat it like a multikey on steroids and just try to apply the first dps action that fullfils all conditions (recasttime, gcd, mobhp <= hp, usercond) on each iteration of the mainloop ? Then users could prioritize by ordering the dpssection and no need for weave. Do I miss something ?

Think of things from the non-uber ... lower level players.... who DON'Tuse conditionals .. perspective.

They want to cast certain spells at certain points in the mobs life % point.

If they don't know about or cant figure out conditional logic.... then saying I want to cast snare on the mob when he is close to 50% hp.. it a great logical way for them to control when they pop off the spell ... because they are mana conscious ... and don't have a XXXk points of mana to blow.

It is the primary and most basic part of logic on how and when to do something detrimental to a mob... and has always been that way since its conception.

Granted ..now with conditional logic... it may be a non factor for those users using conditions... as they can base the order and logic of when they cast/do stuff on higher / alternate reasoning / separate hierarchy methods....

But that is no reason to change what works....

 

[eqholic]

What I tried to say has nothing to do with the new conditionals, but with my conviction that the internal work KA does with sorting is unnecessary and might even make writing ini files harder for the users. I will try to make it more clear once I have more time.

 

[ctaylor22]

Kissassist sorts the various arrays so you don't have to. This allows for the user to add entries as they wish and to make changes of the order(HP%) the spells/entries are checked. It also makes more since when reading through the array to check if the mobs HP passes the test for casting the spell. Since mobs HP starts at 100 and goes down. The logical thing to do is to be able to check the spells in the same order, that way the logic will cast the first available spell through the iteration. If you had 25 entries and lets say entry 25 was your highest level HP, lets say 95. If the array was NOT sorted, then the code would have to read through all 25 elements before finding an entry to cast. When it should of only of had to search the first entry. Yes it will still loop through the rest of the entries, but not until after casting that first entry.

Now why would we care about that when it comes to weaves. Well we try and cast weaves when the spell gems are in globalcooldown. So why we are waiting, for the spell gems to become ready, we try and kickoff as many weaves as possible.

When the weave routine is called we read through all the entries and try and cast every weave entry in the DPS array. We also do a secondary check after trying to cast everything in the DPS Array. If the weave routine was NOT called while looping through the DPS array, then it is called before leaving the CombatCast routine. Same goes for the Mash routine.