• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
KissAssist

KissAssist Release KissAssist (1 Viewer) 12.002.039

No permission to download
@B_I_G__D_A_D_D_Y thats what I tried first, didn't help.

writing as well at the mq2react-thread ... its one of the reacts from mq2react causing the errormessages, I am testing to narrow down which react causes the trouble
 
Today 2 toons dont work anymore:
Tank:
View attachment 25341
Healer:
View attachment 25342

Whereas dd and cc (the other 4 toons of my crew) seems to work as usual.

As far as I remember I din't made any changes in my inis the last days, but started yesterday to use Mq2React.
Can this plugin cause some interferences?
this is because mq2cast is unloaded and you have a condition or something that wants to use mq2cast /casting or similar mq2cast specific command/tlo
 
@Sic : tyvm. Jande at the mq2reac-thread had the solution for me, it's exactly what you described and I got a condition whithout the need of mq2cast.
 
@taylor - FYI come mqnext the autoinventory issue is exacerbated by at least an order of magnitude. We're going to have to refactor the delay and autoinventory structure within KA significantly, because it autoinventories so fast you can barely even get the item to register on the cursor before it's back in your inventory. I have to pause the macro to do almost anything that requires inventory interaction at this point.
 
Noob question.

How do I download KissAssist 12.001? Just use the download button or some other way? If it is just using the download button where do I save the file?

Edit - I'm assuming it is the Macro folder but trying to be certain before doing so.
 
Last edited:
I have an idea suggestion for a modification.
I've got a question. With kissassist, is there a way when doing pullertank to potentially do a power level pullertank mode meaning that that tank runs around and grabs all mobs in the camp radius and pulls them back to slaughter in one pull? It would be sweet for power leveling up groups that are 85-105 with say a 115 that could easily pull and tank the entire camp at once.
 
Noob question.

How do I download KissAssist 12.001? Just use the download button or some other way? If it is just using the download button where do I save the file?

Edit - I'm assuming it is the Macro folder but trying to be certain before doing so.
yes in the macro folder and just start it with /mac kissassist_12001 instead of just kissassist (and whatever parameters you use)

edit: I don't rename mine so I always have the normal release version of kissassist.
 
@ctaylor22

Don't know if this irritates anyone else.

mode: Pullertank
Goes out and pull then when in camp does a multiple /face while mob is running in, looks botlike from outside viewpoint.

Proposed change
Go out to pull once back at camp does a /face once, when mob <100 units then does /face again
Would also lilke the tank to turn autoattack on once mob is within 100 units (do not know if this will mess with anything else)

Code:
    Sub WaitForMob
        /declare MobsInCamp int local 0
        /declare DidFace int local 0
...
            /while (1) {
                /if (${FaceMobOn} && ${Target.ID} && (${Me.Standing} || ${Me.Mount.ID})) {
                    /if (!${DidFace}) {
                        /varset DidFace 1
                        /face ${If[${FaceMobOn}==1,fast nolook,nolook]}
                    } else /if (${Target.Distance} <100) {
                        /if (${Role.Find[tank]}) /attack on
                        /face ${If[${FaceMobOn}==1,fast nolook,nolook]}
                    }
                }
 
Last edited:
I would like to cast Zreliks whenever a new fight starts, what would be the right syntax?

DPS7=Zrelik's Recourse|100|ambush|Cond10
Cond10=!${Me.Song[Zrelik's Watch].ID}
 
@jande Have you tried turning off FaceMobOn?
/sigh its right there isn't it .... even quoted / copied the code

I will try it out.

It works, sort of.
FaceMobOn=0
pull mob to camp, don't face while it is incoming
but once in camp does not face it either.

FaceMobOn=1
pull mob to camp, does facing while running in
suspect (fast nolook) does not work together

FaceMobOn=2
pull mob to camp, don't face while it is incoming
once in camp slowly rotates to face

2 would work if it does a fast face
 
Last edited:
agree to @jande
Special when pulling mobs out of caves, the radar-like turning of the puller, always facing the actual position of the mob while waiting for the mob to arrive in camp, also for me feels the most obvious evidence of some automation in progress.
As my puller is also the tank, I feel, FaceMobOn should kept active.
Would FaceMobOn=0 nevertheless force the tank to turn to mob, once in camp?

I love Kissassist, it allows me to run a full group.
As dps I use only caster as I am a little paranioc about not catching a GM's attention.
I follow as well the rules to avoid interferences with others players game-expericences.

Would be great, if this modification: "FaceMobOn=2" is possible.
This would give me the feeling, that no other player can guess, that I use the support of this nice tools, to handle my team.

Would also like the tank to turn autoattack on once mob is within 100 units (do not know if this will mess with anything else)
I have a hotbutton "/meeleon" which, once activated, for me seem to activate autoattack on each incoming mob. (probably not already at 100 units distance).
 
How about a FaceMobOn=3? That won't break anyone's ini's and give you the ability to do what you want. I will add this to my enhancement requests for Kiss 12. Will /face fast once the mob is in melee range. How that?
 
[CODE lang="ini" title="TargetSwitchingOn"][Melee]
AssistAt=99
MeleeDistance=35
AutoFireOn=0
FaceMobOn=1
MeleeOn=0
UseMQ2Melee=0
StickHow=moveback 35% loose
TargetSwitchingOn=1[/CODE]

Special when doing Heros I would like to have more control over the tanks target. But generaly I would like to be able to change targets at will at the tank.
1605696832672.png
After the fight I checked, if mq2Melee was loaded issuing 2 times /Plugin mq2melee.

Since I am using my new hardware I have the feeling, that it got much harder, to change the target.
Sometimes I have to fight against kissassist for 5 times, until it accepts my wish to swap target. This can happen when tank targets unreachable Griklor and I want him to target one of the adds and sometimes he even seems to insist to keep Griclors Corpse targeted, while there are sufficient adds to defend.

Does the far improved hardware allow kissassist to cycle more often and so fight more often against my wishes?
Can I modify any other parameter to make the tank follow more willingly my wishes?
 
@Dragonslayer I will assume you are using the most recent update to KA 12 macro and your tank is also your MA. SwitchingTargetOn will only work on the MA. When trying to switch targets you should see a message "I am MA, and I switched to new Target." once you see that message the tank should NOT switch back, if he is switching back after getting that message then something else is switching you back to the original target.
 
@ctaylor22 your assumption is right with both: using KA 12 and Tank is MA. Dont remember to have seen a message like: "I am MA, and I switched to new Target.". I'm on my way to the heroes and will report back about that.

addendum: after the departure of Griklor I had to switch 3 times from Griklor to an add, while my tank(ma) flipped back to Griklor. After the 3rd target switch I got the message: "I am MA, and I switched to new Target." and the new target was held.
Today probbably "only" 3 times, because I tried to keep a close eye to the mq2 window for interesting messages which might had lead to slower attempts to target switching.
1605775552569.png
 
Last edited:
Is it possible to change DPSsize or BuffSize, etc.. while the macro is live. This would be a very beneficial. I find that I have to edit my Ini's to turn off my last few entries for certain scenarios. Then go back in and change them back.

Examples:

My druid dps size is 10. The first 5 are just aa abilities, debuffs few dd's. The rest are spells. If I have my cleric in the group I use all 10. When I have no cleric, I only use up to number 5. This way the druid uses less mana for dps and maintain mana for heals.

My shaman is similiar where the first few dps slots are just debuffs and slows. IF cleric in group I open him up for dps, if not he just debuffs.

When doing Missions like GD for Narandi or Kael for Avatar of War in Arena, DPS is not king. These fights are controlled. Typically I turn dps off, but then I loose my debuffs, which is annoying. Not as annoying as having to edit ini's and restart them apparently.

Last example. The last part of my DPS section on all toons are Glyphs. When just farming stuff, I let the toons just burn um up whenever. When I go to do missions though, I want to control when they use them. There fore I have to once again go in and change size's and restart macro.
 
Kiss 12 does have the ability to reload specific sections of the ini file without having to restart the macro. Never really tried to just change the value of DPSSise or BuffsSize to see what would happen. It has been a while since I have looked at that code, but it could be easily tested. Look at the /kasettings command you should be able to find instructions on the 1st page, but here is a review.

Code:
12. Restructure the code in the mainloop so the parts that load the ini file settings are moved to routine(s) This change will allow us to work on re-loading the ini settings without having to restart kiss.

Created a new Bind for this bind_settings the command for this is /kasettings and has several params.
Param 1: load, list, help
list and help are not being supported at the moment.

Load accepts the following params as the second param:
general, spells, buffs, melee, gom, gmail, ae, dps, aggro,
heals, cures, pet, merc, mez, burn, pull, afktools, conditions, or all

To reload your buffs from the ini file use the following command:
/kasettings load buffs
 
I tried /BuffsSize=1 and it tells me this is an invalid command. This means I have to open and edit the ini to change the size. Then I could reload that section, but the issue is I still have to open and edit the ini.
 
@deathlock The issue here is that BuffsSize, DPSSize, etc. Are only really used when starting the macro. This lets the load routine know the size of the array it needs to declare. When you access/call the actual routines like CheckBuffs, CombatCast, etc. The Size field is no longer used but the ${Buffs.Size}, ${DPS.Size}, etc. is used.

The only thing I can think of for now would be to have multiple ini files you use when starting kiss. Yea I know this requires restarting KA, but you should only need to copy over your primary ini file over to a new file and change appropriate entries. Then just have 2 hotbuttons for starting the character using the different ini files.

I will add this suggestion to my ideas list for future changes.
 
Thank you for confirming and considering it for future change. I like the idea about different Ini's to load. I will have to make some up for now as it would be much faster.

Thanks
 
@deathlock I was thinking about this today and there is a /changevarint that will let you change ini file entries. /changevarint BuffSize 5 would let you change BuffSize and then you could use the /kasettings load buffs to reload the buffs.

So creating a hotkey like this:
/changevarint BuffSize 5
/kasettings load buffs

Would change Buffsize=5 and then reload your buffs. Now a warning would be, not to hit that hot key in the middle of the buff routine.
You might want to add a delay between the 2 commands, so they don't step on each other.
 
I am making a kissassist 12 mycmds extension to add a set of compatibility commands to cwtn plugins so that my bcga commands work on characters running either system. I need to modify the main script a tiny bit that I thought might be useful enough that you may want to include for others. Simply adding

Code:
  /if (${SubDefined[SetupMyCmds]}) {
        /call SetupMyCmds
  }

somewhere. I put it under a similar call to load SetupAdvLootVars. This just lets you have a setup/initialization routine that runs when kissassist loads. For me this loads up the aliases for the class binds that mimic the cwtn class plugin calls. I imagine other people might want something like that so it seemed like a good idea.
 
@njk70 You could also use the [Startup] section and just add an entry. I am not sure if a /call will work, but a /bind command would. The startup section has to be added by hand, because it is an advanced feature just like what you are trying to do.
Command1=${If[${SubDefined[SetupMyCmds]},/call SetupMyCmds,/donothing]}



/donothing is a bind that would need to be added. This has given me an idea. I think I am going to add a few binds that will help with expanding the startup section when needing to do things like this. I think I will add the /donothing and a /callthis bind to the base code. Man this triggered a lot of ideas. Thanks for the input.
 
Good to know about the startup section, don't think i noticed that. I still like my original idea for the specific case of the mycmds you templated out as it doesn't require the end user to know more than removing the comment of the include in the main script rather than always modifying their ini files (as well as removing the comment). It would be nice if core MQ2 had an includeoptional or some other method to quietly not include a file if it doesn't exist. Another thing that came up is that it would be nice to have a pause function for kissassist actions. I want the macro to still be responsive to manual commands (change camp size, assistat, etc) but stop combat, buffing, pulling, automated movement. This is similar to the cwtn pause which you might need while moving your group around. I haven't dug into the script enough to see what would be involved. As usual I get more interested in programming than playing the game itself.
 
Having many issues with my bard with 12.001. recently converted him over because someone reccomended it and because he wasn't able to consistently mez Velks HA and now he won't bother at all.
getting very different results each time but they're always crap. Bard is 115, with max mez AA and all mobs are tashed and malo'd by my other toons.

1606455780729.png
 
@Myysterio Can you get me a log file while running KA 12? To start debugging use: /debug all on log. To stop debugging use: /debug all off.

Go to your log directory in you MQ2 folder and rename the log file so the .log is .txt and PM the file to me.

From what your listing above, the bard is casting mez on the mob, but not sure why it is not sticking. Could be something in the casting routine is getting canceled.
 
@deathlock I was thinking about this today and there is a /changevarint that will let you change ini file entries. /changevarint BuffSize 5 would let you change BuffSize and then you could use the /kasettings load buffs to reload the buffs.

So creating a hotkey like this:
/changevarint BuffSize 5
/kasettings load buffs

Would change Buffsize=5 and then reload your buffs. Now a warning would be, not to hit that hot key in the middle of the buff routine.
You might want to add a delay between the 2 commands, so they don't step on each other.

I tried this and I get an error:

Changing 5 to
/varset failed, '5' not found
then another 5 lines of white text.
 
@Myysterio Can you get me a log file while running KA 12? To start debugging use: /debug all on log. To stop debugging use: /debug all off.

Go to your log directory in you MQ2 folder and rename the log file so the .log is .txt and PM the file to me.

From what your listing above, the bard is casting mez on the mob, but not sure why it is not sticking. Could be something in the casting routine is getting canceled.

So, it seems to be mostly working now. I had a condition on my mez which seemed to mess up the entire process. I was trying to keep my bard from mezzing mobs which are named or cannot be mezzed and it did not like it. Id still like to be able to not try and mezz named mobs.
 
@Myysterio Can you get me a log file while running KA 12? To start debugging use: /debug all on log. To stop debugging use: /debug all off.

Go to your log directory in you MQ2 folder and rename the log file so the .log is .txt and PM the file to me.

From what your listing above, the bard is casting mez on the mob, but not sure why it is not sticking. Could be something in the casting routine is getting canceled.

Also seem to have a ton of issues with my bard waking up its own mezzes.
 
So, it seems to be mostly working now. I had a condition on my mez which seemed to mess up the entire process. I was trying to keep my bard from mezzing mobs which are named or cannot be mezzed and it did not like it. Id still like to be able to not try and mezz named mobs.

The macro itself detects when mobs are immune to mez and quits trying.
 
I added a check if spell had a CastTime of 0 in the Event_CAST_RESISTED routine. Without this when a spell which has a side effect proc has the proc resisted the code reports the main spell as having been resisted. I'm not sure about the rest of the logic in the function so maybe this could be expressed more easily. But it works nicely in my version of KissAssist 12. Thought I would share this snippet in case @ctaylor22 agrees.

Code:
    Sub Event_CAST_RESISTED(line,name)
        DEBUGCAST Event_CAST_RESISTED \awEnter
        DEBUGCAST Event_CAST_RESISTED \aw${name.Length} ${CheckResisted}

        /if (${Spell[${name}].CastTime} == 0 ) {
            /echo \aw${name} was Resisted
            /return
        }
        /if (!${CheckResisted}) /return
        /echo \aw${name} was Resisted \ag
        /if (${castReturn.NotEqual[CAST_IMMUNE]}) /varset castReturn CAST_RESISTED
        DEBUGCAST Event_CAST_RESISTED \awLeave
    /return
 
@njk70 When you /return from your code, your not returning a status to the casting routine. Do you want the casting routine to just ignore the fact that the proc was resisted? What are you trying to accomplish?
 
Script doesn't know anything about the proc so just displaying it is fine. What I was trying to stop from happening is getting the message back that some other spell resisted when it was the proc that resisted. I don't know if the script does anything with the knowledge that the spell was resisted but I was getting confused seeing notices from kissassist that a spell resisted when it wasn't.
 
If a spell is resisted the casting routine will try and cast it again without leaving the routine. If it gets resisted a second time then it stops trying to cast it on the mob this time around. The change you made would keep the casting routine from trying to cast the entry a second time.
 
KissAssist Release KissAssist

Users who are viewing this thread

Back
Top
Cart