Config - 105 Wiz - Kiss 10 w/ Conditions

ihc385 · May 26, 2017

Credit to user aspire2008 for writing the conditions for a modded version of kiss, I've only ported them over to the official RG version of kiss.
Its not EoKnuke or anything but does some nice burst and is pretty mana efficient.

**Eradicate magic is OFF**If you need buffs stripped from mobs turn it on
**Lower Element is OFF**If you need this debuff turn it on

KissAssist_Wizzard.ini

Rich (BB code):

[General]
KissAssistVer=10.0.0
Role=Assist
CampRadius=30
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=0
ChaseDistance=25
MedOn=1
MedStart=20
MedCombat=0
LootOn=0
RezAcceptOn=1
AcceptInvitesOn=1
GroupWatchOn=0
CastingInterruptOn=1
EQBCOn=1
IRCOn=0
MiscGem=12
HoTTOn=0
CampfireOn=0
CharInfo=Wizard|105|GOLD
GroupEscapeOn=0
DPSMeter=1
MiscGemRemem=1
ScatterOn=0
MiscGemLW=0
ConditionsOn=1
[SpellSet]
LoadSpellSet=2
SpellSetName=DPS2
[Buffs]
BuffsOn=1
Buffs1=Shield of the Pellarus
Buffs2=Armor of the Codex
Buffs3=NULL
Buffs4=NULL
Buffs5=NULL
Buffs6=NULL
Buffs7=NULL
Buffs8=NULL
Buffs9=NULL
Buffs10=NULL
Buffs11=NULL
Buffs12=NULL
Buffs13=NULL
Buffs14=NULL
Buffs15=NULL
Buffs16=NULL
Buffs17=NULL
Buffs18=NULL
Buffs19=NULL
Buffs20=NULL
RebuffOn=1
CheckBuffsTimer=6
PowerSource=NULL
BuffsSize=20
BuffsCOn=0
[Melee]
AssistAt=98
MeleeOn=0
FaceMobOn=1
MeleeDistance=75
StickHow=snaproll rear
AutoFireOn=0
UseMQ2Melee=1
[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSpell1=NULL
GoMSpell2=NULL
GoMSpell3=NULL
GoMSize=3
GoMCOn=0
[GMail]
GMailHelp=Events currently support - Dead,GM,Level,Named,Leftgroup
GMailOn=0
GMail1=NULL
GMail2=NULL
GMail3=NULL
GMail4=NULL
GMail5=NULL
GMailSize=5
[AE]
AEOn=0
AERadius=50
AE1=NULL
AE2=NULL
AE3=NULL
AE4=NULL
AE5=NULL
AE6=NULL
AE7=NULL
AE8=NULL
AE9=NULL
AE10=NULL
AESize=10
[DPS]
DPSOn=2
DPSSkip=10
DPSInterval=2
DPS1=Eradicate Magic|99
DPS2=Concussive Intuition|99
DPS3=Arcane Whisper|99
DPS4=Mind Crash|99
DPS5=Fury of the Gods|99
DPS6=Focus of Arcanum|99
DPS7=Forceful Rejuvenation|99
DPS8=Crypt-Hunter's Frostfire Robe|99
DPS9=Harvest of Druzzil|99
DPS10=Call of Xuzl|99
DPS11=Silent Casting|99
DPS12=Lower Element|0
DPS13=Mana Burn|97
DPS14=Frenzied Devastation|99
DPS15=Arcane Destruction|99
DPS16=Arcane Fury|99
DPS17=Improved Twincast|99
DPS18=Fundament: Second Spire of Arcanum|99
DPS19=Twincast|99
DPS20=Quiescent Gambit|99
DPS21=Magmatic Burst|97
DPS22=Cloudburst Stormstrike|97
DPS23=Wildflash Barrage|97
DPS24=Chaos Scintillation|97
DPS25=Shocking Vortex|97
DPS26=Dichotomic Fire|97
DPS27=Ethereal Fuse|97
DPS28=Ethereal Skyblaze|97
DPS29=Ethereal Rimeblast|97
DPS30=Claw of the Flameweaver|97
DPS31=Ethereal Fuse|97
DPS32=Ethereal Skyblaze|97
DPS33=Cloudburst Stormstrike|97
DebuffAllOn=0
DPSSize=33
DPSCOn=1
[Aggro]
AggroOn=0
Aggro1=NULL
Aggro2=NULL
Aggro3=NULL
Aggro4=NULL
Aggro5=NULL
AggroSize=5
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=0
Heals1=NULL
Heals2=NULL
Heals3=NULL
Heals4=NULL
Heals5=NULL
XTarHeal=0
XTarHeal2=0
HealGroupPetsOn=0
HealsSize=5
HealsCOn=0
[Cures]
CuresOn=0
Cures1=NULL
Cures2=NULL
Cures3=NULL
Cures4=NULL
Cures5=NULL
CuresSize=5
[Burn]
BurnText=Decepticons Attack
BurnAllNamed=0
Burn1=NULL
Burn2=NULL
Burn3=NULL
Burn4=NULL
Burn5=NULL
Burn6=NULL
Burn7=NULL
Burn8=NULL
Burn9=NULL
Burn10=NULL
Burn11=NULL
Burn12=NULL
Burn13=NULL
Burn14=NULL
Burn15=NULL
UseTribute=0
BurnSize=15
Burn7=NULL
BurnCOn=0
[Pull]
PullWith=Melee
MaxRadius=350
MaxZRange=50
PullWait=5
PullRoleToggle=0
ChainPull=0
ChainPullHP=90
ChainPullPause=30|2
PullLevel=0|0
PullMeleeStick=0
[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=0
AFKGMAction=4
AFKPCRadius=150
CampOnDeath=0
ClickBacktoCamp=0
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=92
[MySpells]
Gem1=Claw of the Flameweaver Rk. II
Gem2=Cloudburst Stormstrike Rk. II
Gem3=Ethereal Fuse Rk. II
Gem4=Ethereal Skyblaze Rk. II
Gem5=Magmatic Burst Rk. II
Gem6=Chaos Scintillation Rk. II
Gem7=Shocking Vortex Rk. II
Gem8=Twincast
Gem9=Dichotomic Fire
Gem10=Ethereal Rimeblast Rk. II
Gem11=Quiescent Gambit
Gem12=Wildflash Barrage Rk. II

KissAssist_Wizzard_Conditions.ini

Rich (BB code):

[DPS]
DPSCOn=1
DPS1=Eradicate Magic|99
DPSCond1=${Math.Calc[${Target.ID} && ${Range.Between[50,99:${Target.PctHPs}]} && ${Target.Beneficial.ID} && ${Target.Beneficial.ID}!=49665].Int}
DPS2=Concussive Intuition|99
DPSCond2=${Math.Calc[${Target.ID} && ${Target.PctHPs}>20 && ${Me.PctAggro}>50].Int}
DPS3=Arcane Whisper|99
DPSCond3=${Math.Calc[${Target.Named} && ${Target.PctHPs}>10].Int}
DPS4=Mind Crash|99
DPSCond4=${Math.Calc[${Target.Named} && ${Target.PctHPs}>10].Int}
DPS5=Fury of the Gods|99
DPSCond5=TRUE
DPS6=Focus of Arcanum|99
DPSCond6=TRUE
DPS7=Forceful Rejuvenation|99
DPSCond7=${Math.Calc[${Me.PctMana}<45 && !${Me.SpellReady[Quiescent Gambit]}].Int}
DPS8=Crypt-Hunter's Frostfire Robe|99
DPSCond8=${Math.Calc[${Cast.Ready[Crypt-Hunter's Frostfire Robe]} && ${Me.PctMana}<85].Int}
DPS9=Harvest of Druzzil|99
DPSCond9=${Math.Calc[${Me.PctMana}<75 && !${Me.Song[Quiescent Gambit].ID} && !${Me.Song[Evoker's Synergy I].ID}].Int}
DPS10=Call of Xuzl|99
DPSCond10=${Math.Calc[${Target.ID} && ${Range.Between[50,99:${Target.PctHPs}]} && (${Target.Named} || ${Me.XTarget}>2)].Int}
DPS11=Silent Casting|99
DPSCond11=${Math.Calc[${Target.Named} || ${Me.XTarget}>2].Int}
DPS12=Lower Element|0
DPSCond12=${Math.Calc[${Target.ID} && ${Range.Between[80,99:${Target.PctHPs}]} && !${Target.Buff[Lower Element III].ID}].Int}
DPS13=Mana Burn|97
DPSCond13=${Math.Calc[${Target.ID} && ${Target.Named} && ${Range.Between[20,96:${Target.PctHPs}]} && ${Target.BuffsPopulated} && !${Target.Buff[Mana Burn].ID}].Int}
DPS14=Frenzied Devastation|99
DPSCond14=${Math.Calc[!${Me.Song[Arcane Destruction].ID}].Int}
DPS15=Arcane Destruction|99
DPSCond15=${Math.Calc[!${Me.Song[Frenzied Devastation].ID} && (${Target.Named} || ${Me.XTarget}>2)].Int}
DPS16=Arcane Fury|99
DPSCond16=${Math.Calc[${Target.ID} && ${Target.PctHPs} > 1 && ${Target.Named} && !${Me.Song[Chromatic Haze].ID} && !${Me.Song[Gift of Chromatic Haze].ID} && (${Me.Song[Arcane Destruction].ID} || ${Me.Song[Frenzied Devastation].ID})].Int}
DPS17=Improved Twincast|99
DPSCond17=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && ${Target.Named} && !${Me.Buff[Twincast].ID}].Int}
DPS18=Fundament: Second Spire of Arcanum|99
DPSCond18=${Math.Calc[${Me.Song[Frenzied Devastation].ID} || ${Me.Song[Arcane Destruction].ID}].Int}
DPS19=Twincast|99
DPSCond19=${Math.Calc[!${Me.Buff[Twincast].ID} && !${Me.Buff[Improved Twincast].ID}].Int}
DPS20=Quiescent Gambit|99
DPSCond20=${Math.Calc[${Target.ID} && ${Range.Between[30,99:${Target.PctHPs}]} && ${Me.PctMana}<75].Int}
DPS21=Magmatic Burst|97
DPSCond21=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && ${Me.XTarget}<2 &&  ${SpawnCount[npc los radius 60 zradius 10]}<2 && ${Range.Between[30,60:${Target.Distance}]} && ${Me.Song[Quiescent Gambit].ID}].Int}
DPS22=Cloudburst Stormstrike|97
DPSCond22=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && (${Me.Song[Quiescent Gambit].ID} || ${Me.Song[Evoker's Synergy I].ID})].Int}
DPS23=Wildflash Barrage|97
DPSCond23=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && ${Me.Song[Quiescent Gambit].ID}].Int}
DPS24=Chaos Scintillation|97
DPSCond24=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && ${Me.Song[Quiescent Gambit].ID}].Int}
DPS25=Shocking Vortex|97
DPSCond25=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && ${Target.BuffsPopulated} && ${Cast.Ready[${Spell[Shocking Vortex].RankName}]} && ${Me.SpellReady[${Spell[Shocking Vortex].RankName}]} && (!${Me.Song[Evoker's Synergy I].ID} || !${Target.Buff[Shocking Vortex Effect].ID})].Int}
DPS26=Dichotomic Fire|97
DPSCond26=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && (${Me.Song[Gift of Mana (105)].ID} || ${Me.Song[Gracious Gift of Mana (105)].ID}) && !${Me.Song[Quiescent Gambit].ID} && !${Me.Buff[Twincast].ID} && !${Me.Buff[Improved Twincast].ID}].Int}
DPS27=Ethereal Fuse|97
DPSCond27=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && (${Me.Song[Gift of Mana (105)].ID} || ${Me.Song[Gracious Gift of Mana (105)].ID} || ${Target.Named})].Int}
DPS28=Ethereal Skyblaze|97
DPSCond28=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && (${Me.Song[Gift of Mana (105)].ID} || ${Me.Song[Gracious Gift of Mana (105)].ID} || ${Target.Named})].Int}
DPS29=Ethereal Rimeblast|97
DPSCond29=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && (${Me.Song[Gift of Mana (105)].ID} || ${Me.Song[Gracious Gift of Mana (105)].ID} || ${Target.Named})].Int}
DPS30=Claw of the Flameweaver|97
DPSCond30=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1].Int}
DPS31=Ethereal Fuse|97
DPSCond31=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && !${Me.Song[Quiescent Gambit].ID}].Int}
DPS32=Ethereal Skyblaze|97
DPSCond32=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && !${Me.Song[Quiescent Gambit].ID}].Int}
DPS33=Cloudburst Stormstrike|97
DPSCond33=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1].Int}

surfdog21 · May 27, 2017

Not sure if you put your characters name in the post at the top: Kissassist_WXzzXXd.ini or not in two places in your post, might want to take that out of there if it is...

aspire2008 · May 27, 2017

Hey Ihc385,

would you mind explaining the Math.Cal and .Int you added to those conditions I made. I'm at a total loss on understanding the change, if you can explain it in laymen terms. I'm still trying to understand basic mq2 code and I don't understand the reasoning behind the change, vs the conditions in my original post.

Also, slightly off topic. I noticed you turned off Eradicate Magic, the way I setup my condition is it only goes of if you are in a selected zone listed (although the numbers I have listed for the zone id's are completely wrong, I was just adding some arbitrary numbers so I had some sorta placeholder when I added in actual zones where I encountered mobs I wanted to use the despell on. Does turning it OFF completely go past the condition check so it would speed things up on going down the line of conditions or will it still make a condition check at that interval when the macro reads it?

I guess what I'm asking is, is there a speed up in maybe microseconds from if the condition is FALSE i.e its OFF in that state anyways, vs. actually turning the whole DPS condition to OFF i.e. DPS1=Eradicate Magic|0

Meistro · May 27, 2017

I think there was an issue with conditions when looking for a buff that wasn't there. If it wasn't up, condition would return as a NULL, which according to the devs (Claytor??) would "break" the condition. The Math.Cal and .Int add turns NULL into a number that the condition can understand, therefore fixing the issues of broken conditions.

https://www.redguides.com/community/threads/53860-Kiss-10-Condition-checks-not-working

ctaylor22 · May 27, 2017

Yea, but using ${Math.Calc[].Int} will just return a calculated value... If the condition returns TRUE the Math.Calc[TRUE].Int} returns 1 and ${Math.Calc[False].Int} returns 0. ${Math.Calc[True && True].Int} returns 1, while ${Math.Calc[TRUE && FALSE].Int} returns 0. ${Math.Calc[TRUE || FASLE].Int} Returns 1, while ${Math.Calc[False || False].Int} returns 0.

So there is some logic to his using ${Math.Calc[].Int}, so if it works for him...

ihc385 · May 27, 2017

surfdog21 said:
Not sure if you put your characters name in the post at the top: Kissassist_WXzzXXd.ini or not in two places in your post, might want to take that out of there if it is...

Nope not my wizards name, not sure why I used 2 z's either lol, good lookin out though!

aspire2008 said:
Hey Ihc385,

would you mind explaining the Math.Cal and .Int you added to those conditions I made. I'm at a total loss on understanding the change, if you can explain it in laymen terms. I'm still trying to understand basic mq2 code and I don't understand the reasoning behind the change, vs the conditions in my original post.

I'll try my best

As far as I understand it the kiss conditions dont like NULL vales and it will cause the evaluation to stop / fail ( credit to ctaylor for telling me this ), it seems that it then evaluates to true (not positive) which was causing stuff like mana burn and Forceful Rejuvenation ( among others ) to fire off every time they weren't on cool down and dps wasnt following the flow you set up.
I dont know the inner workings of the Math TLO but usually in math NULL values are treated as a 0 or FALSE so I ran a little test and did /echo ${Me.Buff[God].ID} and got NULL, did /echo ${Math.Cal[${Me.Buff[God].ID}]} and got a 0 back so I knew this was the fix for NULL returns in the conditions.
On a side note...mq2melee must have something built in that does this automatically because I write my holies / downs the same way you've written your conditions and NULL is used as a FALSE.

aspire2008 said:
Also, slightly off topic. I noticed you turned off Eradicate Magic, the way I setup my condition is it only goes of if you are in a selected zone listed (although the numbers I have listed for the zone id's are completely wrong, I was just adding some arbitrary numbers so I had some sorta placeholder when I added in actual zones where I encountered mobs I wanted to use the despell on. Does turning it OFF completely go past the condition check so it would speed things up on going down the line of conditions or will it still make a condition check at that interval when the macro reads it?

I guess what I'm asking is, is there a speed up in maybe microseconds from if the condition is FALSE i.e its OFF in that state anyways, vs. actually turning the whole DPS condition to OFF i.e. DPS1=Eradicate Magic|0

Haha well...I spent a couple hours /echo'ing every one these conditions and making sure everything worked and when I came across the select zone list I didn't really understand what was going on so I echo'd each ID and a couple came up NULL lol now I know why! I was just going to turn it on and off manually based on if I felt I needed the debuffing and where I was testing at ( DH ), I felt it was just slowing down my dps and I wanted to see what this baby could do :dance:

As far as a speed up...I think so? I think kiss sorts the cast order based on mob hp % and casts sequentially in the sorted order when DPSOn is set to 2 ( thats what I got out of the explanation in the manual ) ...so the 0's are basically last in line and not even evaluated. How much of a real difference it makes I have no clue.

BTW Big ups and thanks again on the conditions.....its a small sample and kinda wussy mobs but using gameparse after around 500 mobs I'm averaging 77k dps ( not EoK geared and not max aa ), have real nice bursts and mana efficiency is amazing...best I've had on my wiz.

aspire2008 · May 27, 2017

Thanks guys. Its sorta making sense now , but probably need to reread what you guys said and play with the conditions with /echo by myself to fully understand what you are saying lol. Or reread what you guys said 1000x more times :bang:

I'm still confused on some of the conditions not using the .Int while some are though.

For example,

DPS27=Dichotomic Fire|97
DPSCond27=${Math.Calc[${Target.ID} && ${Target.PctHPs}>1 && ${Me.Song[Gift of Mana (105)].ID} && !${Me.Song[Quiescent Gambit].ID} && !${Me.Buff[Twincast].ID} && !${Me.Buff[Improved Twincast].ID}].Int}

Like Gambit and Gift of Mana didn't have the .Int at end, also is there some syntax error on the last part, i don't see a open bracket to match the last bracket before the .Int

Also slightly of topic,

In the eqmule version of the macro, I was getting mq2cast (castM) error sometimes with the shocking vortex condition I use, which is why I added so many checks for it. Which didn't help.
Are you getting that error in your version? If so I'm not sure on how to resolve it yet, if you had any ideas. It causes the bot to go idle for that combat interval till it comes out of combat and a new combat event occurs. Which is rather annoying.

Also very nice you saw that much of a dps bump, I think the 13 hour parse with Dev's wizard bot back in January showed 45k dps or so. I improved the conditions slightly since then, but I bet the real improvement is due to Kissassist is very responsive compared to Dev's bots in general, I saw 2-3 sec bump in responsiveness on casting using the eqmule version. Can't wait to get some time to try out the new KA and give it a spin for a few hours of testing!

ctaylor22 · May 27, 2017

aspire2008 said:
Like Gambit and Gift of Mana didn't have the .Int at end, also is there some syntax error on the last part, i don't see a open bracket to match the last bracket before the .Int

The Last ].Int closes the Math.Calc[. It is Math.Calc[].Int. Everything else just gets stuck in the middle.

aspire2008 · May 27, 2017

ctaylor22 said:
The Last ].Int closes the Math.Calc[. It is Math.Calc[].Int. Everything else just gets stuck in the middle.

Oh wow, totally didn't see that, probably cause I'm not understanding how he's using the Math.Calc still, so its like you were saying , he's using it around the whole argument i.e A && B && C && D would be MathCalc[A && B && C && D].Int

and if there were 2 arguments like, (A || B) && (C && D), it would go around both arguments as follows ?

Math.Calc[(A || B)].Int && Math.Calc[(C && D)].Int

Nm, thats stupid and redundant. Need to spend some time thinking this through more.

ctaylor22 · May 27, 2017

What he is using is only one way of doing it, Another way would be to use ${If[A && B && C && D,1,0]}

Basically the ${If[Condition,true,false]} if the Condition evaluates to TRUE then return ,true if it evaluates to False then return ,false. The 2 values can be anything including other ${If[]} statements.

You could nest conditions like this ${If[${Me.PctMana}<45,${If[${Me.SpellReady[Quiescent Gambit]},1,0]},0]}

That is just an example.

eqmule · May 27, 2017

Rich (BB code):

DPS20=Twincast|99
DPSCond20=${Math.Calc[!${Me.Buff[Twincast].ID} || !${Me.Buff[Improved Twincast].ID}].Int}

I don't think that's right.
That condition reads "if not Twincast OR not Improved Twincast then cast Twincast" in other words it will always be met. (If Twincast is not up but improved Twincast IS up The condition is met and Twincast will be casted since you use OR.

If improved Twincast is NOT up but Twincast IS, The condition is also met and Twincast will be casted.

If NONE of them are up The condition is met as well.)

The only scenario where the condition is not met and Twincast won't be casted is if BOTH are up...

If you only want to cast Twincast if neither Twincast nor Improved Twincast is up it should be:

Rich (BB code):

DPS20=Twincast|99
DPSCond20=!${Me.Buff[Twincast].ID} && !${Me.Buff[Improved Twincast].ID}

The math calc is just overhead and is totally not needed.

This condition now reads: "If Twincast is NOT up AND Improved Twincast is NOT up Then cast Twincast"

ihc385 · May 27, 2017

ctaylor22 said:
What he is using is only one way of doing it, Another way would be to use ${If[A && B && C && D,1,0]}

Basically the ${If[Condition,true,false]} if the Condition evaluates to TRUE then return ,true if it evaluates to False then return ,false. The 2 values can be anything including other ${If[]} statements.

You could nest conditions like this ${If[${Me.PctMana}<45,${If[${Me.SpellReady[Quiescent Gambit]},1,0]},0]}

That is just an example.

This is exactly what I was doing at first but I wasnt sure how kiss would treat a string 1 as opposed to an actual int number, suppose it makes no difference? Guessing since conditions accept TRUE/FALSE which are strings

- - - Updated - - -

eqmule said:
The math calc is just overhead and is totally not needed.

Hey mule,

So is that true for all my conditions or just this one? I'd like to keep it as clean as possible so it'll be easier to edit. I'm trying to understand why things like mana burn were casting on trash mobs without the math calc even when I trimmed the condition down to something as simple as ${Target.Named} && !${Target.Buff[Mana Burn].ID}

Thanks for the catch on the twincast, I'll update it.

eqmule · May 27, 2017

Keep it simple. Math.calc seems like a really complicated way of adding a condition, conditions can be strings or numbers since it's evaluated during runtime by the /if command...

I use

Rich (BB code):

${Target.Named} && ${Target.BuffsPopulated} && !${Target.Buff[Mana Burn].ID} && ${Me.PctMana} > 75

in my wizards manaburn condition and it works flawlessly.

Now I haven't had time to converting it over to kiss 10 but assuming the implementation of the condition check is the same as in my modded kiss 924 that should work.

ihc385 · May 27, 2017

eqmule said:
Now I haven't had time to converting it over to kiss 10 but assuming the implementation of the condition check is the same as in my modded kiss 924 that should work.

Ahhh I think that might be it! I was using your modded kiss and this ini and loved it so when the new kiss came out I just copied the conditions over to the new kiss and it was a mess so I asked for a little help on here and ctaylor had told me that NULL values kinda break the condition check so my solution was to use if or math to turn that NULL into a 0....math won cause it was shorter for me to use lol

Thanks for the info and all your work! much appreciated

ctaylor22 · May 27, 2017

There is more to the conditions structure than was released in EQMules version. We are having to take into consideration other conditions that allow for turning on and off the conditions function. I made a change earlier today that may help with some of the conditions stability issues some of you are having.. I noticed some strange reactions to what you would think should evaluate to false, but would always evaluate to true.

aspire2008 · May 28, 2017

ctaylor22 said:
What he is using is only one way of doing it, Another way would be to use ${If[A && B && C && D,1,0]}

Basically the ${If[Condition,true,false]} if the Condition evaluates to TRUE then return ,true if it evaluates to False then return ,false. The 2 values can be anything including other ${If[]} statements.

You could nest conditions like this ${If[${Me.PctMana}<45,${If[${Me.SpellReady[Quiescent Gambit]},1,0]},0]}

That is just an example.

Ok, cool that will be easy to set it up like that, since I have conditions setup in the ini file I use for Dev's macro similar to ${If[Condition,true,false]}. Do I have to include the ${} syntax around the If statement though for KA? In Dev's macro ini file, I just have something like :

Condition22=If[${namedCount} || ${lTargCount} >= 3,TRUE,FALSE]

eqmule said:
Rich (BB code):

DPS20=Twincast|99 DPSCond20=${Math.Calc[!${Me.Buff[Twincast].ID} || !${Me.Buff[Improved Twincast].ID}].Int}

I don't think that's right.
That condition reads "if not Twincast OR not Improved Twincast then cast Twincast" in other words it will always be met. (If Twincast is not up but improved Twincast IS up The condition is met and Twincast will be casted since you use OR.

If improved Twincast is NOT up but Twincast IS, The condition is also met and Twincast will be casted.

If NONE of them are up The condition is met as well.)

The only scenario where the condition is not met and Twincast won't be casted is if BOTH are up...

If you only want to cast Twincast if neither Twincast nor Improved Twincast is up it should be:

Rich (BB code):

DPS20=Twincast|99 DPSCond20=!${Me.Buff[Twincast].ID} && !${Me.Buff[Improved Twincast].ID}

The math calc is just overhead and is totally not needed.

This condition now reads: "If Twincast is NOT up AND Improved Twincast is NOT up Then cast Twincast"

Err wow thanks for catching this. Will it return TRUE though if Twincast buff is up and Improved Twincast is NOT up. Because, ideally you don't want to use your spell gem Twincast if either is on your character.

ctaylor22 · May 28, 2017

Ok, cool that will be easy to set it up like that, since I have conditions setup in the ini file I use for Dev's macro similar to ${If[Condition,true,false]}. Do I have to include the ${} syntax around the If statement though for KA? In Dev's macro ini file, I just have something like :

Condition22=If[${namedCount} || ${lTargCount} >= 3,TRUE,FALSE]

you won't need the ${If[]} I added it to the Base code, so all you need is the condition part:

Condition22=${namedCount} || ${lTargCount} >= 3

In Kiss it would be like this ${If[${Condition22},1,0]}.

Fennil · Jun 1, 2017

added to INI List

Tone · Jul 6, 2017

This works really well... good work

ihc385 · Oct 20, 2017

Updated for the recent AA consolidation

eqgeek · Oct 27, 2017

Does this happen to have an conditions for Chromatic Haze?

ihc385 · Oct 28, 2017

eqgeek said:
Does this happen to have an conditions for Chromatic Haze?

Just for Arcane Fury, wont pop it if Chromatic Haze is on.
I'm no expert on the wiz class, if you know certain spells that should only be cast/not cast or take cast priority when its active I could probably figure out a way to work them in.

eqgeek · Oct 29, 2017

Basically if Chromatic Haze is in the song window, you'll want the wiz to stop casting whatever and hit the biggest nuke. This would only apply to having a chanter in the group, but that shouldn't matter when you create an IF statement.

Here is some example code from EOK nuke:

Rich (BB code):

/if (${Me.Song[Chromatic Haze].ID}) {
/if (${Cast.Ready[${Ethereal Fuse}]}) /casting "${Ethereal Fuse}"

rocaflocaa · Feb 4, 2018

I've been using this for a while and it does some serious damage! Do you happen to have an updated version for 110? I've tried some others, but this one is easily doing triple the damage with only EoK spells.

Wizard101 · May 12, 2018

Where do the conditions go?

eqtrader74 · May 13, 2018

For ConditionsOn=1 they go in a conditions ini file. If you set it to ConditionsOn=2 then they can go in the same KA ini under each section (DPS, Heals, Burn...)

When it is set to "1", if you run KA on that character and it doesn't find the conditions file, it will make a default one with the conditions all set to basic TRUE/FALSE. You can then copy/paste the conditions into the file. Otherwise you can make your own with the file name being KissAssist_Name_Conditions.ini

Config - 105 Wiz - Kiss 10 w/ Conditions

ihc385

surfdog21

Seasoned veteran member

aspire2008

Well-known member

Meistro

Member

ctaylor22

ihc385

aspire2008

Well-known member

ctaylor22

aspire2008

Well-known member

ctaylor22

eqmule

ihc385

eqmule

ihc385

ctaylor22

aspire2008

Well-known member

ctaylor22

Fennil

Member

Tone

ihc385

eqgeek

ihc385

eqgeek

rocaflocaa

New member

Wizard101

Member

eqtrader74

Users who are viewing this thread

Cart