Question - KA and Charming? My bots don't know friend from foe!

[colexian]

I have my enchanter set up like this:

DPS2=Tashanian|100|once
DPS3=Boltran's Agacerie|100|once
DPS4=NULL
DPS5=Dyn's Dizzying Draught|90
DPS6=Dementing Visions|100

Problem is, my tank (and MA/puller) stays on the charmed mob while the rest of the group gets beat on by adds.

I am also having an issue (posted about in a different thread, but wanted to put it in a better forum location) with my MT/MA/Puller going to pull mobs and getting an add, and running back to camp with the add but still targeting the still-out-of-combat original mob. So then the add beats on the group, everyone assists the tank, and the tank stays targeting some mob that never got pulled.

Suggestions? Recommendations?
Appreciate any help or unhelpful but witty/funny commentary.

 

[Hihi]

Meistro posted about your issue in the other thread, which should clear your issues up for that.


As for the charm mob, I'd recommend adding a holyshit to check your target for the charm buff, and if it's charmed, do a /switch.


Something like:

holyshit#=/if (${Target.Buff[Name of chanter charm debuff here].ID})  /switch

 

[colexian]

You are very correct! Meistro fixed my issue right up.
Do you have a recommended guide for holyshits and downshits? I have been using KA to handle everything so far and haven't messed with them yet.
I will go read the friendly manual.

 

[Hihi]

Downshits and holyshits are paired with downflags and holyflags.

You can have something like 40-60 of each now, I believe.

In your server_name.ini file in your release directory, there will be a MQ2Melee section, and is where your shits/flags will be located.

downshits will ONLY process when you do not have auto-attack on, and holyshits will ONLY process if you have autoattack on. If you want something to process both during autoattack and not, you need to have a down and a holy for the same situation.

Downshits and holyshits are formatted the same way:

downshit1=/if (Condition && Condition && Condition) /command

Conditions must produce a number other than 0 or produce "TRUE" to process correctly and issue the end command. You can use comparisons or use Equal/NotEqual MQ2data types to produce your results for your conditions. In the above holyshit I made for you, the .ID at the end of the buff check produces the buff's ID number, or results in a NULL if the buff is not present. If the buff is present and a number is returned from the ID check, it will treat it as a TRUE and process the /switch command.

You can use comparative statements like ${Target.PctHPs}<98 or ${Me.CombatState.NotEqual[COMBAT]} as conditions. They're extremely versatile when you've familiarized yourself with the MQ2 TLO's and data types.

If you have more questions, post. I'll help as much as I can. Would have made a more thorough description of the shits if I weren't at work atm.

 

[Maskoi]

Kiss doesn't do charm. There is a hacked version of it for that but the RG Official version does not.