KissAssist Release KissAssist (3 Viewers) 12.002.039

[Zebadiah]

Lets see if we can get you going. A few questions first:

1. Is this only happening on one character or is it happening on all of your characters?
2. Have you tried to do a fresh install (D/L the launcher and then update your macro and plugin sections) to make sure nothing is corrupted there?
3. Is everything pointing to the right directories?

If all that is good and current I would then look at how you are calling KissAssist. I use /mac Kissassist and either tank or assist at the end. If you are using a hotkey to load Kissassist might want to look at the structure of the hotkey. If you need I have several hotkey set ups for running Kissassit if you want to look at them or use one. (been collecting hotkey set ups). The next thing to look at would be the Charater_ini file.

 

[sl00tx]

Only using kiss on one char - Same ini worked on 1 pc, no longer working on another. Everything is freshly installed

 

[ctaylor22]

Most likely you have EQBCOn and/or DanNetOn set to a NON-Numeric value.

 

[methodx]

So I was trying to start KA12 up to use a specific ini file;

/mac kissassist assist <assists_name> ini <ini_file_name>.ini

No bueno, the commands above works with KA11.


It does seem to be trying to load the correct ini because I get a message at the start 'Ini file has been set to >> <ini_file_name> <<. The error I'm getting is 'Mainassist ini is no where to be found. Ending Macro.' so it seems to be taking 'ini' as the assist's name no matter what arrangement I try. Perhaps the syntax I need to use has changed?

 

[ctaylor22]

@methodx There were some changes made to the param parsing routine, but nothing that I can think of, that would keep what you're trying to do from letting you. I will take a look at it and see if I find anything.

Try this: /mac kissassist assist ma <assists_name> ini <ini_file_name>.ini

Shouldn't have to use the ma tag, but just wondering how that works.

 

[methodx]

@methodx There were some changes made to the param parsing routine, but nothing that I can think of, that would keep what you're trying to do from letting you. I will take a look at it and see if I find anything.

Try this: /mac kissassist assist ma <assists_name> ini <ini_file_name>.ini

Shouldn't have to use the ma tag, but just wondering how that works.

No difference including the ma tag

 

[freeferli]

I am curious if this is ready to be moved out of beta?
I have been using it for a while now, and it seems very stable.

 

[deathlock]

I am curious if this is ready to be moved out of beta?
I have been using it for a while now, and it seems very stable.

But if he releases, then he has to start on KA 13!!! I got ideas

 

[freeferli]

But if he releases, then he has to start on KA 13!!! I got ideas

Thats not true, he can do KA 12.002-12.999

 

[B_I_G__D_A_D_D_Y]

I am curious if this is ready to be moved out of beta?
I have been using it for a while now, and it seems very stable.

Yes, I agree too. While there remain some quirks it runs well on 3 machines and 2 teams for me. I'd say it's ready for prime time!

 

[ctaylor22]

I am currently working with @Redbot to get this mover over. Please be patient, we are still working on other aspects of the macro. Like the help and instructions information.

 

[AnotherJohn]

A small problem on bards. I am level 80 on a TLP and just switched my aura buff from "Aura of the Muse" to "Aura of the Artist Rk III". Muse worked perfectly and just rebuffed when the aura wore off. However Artist continues to try to spam rebuff every cycle (ie each time it finishes a twist out of combat). I have my buff entry set this way, "Buffs1=Aura of the Artist|Me", which is exactly how I had Muse set up. Also should let you know I tried changing it to "Buffs1=Aura of the Artist Rk. III|Me" just to see if it made a difference but it did not so changed back. The problem also occurs on the most recent version of Kissassist 11 so not sure if it is a fix I need to make on my end or if it is in the coding. I do not get any error messages in the MQ2 window just the "You do not have sufficient focus to maintain that ability" in the EQ window which is the message you get whenever you try to cast an aura when you already have one applied. If it appears to be something on my end suggestion on fix appreciated. Thanks, AnotherJohn

Also should mention that every once in a while (anywhere from 3 times in 6 hour stretch to once a week) I still have the gems lock up and need to log out and back on to clear. Same as the other problem it also happens on Kissassist 11.

 

[ctaylor22]

I thought auras had their own tag? "Buffs1=Aura of the Artist|Aura"

 

[AnotherJohn]

ctaylor22,

I thought auras had their own tag? "Buffs1=Aura of the Artist|Aura"

Ok, that seems to fix it. You would think that having done this a while I would catch some of this stuff by now but alas I guess not. In hind sight it makes total sense as I was probably having the macro check the buff windows rather than the aura window, sigh. Thanks for the help, again, AnotherJohn

 

[ctaylor22]

NP. Glad I could be of assistance.

 

[jande]

On the TargetSiwtching, Mine is turned on.

While doing the great divide mission it sees the npcs as named and switches to them. Could there perhaps be a switch to not switch at all ?
e.g if you have TargetSiwtchingXXX on it does not switch to named.

 

[deathlock]

On the TargetSiwtching, Mine is turned on.

While doing the great divide mission it sees the npcs as named and switches to them. Could there perhaps be a switch to not switch at all ?
e.g if you have TargetSiwtchingXXX on it does not switch to named.

The target switching is a little glitchy. When I have 5 mobs on extended target and I am killing mob 1 and it is almost dead, I switch to mob 2 (let the pets and dots kill mob 1). When mob 1 dies, my target switches off mob 2 to something different say mob 3 or mob 4, if mob 2 was next to be auto selected. Then I have to try to switch back.

I kindly nudged Ctaloyr22 to look into a possible fix.

 

[ctaylor22]

@jande, @deathlock, Yes. That is something on my list I am going to look at. The problem is that the MA is going back through the GetCombatTarget after a mob in camp dies, even though at first glance there is nothing trapping for it..

 

[jande]

@jande, @deathlock, Yes. That is something on my list I am going to look at. The problem is that the MA is going back through the GetCombatTarget after a mob in camp dies, even though at first glance there is nothing trapping for it..

Not even when the mobs dies, assuming you are familiar with ToV:Great Divide mission.
Giant+wolf spawns.

If you want to kill the wolf (or anything else that aggoes) then it continually switches back to the giant.
One of the steps is killing a giant where he deaggo/healthlock and spawn 3 ice golems, kiss keeps going back to the golem. Giant is not xtar.

Though it was since mq2 sees it as a named as other places without named around it works.

 

[ctaylor22]

For Target switching to work in kiss, you have to turn off UseMQ2Melee and turn TargetSwitchingon on.

 

[jande]

For Target switching to work in kiss, you have to turn off UseMQ2Melee and turn TargetSwitchingon on.

Dang it forgot about mq2melee, will try that next time I run it. TargetSwitchingon does not do this automatically ?

 

[Cryptonomicon]

Hello all, im having trouble with a .ini issue one multiple chars.

One char wont keep spells loaded, and gives an error "no My spells set" even though there is a Myspells and Spells set, with the exact same code as my other char, where it doesn't give me an error. Using /writespells doesn't fix the issue, and could be related to the problem below, where KA isn't reading the current .ini?

Im also having an error on my other char where it doesn't update the .ini. For example, I changed a item name, saved the ini, reloaded MQ2 and KA, and with a /kisscheck, it still returns the name of an old item that no longer can be found in the mini. I even took the .ini out of the folder, reloaded MQ2 and it still found the same errors. Really weird, its almost like it has the old mini saved somewhere else and keeps using it? I am using the ini's in the macro folder.

Any ideas?

 

[surfdog21]

Crypto...it sounds like you have inception going on. 2 macro folders. The true destination folder you are not updating. Go to the launcher, go to home, click open mq2 folder and look at the ini. This is the macro folder that is being read. Sometimes, somehow you end up with a second macro folder that you are updating instead of the one located where your launcher path takes you. I would look that way.

 

[Cryptonomicon]

Crypto...it sounds like you have inception going on. 2 macro folders. The true destination folder you are not updating. Go to the launcher, go to home, click open mq2 folder and look at the ini. This is the macro folder that is being read. Sometimes, somehow you end up with a second macro folder that you are updating instead of the one located where your launcher path takes you. I would look that way.

Yes, *duh* thank you, all fixed!

 

[ctaylor22]

Dang it forgot about mq2melee, will try that next time I run it. TargetSwitchingon does not do this automatically ?

Thinking about that now that may be something we will want to add. If you turn TargetSwitching on then by default you would have to either turn off MQ2Melee or Unload the Plugin.

Any input on this from you guy's would be helpful. My suggestion would be to just unload the plugin. When would someone need to use MQ2Melee while allowing kiss to handle target switching, or is that even possible?

 

[drawthow]

Thinking about that now that may be something we will want to add. If you turn TargetSwitching on then by default you would have to either turn off MQ2Melee or Unload the Plugin.

Any input on this from you guy's would be helpful. My suggestion would be to just unload the plugin. When would someone need to use MQ2Melee while allowing kiss to handle target switching, or is that even possible?

I run with MQ2Melee on and the only problem I have with target switching is if I double click the mob in xtargets it goes back to the last target. Other than that have no problems. I do the restless assault mission almost daily on three groups so I do a lot of target switching.

 

[ctaylor22]

Yea, MQ2Melee will NOT let you switch to another target. Once you issue the /killthis command. MQ2Melee focuses on your current target till the mob is dead.

I know in the pull routine if you have MQ2Melee loaded we issue the /melee melee=0, when pulling with melee. This way MQ2Melee won't jump in and take over. Not sure how that would work for the rest of the MQ2Melee functions like down/holy's.

 

[jande]

Yea, MQ2Melee will NOT let you switch to another target. Once you issue the /killthis command. MQ2Melee focuses on your current target till the mob is dead.

I know in the pull routine if you have MQ2Melee loaded we issue the /melee melee=0, when pulling with melee. This way MQ2Melee won't jump in and take over. Not sure how that would work for the rest of the MQ2Melee functions like down/holy's.

I will try that out next run, unloading mq2melee stopped the target switching I was experiencing
Wonder if with melee=0 it still does the spellcasts that is not in the holy's

 

[deathlock]

Thinking about that now that may be something we will want to add. If you turn TargetSwitching on then by default you would have to either turn off MQ2Melee or Unload the Plugin.

Any input on this from you guy's would be helpful. My suggestion would be to just unload the plugin. When would someone need to use MQ2Melee while allowing kiss to handle target switching, or is that even possible?

I do not use Mq2melee, so I have no input Mq2melee is useful in some ways, but seems to screw up more things then it helps.

 

[deathlock]

Yea, MQ2Melee will NOT let you switch to another target. Once you issue the /killthis command. MQ2Melee focuses on your current target till the mob is dead.

I know in the pull routine if you have MQ2Melee loaded we issue the /melee melee=0, when pulling with melee. This way MQ2Melee won't jump in and take over. Not sure how that would work for the rest of the MQ2Melee functions like down/holy's.

In the next Kiss_12.002 or greater /wink. Maybe you could include a raw section for holyshit type commands, similar to OhShit section Mule uses. That be kewl.

 

[B_I_G__D_A_D_D_Y]

Periodically (not very often!), I have noticed some of my characters trying to cast the AA origin. This happened most often right after I mashed my ISBoxer key which triggers all my characters to mash their Invis key. I have posted in another thread how I've got them all synchronized so that I get all characters double invis'd about 99% of the time.

So when these characters begin to cast Origin it breaks their invis and I have to wait 10 seconds for the Perfected Invis cooldown to expire and then try again.

I finally decided to do some research this morning and I find that the current iteration of kissassist_12001.mac has a subroutine called CheckStuckGems that gets called twice (Line 332 and 1757) that will attempt to cast Origin.

I'm not saying this is a bad thing because now that I know about it, it's easy to mash my /mqp on button before mashing my double invis button.

However, if you ever decide to revisit the logic that calls the "CheckStuckGems" subroutine perhaps there would be a method to verify if the casting window is visible and give it a second to time out? This is low priority and I understand you've got a lot of more important things you're working on!

 

[ctaylor22]

@B_I_G__D_A_D_D_Y I got it on the list. That's the best I can do for now. I think I could add some code to the stuck gem routine to check if your invised or casting to just exit.

 

[Knightly]

In the next Kiss_12.002 or greater /wink. Maybe you could include a raw section for holyshit type commands, similar to OhShit section Mule uses. That be kewl.

Try out MQ2React for that, it's just that functionality, but in a plugin.

 

[drwhomphd]

Try out MQ2React for that, it's just that functionality, but in a plugin.

Arguably faster as well -- though differently disruptive. *grin*

PLUS, added benefit, you can use it to centralize your Holy's, Down's, and Oh's across all your characters and macros (and re-use any of those conditions in KA12).

 

[ctaylor22]

I have several things on the back burner that I have been holding off on adding to Kiss, because of the linear nature of a macro. Plugins aren't as linear and allow you to do things outside of the macro, but with that said. The macro and the Plugin have to be able to stay in sync if they are to work well together.

Maybe MQ2React could be helpful in getting us over some of the hurdles that has stalled our progress. I don't like the idea of adding more Plugins(Dependency) to KISS, but that doesn't mean I am not willing to consider it.

 

[Dragonslayer]

Undefinded Variable LootOn used in Line [email protected] ... using "/mac kissassist Pettank" .... seems a new effekt today. "/mac Kissassist assist" works as usual

 

[Dragonslayer]

Now I see a message which makes me scratch my head: "Undefinded Variable LootOn used on Line [email protected]" ..... so should those variable "LootOn" be a globale Variable which I am missing for smoe reason?

 

[Dragonslayer]

One more observations: after running overseer again the message about "LootOn" did not occure again. After a sucessful run of overseer now I can run "/mac Kissassist Pettank" without errors

 

[jande]

Thinking about that now that may be something we will want to add. If you turn TargetSwitching on then by default you would have to either turn off MQ2Melee or Unload the Plugin.

Any input on this from you guy's would be helpful. My suggestion would be to just unload the plugin. When would someone need to use MQ2Melee while allowing kiss to handle target switching, or is that even possible?

Turning it off if loaded yes, unload no, if loaded and kiss knows about it usemq2melee=1 then kiss issues /killthis commands. Throws errors if you unload it while kiss is running, of course can be done that if targetswitching is on and mq2melee is on, throw a warning and turn mq2melee off.

OR mq2melee needs a flag that turns off its target switching/holding..

I switched my tank to not use mq2melee so that problem now went away for me. The things it does is pretty nice so that the kiss ini is smaller but not worthwhile the aggravation if you need to switch targets sometime.

 

[WOnce]

Silly question. How do I use KA12? Do I just add the file to my Macro folder? If I use /mac kissassist to start KA12, how does MQ2 know to use KA12 instead of KA11?