KissAssist Release KissAssist (1 Viewer) 12.002.039

[Evelyn]

I don't think I saw a response on this request, I would like to see this too please.

I agree. It would be nice to try and incorporate this. For the time being, I am still forced to continue to use a manual multi-line macro key to accomplish this. I have one line that is explicitly for my caster pet class that involves:
/bct casters //pet attack; /bct casters //pet qswarm

Problem is... I forget sometimes to hit the stupid macro key, LOL!

 

[ctaylor22]

@Junck I have it on my list of things to look at.

 

[Dozecar]

That sounds weird. Something must of flaked out, because I was having a hard time coming up with a situation in kiss where it would do what you had described.

I've seen it a bit, recently, but nothing like the screengrab. Has been fine since. If It happens again, I'll see about grabbing a debug.

I do have another question, how hard would it be to put Clerics/Shaman/Druids at the bottom of the rez list? It's annoying as hell to have him get called, or campfire into a wipe, and immediately rez himself thus killing his mana and making rezzing slower while he waits for mana.


Also, in some earlier posts we discussed saving divine rez for the tank.

Heals1=Divine Resurrection|0|rezcombat|cond13

Cond13=${RWCWho.Equal[ma]} && ${AutoRez[${i}].Arg[1,|].Find[Divine Resurrection]}

Didn't work. Cleric just ignores divine rez entirely and never uses it. Should I try killing the && etc?

 

[ctaylor22]

@Dozecar First thing I would do is add an
/echo ${RWCWho} ${RWCWho.Equal[ma]} ${AutoRez[${i}].Arg[1,|]} ${AutoRez[${i}].Arg[1,|].Find[Divine Resurrection]}
to the RezWithCheck routine. I would put it just above the following line:

/if (${Me.CombatState.Equal[COMBAT]} || ${SpawnCount[xtarhater radius ${MeleeDistance}]}) {

and see what is being returned.

 

[Dozecar]

Ok So edit the KA mac to add that line?

Then also add the condition back to the ini?

 

[ctaylor22]

And check you Discord PM's.

 

[Almafa]

I just noticed that running Kisassist_12001 the cleric was casting heals on mobs vs tank or Group members.
When I switched back to Kiss, it worked fine.
It might be something to look into.

 

[Armyboxer99]

@Armyboxer99 From looking at the log. Your Target is the mezzed mob, but your MyTargetID is the named mob and all that is good, but at the bottom of the DoMezStuff routine there is a line that is checked if the Target.ID is not Your MyTargetID, and I think the line is being skipped.

/if (${mezCombat} && (!${Target.ID} || ${Target.ID}!=${MyTargetID})) /call CombatTargetCheck 1

That line should call CombatTargetCheck and switch you back to the named. The only part of that line that would fail would be the ${mezCombat} would have to be returning FALSE. Now mezCombat is set to ${Me.Combat} in the top of the routine, so my first question is. Are you using a custom UI? If you are then try switching to the default UI and try it again.

Now if you are using the default UI, then I would need you to try and use this command the next time this happens. /echo ${Me.Combat}
and let me know what it returns.

@ctaylor22 - Sorry its taken me ages to reply. Captured this again today - as suspected Me.Combat is returning FALSE, Me.CombatState is returning COMBAT. Interestingly even when only one in camp and enchanter is in the middle of casting damaging spells Me.Combat is returning FALSE. Hope this helps.

 

[ctaylor22]

@Armyboxer99 That is very helpful, @eqmule Is this how Me.Combat should be functioning? Just wondering if this is functioning as designed being Me.Combat returns False while Me.CombatState returns Combat.

 

[ctaylor22]

@Almafa do you have your cleric doing DPS or just heals?

 

[Almafa]

@Almafa do you have your cleric doing DPS or just heals?

I set up a line in DPS to cast Turn Undead. I am not sure if I had this issue before or after. what I noticed was with Kiss_12001 I saw casting heals on mobs, when I switched to running Kiss (regular) I did not.

 

[ctaylor22]

Targeting is done in the CastWhat routine and the only difference with 11.5 and 12.001, for changing targets before casting, is 1 line that was added.

Can you tell me what the TargetType of the heal spell is returning? ${Spell[SpellNameHere].TargetType}

 

[Armyboxer99]

@Armyboxer99 That is very helpful, @eqmule Is this how Me.Combat should be functioning? Just wondering if this is functioning as designed being Me.Combat returns False while Me.CombatState returns Combat.

@ctaylor22 Hi - a bit more info that might be relevant from some testing I was doing today. Without any macros running Me.Combat only ever seems to report TRUE when auto attack is on. I don’t ever melee with my casters, hence Me.Combat always reporting FALSE even when casting dps spells.

 

[freeferli]

I am not sure if this is a new issue with 12, or if I have just not seen it before.

I am trying to PL my lower level guys (54) and my higher level guy (80) goes through all of the mobs and adds them to his ignore list.
Mobs are level 62.

It is not clear why he is doing this. When adding a mob to the ignore list, could the log give a reason why?

 

[ctaylor22]

@freeferli That is a possibility, I will put the suggestion on the list.

 

[freeferli]

Also FYI @ctaylor22 I switched back to kiss 11 and I am no longer having this problem.
Nothing is added to the ignore list.

I tried to look into the code, and see why this was happening, but I did not know what "a" means when it is given as the 2nd parameter.

 

[manydills]

Can pets beg for buffs from other party members using |begfor| in the Pet buffs section? Or is there a better way to do this?

(Like, say, a mage pet wanting a damage shield from a druid, or something. Can the druid put Thorns|pet in the buff section or does |pet only refer to the caster's pet?)

 

[ctaylor22]

@manydills There were plans for pet buff begging, but we ran into some issues that made the process very difficult. This is on my list to be revisited in the future. I haven't given up on this, just have other things on the list that I need to get finished first.

 

[ctaylor22]

@freeferli I am assuming you are referring to the PullIgnoreCheck routine? a=add to List, d=delete from list, c=clear the list.

If you you use debug there is plenty of spam that will be generated with why a mob was bypassed for pulling. There have been a lot of things changed in the pull routine(s), so could be some situation in how you are trying to pull that is being overlooked.

If you can get me a Debug log, just PM me the log so I can look and see what is going on. In this situation it would be a good idea to start the log before the puller starts pulling so the log will contain the reason the mob was added to the list to ignore.

 

[deathlock]

I would like to suggest a command that will lock your toon from moving when in combat. So he stays at the exact position where you want him. This wold be very useful for killing certain mobs or getting certain achievements.

 

[ctaylor22]

@deathlock We kind of did that. I made a change to the check before running out to meet the incoming mobs, just have to set your campradius and MeleeDistance the same. I am planning on posting an update later today.

 

[ctaylor22]

ctaylor22 updated KissAssist 12 Beta with a new update entry:

Beta4 Release

04-24-2020
Changed DPSMeter to use MQ2DPSAdv plugin.
Changed how AECheck validates mobs in AE range.
Added flag for clerics to check RezMeLast=0/1 This is in combat check related. Will Check MA, group members, then self when turned on.
Keep your tank closer to 1 spot when grabbing incoming mobs. Set CampRadius and MeleeDistance to the same value.
Mez routine now checks Me.CombatState and DPSOn as well as...

Read the rest of this update entry...

 

[manydills]

I must be doing something wrong with the syntax here; can someone help?

On my Ranger, I have:
Buffs7=Summoned: Arrow|begfor|100|alias|modrod

On my Mage, I have:

Buffs7=Summon Arrows|Summon|Summoned: Arrow|100|alias|modrod

I realize that arrows are not modrods, but what else am I doing wrong?

To clarify, I see that the Ranger sends the begfor message in MQ2 chat, but the Mage doesn't do anything at all in response.

 

[B_I_G__D_A_D_D_Y]

Just switched back to Kiss12beta tonight. Ran it earlier but then switched back to Kiss11. Running Restless Assault tonight under this newest Beta for Kiss12 I noticed it's almost impossible to change targets. I like to kill the light blue con restless dire wolves first before I kill the yellow con minis. With KA11 it sometimes takes a couple of clicks on the wolf in my Xtarget but after a few clicks it will stay on that target until it's dead. Tonight with KA12 I can spam click forever and it just stays on the Mini. Not a show stopper but being able to switch targets mid-fight makes several of these ToV Missions a lot easier! I like the macro to control nearly every aspect of the character except for movement and targeting. I don't camp much because I don't dare AFK, so I find it easier to plow content with me at the keyboard.

My Melee section looks like this:
[CODE lang="ini" title="Melee"][Melee]
AssistAt=99
MeleeOn=1
FaceMobOn=1
MeleeDistance=70
StickHow=front loose
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=1
[/CODE]

 

[ctaylor22]

@manydills Are you seeing the the beg for message your ranger is sending, on you mage in the EQBC window?

@B_I_G__D_A_D_D_Y Not sure what's up with the targeting, I made some changes to the combat routine, but not anything to do with the targeting code. Can I get you to get me a debug log and PM me the log?

 

[ctaylor22]

@B_I_G__D_A_D_D_Y Are the restless dire wolves pet's by any chance? /echo ${Target.Type} will tell you. I did make a change to the target switching to include not to switch if your current(New) target is a pet, mercenary, pc. I can remove the pet so it will switch when you target a pet.

 

[ctaylor22]

@manydills Also your ranger has to be in 1 of the following with your mage or your mage will ignore the message.

Raid, Fellowship, Guild, or Friends List.

 

[ctaylor22]

@manydills Took me a while. I had to go back and dig through the code. But the begfor code is setup to only work with items that can be summoned to your target, not items that have to be handed to another character. Most items that can be summoned and given to another character are classified as a TargetType of self and those type items are ignored. Once I figure out how to tell if an item of TargetType self can be checked if the item can be given to other characters, without having to summon it first. I will add the ability to summon things like arrows and give them to other characters. I still have some reservations on how to give items to other characters safely.

 

[B_I_G__D_A_D_D_Y]

@B_I_G__D_A_D_D_Y Are the restless dire wolves pet's by any chance? /echo ${Target.Type} will tell you. I did make a change to the target switching to include not to switch if your current(New) target is a pet, mercenary, pc. I can remove the pet so it will switch when you target a pet.

OK, so I did the mission this morning exactly like before and there was no issue at all with changing targets mid-combat! I checked all those wolves and they all reported as NPC. Please ignore my original complaint as it had to be something fluky going on with my system. Sorry for wasting your time!!!

 

[ctaylor22]

@B_I_G__D_A_D_D_Y No Problem, it is all good. I would rather people speak up about something, even if it turns out to be something wonky, than not say anything at all.

 

[manydills]

@ctaylor22 To answer your questions, yes: the Mage does see the begfor message from the Ranger in the EQBC window, and we are in the same guild. But it sounds like you figured it out - I agree that between-character trading opens a can of worms that could require careful handling.

Thanks for all you do!

 

[ctaylor22]

@manydills Well the plan is to do the Buff/Item begging in stages. Start with the easy stuff and progress onto the more complicated stuff. So don't count out the possibility, that in the future, Item begging will allow you to what your trying to do.

 

[deathlock]

Why does my shaman keep spam targeting back and forth between the MA and himself? This is when we are sitting there doing nothing. Typically happens after a battle or two.

 

[microscope]

Why does my shaman keep spam targeting back and forth between the MA and himself? This is when we are sitting there doing nothing. Typically happens after a battle or two.

Got that problem too, if you turn heals off it will fix it. But if you still want heals, not sure, hopefully someone else can help.

 

[Many_Whelps]

You probably have spells or buffs that are specified for target ME or MA and the macro is checking to see if it needs to recast.

 

[Brandash]

with the latest version of kiss12.. the /setdps spell 1 returns "SETDPS You need to mem a spell"
when rolled back to previous "release of kiss_12001" it works again.

 

[Tiger]

Is there any way to force my puller to sit whenever he pauses to let group members med?

 

[deathlock]

You probably have spells or buffs that are specified for target ME or MA and the macro is checking to see if it needs to recast.

Will dannet fix that? I thought the buff ini file kept track of buff timers.

 

[deathlock]

Why does my shaman keep spam targeting back and forth between the MA and himself? This is when we are sitting there doing nothing. Typically happens after a battle or two.

This is super annoying considering you have to pause the macro to do any hails, inspects, etc... I do not recall this happening ever in any previous version of KISS.

 

[B_I_G__D_A_D_D_Y]

This is super annoying considering you have to pause the macro to do any hails, inspects, etc... I do not recall this happening ever in any previous version of KISS.

When doing hails or trades or things like that I always make sure my MA has nothing on target. That stops the Assists from always trying to target whatever the MA has.