Problem - Clouburst Thunderbolt

[aspire2008]

So apparently the EQ developers were to lazy, no shock there, and there are 2 versions of Cloudburst Thunderbolt, level 97 and level 107, both named exactly the same.

Kissassist seems to load the 2nd one in a random spell gem slot (not sure if its random or why its defaulting to gem 5 to load it, because my MiscGem=10
what its set too) , which means the spell that I had in that slot gem5 as a DPS spell gets unmem'd for the lower level version of Cloudburst Thunderbolt.

I'm sure there is a way around this by writing a DPS condition for spellgem slot check to check for the spell id, just not sure how to write it.

 

[Rooster]

delete the old from spell book work?

 

[aspire2008]

delete the old from spell book work?

Good idea, I just tried it, either I'm retarded or I have no clue why, I thought you delete spells by right clicking by highlighting the spell till it flashes in the spellbook, then hitting DELETE on the keyboard. That's not working. How do you remove spells from the Spellbook, I swear I thought that was the method, but doesn't seem to work for me.


EDIT: Googled it: Only vendor sold spells are deletable , and recent expansion vendor bought spells are not deletable

So I'm still stuck, need some way to not get the lower version spell to load.

 

[Rooster]

Interesting... can't recall the last time i deleted a spell. Let alone how i did it.

That sucks =\.

I wonder if you could re-order them in the spell book that would make the new spell first and used?

 

[aspire2008]

Interesting... can't recall the last time i deleted a spell. Let alone how i did it. That sucks =\. I wonder if you could re-order them in the spell book that would make the new spell first and used?

You delete spells like I described above. The game is just not letting you delete any vendor bought spells in recent expansions it seems. I was able to delete a Level 1-50 spell, but not anything newer.

I doubt reordering will work, still gonna load both I think, because I think its loading during the global cooldown spell timer since its thinking the one thats loaded already is not ready to cast, and due to the GCD it detects whichever one it thinks is first to be ready to cast, to cast it, so its casting both the 107 and 97 version depending on latecy/computer lag.

I tried doing a force with a condition

DPS36=CloudburstThunderbot|97
DPSCond36=${Target.ID} && ${Target.PctHPs} > 1 && ${Me.Gem[2].ID}=56794

, the level 107 version is in gem2, seemed rather redundant to add that. That condition didn't work.

Only option I can see now is if there is some way for KA to recognize DPS spells by numbers ID instead of written strings. So I could just do DPS36=56974 instead of DPS36=CloudburstThunderbot



I'm surprised noone else has reported this issue since the expansion has been out for over a month. I can't be the only one that has both versions of the spell in the spell book. I would have reported it sooner, but yesterday was the first time I went to RoS to play in it, so went and bought spells too.

 

[Rooster]

Might of found a work around. If you find the Sub CastWhat and on line 2264 use find "/if (${Me.Book[${castWhat}]} && !${Me.Gem[${castWhat}]} && ${ReadyToCast}==0) {

and change ${Me.Book[${castWhat}]} to ${Me.Book[${castWhat}]}<xxx where xxx is the slot number in the spell book. So you can just move the old spell to the back of the book. and make sure your < is less than where ever your spells go up to for now and some future proofing.

I can't test for same spell names (i haven't bought RoS) but i tested it for a general buff changed the < to suit for a false of true to test

You can /echo ${Me.Book[last spell name in your book]} to find out a suitable number

 

[aspire2008]

Tried what you suggested, moved the 97 version to slot 654 in the spell book , which is the last spell in the book, not the last spell page of the book, but moved it to last spell slot on page 82 out of 100.

Then changed to ${Me.Book[${castWhat}]}<654

EDIT: Err it worked! Thank you for the ghetto fix !

- - - Updated - - -

Tried what you suggested, moved the 97 version to slot 654 in the spell book , which is the last spell in the book, not the last spell page of the book, but moved it to last spell slot on page 82 out of 100.

Then changed to ${Me.Book[${castWhat}]}<654

EDIT: Err it worked! Thank you for the ghetto fix !

Just realized its a bad idea to leave it as the last spell, instead of moving it all the way back to the last page of the spell book, as this is editing an ALL class macro; therefore classes that have more than your defined spell slot value would get screwed if their spellslots are beyond that.

Last spell slot is 960, incase anyone wants to use Rooster's ghetto fix. So it should be ${Me.Book[${castWhat}]}<960

 

[Rooster]

hmmm it shouldn't skip from the way i read the logic,

/if (${ReadyToCast}==5 && ${Me.SpellReady[${castWhat}]} && ${Me.Book[${castWhat}]} && ${Spell[${castWhat}].Mana}<${Me.CurrentMana}) /call CastSpell "${castWhat}" ${WhatID} ${sentFrom}

Should still result to true and call the cast without ever getting to the } else { before it's actually on cool down and using the < function. First cast should occur at the least

I can't play with this really sorry, wizards all 105 no RoS

 

[LurkMcGurk]

I see this is an old thread but is there any better fix for this problem than doing this? My Kissassist is loading Cloudburst Thunderbolt (level 97) in random spell gems and being really annoying just like this thread described a year ago.

 

[aspire2008]

Nope there isn't unless KA allows you to enter the spell ID number as a valid tag instead of the spell name.

 

[LurkMcGurk]

Nope there isn't unless KA allows you to enter the spell ID number as a valid tag instead of the spell name.

Thanks!! Guess I will use the fix you guys came up with then since there is no alternative =(