Question - Custom conditions WITHOUT using KissAssist?

[Yaguex]

Version of KissAssist.mac?

12

When did your problem start?

Today

Character Role?

1. Assist

What class is having this issue?

1. Necromancer

How often does this issue occur?

Always

Can you reproduce the issue?

By taking damage

Hey All,

I play a 6-necro group, where I manually play the main chaaracter, and all other non-main characters are managed via basic macro keys like "/dgae /assist MainNecro", "/dgae /pet kill" , "/dgae /cast DoT", etc. Everything is running fine, but I would like the 5 non-main characters to auto-cast Harmshield and Feign Death if they get hit.

I have tried to copy/paste the following [KConditions] and [DPS] from KissAssist's INI library and place them into the character's standard INI files (ServerName_CaracterName.ini) for all those 5 non-main characters:

[KConditions]
ConOn=1
CondSize=2
Cond1=${Me.PctHPs} <= 99 && ${Me.PctHPs} > 80 && !${Me.Feigning}
Cond2=${Me.PctHPs} <= 80 && ${Me.PctHPs} > 0 && !${Me.Feigning}

[DPS]
DPSOn=1
DPSSkip=0
DPSInterval=1
DPSSize=2
DPS1=Harmshield|100|Cond1
DPS2=Feign Death|100|Cond2
DebuffAllOn=0


Unfortunately, it doesnt work: when any of those 5 non-main characters take damage, neither HarmShield or Feign Death trigger. I would prefer not to use KissAssist if possible (I have had too many headaches trying to making it work, no need to elaborate). Is there any way to program some basic conditional rules to achieve the above WITHOUT using KissAssist?

Thanks!

 

[Robban]

Hey All,

I play a 6-necro group, where I manually play the main chaaracter, and all other non-main characters are managed via basic macro keys like "/dgae /assist MainNecro", "/dgae /pet kill" , "dgae /cast DoT", etc. Everything is running fine, but I would like the 5 non-main characters to auto-cast Harmshield and Feign Death if they get hit.

I have tried to copy/paste the following [KConditions] and [DPS] from KissAssist's INI library and place them into the character's standard INI files (ServerName_CaracterName.ini) for all those 5 non-main characters:

[KConditions]
ConOn=1
CondSize=2
Cond1=${Me.PctHPs} <= 99 && ${Me.PctHPs} > 80 && !${Me.Feigning}
Cond2=${Me.PctHPs} <= 80 && ${Me.PctHPs} > 0 && !${Me.Feigning}

[DPS]
DPSOn=1
DPSSkip=0
DPSInterval=1
DPSSize=2
DPS1=Harmshield|100|Cond1
DPS2=Feign Death|100|Cond2
DebuffAllOn=0


Unfortunately, it doesnt work: when any of those 5 non-main characters take damage, neither HarmShield or Feign Death trigger. I would prefer to not use KissAssist if possible (I have had too many headaches trying to making it work, no need to elaborate). Is there any way to program some basic conditional rules to achieve the above?

Thanks!

if you want to use Kissassist stuff, you must use Kissassist. You cant put random macrospecific stuff in other ini files.

 

[Yaguex]

if you want to use Kissassist stuff, you must use Kissassist. You cant put random macrospecific stuff in other ini files.

Got it. Any way to achieve what I described above witthout KissAssist?

 

[Yama]

You could use MQ2react / LEM to get these to work. but its not just has simple has copy and paste above though

 

[LamahHerder]

Got it. Any way to achieve what I described above witthout KissAssist?

LEM is the proper way to do such things now (skip mq2react)

 

[Yaguex]

LEM is the proper way to do such things now (skip mq2react)

Thanks for the feedback. I like MQ2React's straight forward approach (condition -> reaction). Could you please elaborate on why MQ2React is not a good solution for what I am trying to do, and why LEM would be a superior alternative?

Really appreciate your insights!

 

[Nendiil]

Thanks for the feedback. I like MQ2React's straight forward approach (condition -> reaction). Could you please elaborate on why MQ2React is not a good solution for what I am trying to do, and why LEM would be a superior alternative?

Really appreciate your insights!

LEM is a Lua, so it can be managed in-game via GUI vs INI files and it's all live so you don't have to reload like you would with KA Conditions.

I believe (I am not an expert), it can also be more complex or capable in comparison while more user friendly and quicker to get started with.

Additionally, I'd say it's what everyone uses now. That in turn is more support from the community, and more community provided examples of ready made encounters and scenarios that you can use as a starter or template if you're doing something new.