Question - Enchanter Charm

[Fueil]

Hey all, I'm curious how or if anyone deals with charm on enchanter, bard, necro, and druid.

As I know kiss doesn't handle it, which is fine. However, when I pause kiss to say charm on my enchanter and unpause my enchanter wont send in the charmed pet. I have repeated this also on my druid.

I'm trying to find a way to make this work, and simplify this. I don't mind manually doing it, but when kiss isn't sending in the pet, it makes me wonder if I need to go back to my old ways of kind binds in Isboxer? If I do this, it will not only slow my overall dps and amazing capabilities, but overall making it more work.

So, if I can get some thoughts, theories, and what you do? I would be grateful!

Thanks all!

Also, I hope everyone is doing well during these times!

 

[drawthow]

you could try DPS1=command:/pet attack|100 If this command works with charmed pets

 

[Fueil]

I will give this a try later, and report back. I have one for all the swarm pets, so maybe this will do the trick.

 

[Evelyn]

Hmm. This is a nice experiment. Are you controlling your tank/ma manually? If so, my thoughts here would need testing. Right now I'm just brainstorming and throwing ideas out here. It would involve something along the lines of:

a) Casting the charm spell via /command and then pet attacking via /command as well (would be two separate DPS lines)
b) The /command line with the charm spell would need to have conditionals set for it.
c) The conditionals would check xtarget (mob on the extended target window), checking it's level to make sure it can be charmed.

Once you charm the mob, it should be off the automatic extended target slot. When charm wears off, it will go back onto the automatic extended target slot.

I think you can force KA to cast anything via the /command line if I'm not mistaken including charm, so that's what I'm going by with this.

Again, these are just ideas. Not sure if it will work.

 

[Fueil]

I didn't get a chance yesterday to try out the command. I will this afternoon.

Evelyn, interesting thoughts. I will test some stuff out. I know there's a lot of risk with charm, but damnit if I dont want to risk if for the biscuit! I will play around with this later for sure.

I'm assuming a condition would have to be like if charmed something like that.

 

[Evelyn]

There are ways around this. Probably a more simple and elegant solution, which is why I asked if you control the tank manually (preferred in this situation), is to just make manual macro keys. If you run all toons in bot-mode then you can realistically just put this on any toon's screen you are watching the most (I would still do it on the tank's screen though just in case). You would have quicker control to charm and on charm breaks.

Plus, maybe you're tired and don't want to keep charming over and over and take a break where ever you want. Or what if the mob is not charmable? That's a lot of stuff try and set conditionals for in KissAssist and honestly will just make your toon slower to do other things or bug out.

For example, you can tell your enchanter to charm the target you/tank are on while keeping it at bay (taunting, etc). If you are running kissassist on the enchanter, you can additionally pause kiss, have enchanter target your target, cast charm and resume kiss. You can do it all in one key as follows:

Your Social Macro Key to charm a mob can look like this:

Line 1: /bct EnchanterName //mqp on
Line 2: /pause 1; /bct EnchanterName //target id ${Target.ID}
Line 3: /pause 1; /bct EnchanterName //cast InsertSpellgemNumberforCharm
Line 4: /bct EnchanterName //mqp off

You then have 1 of 2 options as far as sending the charm pet.

option a) You can just pet attack from the tank via a 2nd social macro key. It should work just fine even if kissassist is turned back on. Just mash the button and send it in.

Line 1: /bct EnchanterName //pet attack

option b) If you want to try to set it and forget it in kiss, (not sure if this works)

DPS1=command:/pet attack|100
(I'm not sure if this would work. If you don't have a pet up then it should theoretically just move on to the next thing in your DPS section anyway)

 

[eqtrader74]

Not sure if it's still an active toggle option, but IHC's ench macro had charm pet built in awhile back.

 

[holllywoooood]

Not sure if it's still an active toggle option, but IHC's ench macro had charm pet built in awhile back.

Ive actually been trying to use this the past few days. It seems he (chanter) will start using it randomly im not sure what triggers it. But he will not always do it for some reason. Every couple of hours he will just randomly charm a pet and it will go smooth for a while where he will re Charm the pet. All of a sudden when it breaks he mezz's it and it will be hours before he tries to do it again.

 

[Fueil]

Sorry for the delay on the reply.

So, I tried the Social Macro key. One thing I noticed is, my enchanter is doing the commands except casting the actually spell itself.

I am playing around the the delay to see if this will make a difference.

I also dried that DPS1=command and it didn't work, but it did of course work with a regular pet.

 

[Evelyn]

Ok let's try this:

/bct EnchanterName //cast InsertSpellgemNumberforCharm

Can you just use that first and make sure it works?

/bct Fueil //cast 9 (or whatever slot in your spells gems it's in.

Is that part just not working? I should ask if you are using EQBC

 

[Fueil]

So, I just tried sending a basic /bct name //cast 13 and it will cast charm. But, in the social macro it won't.

 

[Fueil]

Yes, using EQBC, and the basic command it working. So, obviously I need the target ID for good reason. I'm wondering if I need a two step social macro. One for just targeting then another for actual command to charm?

 

[Fueil]

Okay, so I just tested a few things here.

Line 1: /bct name //mqp on
Line 2: /pause 1; /bct name //target id ${Target.ID}

On their own separate social key, and this works no issues.

Trying this command on its own macro doesn't work, except the /mpq off works.

Line 1: /pause 1; /bct name //cast 13
Line 2: /bct name //mqp off

However, if I just leave

If I just use its own social macro without a pause for the //cast 13 it works. So, tells me the pause is causing an issue. Also the commands in sequence is also conflicting somehow.

Also, just tested out the DPS15=command:/pet attack|97 worked lower in my DPS list versus DSP1

 

[Evelyn]

I re-read the last post, oops! I think i realized why it didn't work. The /pause command delays the next spell after it's cast. I used it incorrectly before. It needs to only be used with an actual spell being cast on the respective macro line - my bad. I thought it would delay actions in EQBC but it does not do that. I think as a result, that's why line 2 probably didn't even work in my original example.

Maybe try the original macro social example without any pauses at all and see if it can work that way?

 

[Fueil]

I tried the original without any pauses, all it does it just mqp/on or off doesn't cast the spell at all sadly. Tomorrow I will keep playing around with it. Worse case scenario is having two macros. I just wanted to simplify it more, as we all do try our best too hehe!

 

[Evelyn]

Hmm. I now tested this out of curiosity on my enchanter, and I think the issue was actually not having a comma after the pause (my bad again). I also needed to factor in a much longer delay to give the enchanter time to "process" the lines spammed to her. I was able to do this by creating the macro on my tank. Deviser's Command takes a good 3 seconds for me to cast (3.3 to be exact with my spell haste). This ended up being the working macro (I was using the charm spell in my 1st gem slot):

Line 1: /pause 2, /bct Enchanter //mqp on
Line 2: /pause 2, /bct Enchanter //target id ${Target.ID}
Line 3: /pause 30, /bct Enchanter //cast 1
Line 4: /bct Enchanter //mqp off

What happened before in my original (bad) example is that you were probably turning kiss on and off before she could even react to casting the charm. As long as she is midway casting, it's fine to turn KA back on though (probably because I have CastingInterruptOn=0 in my enchanters KA ini file to prevent her from stopping midcasts).

I would adjust the pause values to be higher if you feel they are not working for you still to compensate for any lag or if you take longer to cast the respective charm spell than I do.

 

[Fueil]

I will check this out here in a few minutes. I'm still trying to get all this stuff down, its all trial and error I feel lol. So, no your bads or my bads, just of the journey to make things work. I just appreciate yours and everyone's help/assistance with these things.

 

[Fueil]

Okay, so with your new information posted, I can get it to work, but now the //mqp off isn't working. I'm messing around with the delays see if that doesn't work. If not my other idea is maybe moving it up one line in the macro. Otherwise its pretty flawless.

Also, I do have CastinInterruptOn=0

 

[Fueil]

Okay, I can confirm on both Enchanter & Druid this works in this order. Since you said something about the CastingInterruptOn=0, I figured that if the command is sent like you said before the previous command basically, it will still send the casting command. This does work in this order for me.

Line 1: /pause 2, /bct Enchanter //mqp on
Line 2: /pause 2, /bct Enchanter //target id ${Target.ID}
Line 3: /bct Enchanter //mqp off
Line 4: /pause 30, /bct Enchanter //cast 1

 

[Fueil]

The one thing I just observed is, if you pull and say you have Enchanter/Druid both charmed, one breaks, my enchanter mezzes because of his Ini (which I want and is fine), I noticed that even after a recharm the rest of the group thinks its still an enemy and will start running through their DPS lines on a charmed pet. I'm assuming this is just the way KISS is, and have to restarted the other's KISS macro's?

I just tested a /bcaa //mqp during breaks, and it seemed to fix my group from not blasting the mobs. I will test this a few more times, and it wasn't during combat, as I don't risk the charm during combat.

 

[Evelyn]

Yea, that can be an issue. Unfortunately, in some zones, if I have an NPC just targeted so I can say stuff to it, the rest my grp sometimes gets stalled on it (will keep it targeted and sometimes bug out thinking it's a boss or something). If this is happening for you on a charm situation, then you probably need to tell your whole grp to change targets. On some missions, I have to force my grp anyway to burn and change targets where I see fit. I keep separate macros for cases I need to force them to do things or override kiss. I'm actually not sure if there is a command to reset or wipe targets. I believe since it registers the charmed mob as a "mob" based on camp detection settings, that even having the mob off extended targeted after charm may still pose some problems. For these reasons, that's why I keep targeting and burn macros additionally in my hotbars. Maybe someone else can give further input on how to deal with it, but the additional macros are the only way I know of in this case.

 

[Fueil]

I've still yet to get /changetarget to actually work, and my burn section. The only burns I get to work are actually just burned all name. So, other issues i'm going through. But, the charm information you provided and helped me work through is great! I'm glad it works, and truly thank you.

 

[hellfyre]

/switchnow is the command for kiss to switch targets and i believe it's /burn to get them to burn but I may be wrong on the second one.

 

[Fueil]

/switchnow is the command for kiss to switch targets and i believe it's /burn to get them to burn but I may be wrong on the second one.

Thanks, yeah I was just giving an example, I should have used the right command for it. But, the last time I did /burn it came up empty lol. So. That is with including the burn section in the ini