• 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 (2 Viewers) 12.002.039

No permission to download
Join us with Level 2 access RedCents
Overview Commands Instructions Updates (69) Reviews (5) History Discussion
Is this supposed to be working ok on emu servers or is it just for live? I run my own LAN server and tried this last night. The tank was having issues targeting adds in camp. No problem targeting the first mob pulled but if there was an add he wasn't targeting it after the first mob died. 10.2.6 runs fine.
 
phillsphan said:
Hi all,
I'm using Kiss 10.2.6. I am trying to get KA to cast this buff on my other toons and it only casts on the rogue who's not in the group.

Buffs21=Vaporous Veil|Class|Bar,Mon,Rog,Bea,Ber

Where am I going wrong?
Thanks
Click to expand...

Technically I don't think that question belongs in this thread about the manual, but in the spirit of not being a dick it would appear the abbreviations you used for the various classes look questionable for all but the Rog and the Ber. Bard should be BRD, Beast should be BST, and Monk should be MNK. So to bring this back to the intent of the thread it would be nice if the official 3-letter class abbreviations were inserted at the location in the manual where the class modifier is first exposed! :)

As to why it works on Rog but not Ber I don't know, maybe try mixing up the class order in your statement? Or see if you have a trailing space at the end of the line?
 
Why won't My magi break my chanters Mezz? mezz fade and merc DOA! please help! thank you, happy new year
 
Reminder:

- KissAssist updated to 11.000 Lots of changes, but the biggest is that old conditions are broken.
To convert your old conditions, type "/plugin mq2kisstemplate" and then "/maketemplate"

- The old KissAssist has been preserved. To use, type "/mac kiss10"
 
Is KA11 usable on emu servers or is it just for live? I did a quick test of it on my own LAN server and seemed to have an issue with my tank not attacking adds. It was only a quick test so may have been my settings, I was using 10.2.6 before without issue.
 
Tiger said:
Is KA11 usable on emu servers or is it just for live? I did a quick test of it on my own LAN server and seemed to have an issue with my tank not attacking adds. It was only a quick test so may have been my settings, I was using 10.2.6 before without issue.
Click to expand...

Our RoF2 compile needs to be updated before we get into testing, at the moment please use Kiss10.mac for emu
 
Just downloaded the new release of 11.000 and came across this while reviewing the diff from the last beta, looks like a typo to me.

Code: 
/varset SpellToC/ast
 
There are a good number of changes from 11.010 beta to 11.000 release.

You can run a diff to see what changed with a program like notepad++.
 
I am working on updating all the changes. I should have it posted by tomorrow.
 
This is an observation and something to watch out for. If you decide to use a spell with a really long cool-down in your MiscGem spot your toon will stand there and do nothing during the entire cool down period.

I just observed this on my shaman. I changed up my spells last night and put Dissident Roar in slot 13 permanently, but slot 13 was my designated MiscGem. During a battle just now I happened to be on the shaman. We had 3 mobs mezzed in camp. When the last actively tanked mob was killed, (but before the MT had awakened another), the shaman put the Dissident Roar back into slot 13. Meanwhile, the MT awoke one of the mezzed mobs and I watched the shaman stand there doing nothing at all until the full 60 second cool-down of Dissident Roar had cycled.

Obviously the fix is simple, I changed the MiscGem to 12 and reloaded the macro, but I point this out simply because I see people report that KISS sometimes seems to stop for no reason and this could be one of them. Going forward I'll be sure to consider the ramifications of spells with long cooldowns!
 
B_I_G__D_A_D_D_Y said:
This is an observation and something to watch out for. If you decide to use a spell with a really long cool-down in your MiscGem spot your toon will stand there and do nothing during the entire cool down period.

I just observed this on my shaman. I changed up my spells last night and put Dissident Roar in slot 13 permanently, but slot 13 was my designated MiscGem. During a battle just now I happened to be on the shaman. We had 3 mobs mezzed in camp. When the last actively tanked mob was killed, (but before the MT had awakened another), the shaman put the Dissident Roar back into slot 13. Meanwhile, the MT awoke one of the mezzed mobs and I watched the shaman stand there doing nothing at all until the full 60 second cool-down of Dissident Roar had cycled.

Obviously the fix is simple, I changed the MiscGem to 12 and reloaded the macro, but I point this out simply because I see people report that KISS sometimes seems to stop for no reason and this could be one of them. Going forward I'll be sure to consider the ramifications of spells with long cooldowns!
Click to expand...

The same thing happened to me BigDaddy except i was on the cleric. Took a group wipe to figure this out. Removed spell from file. Problem fixed. Spell was Sound of Wrath I think.
 
Yes, I watched the same thing happen on my cleric with the Undying Life 60 second cooldown. So I rebooted my PC and restarted everything and suddenly the cooldown doesn't matter anymore. So something happens over time that a restart can fix.
 
B_I_G__D_A_D_D_Y said:
This is an observation and something to watch out for. If you decide to use a spell with a really long cool-down in your MiscGem spot your toon will stand there and do nothing during the entire cool down period.

I just observed this on my shaman. I changed up my spells last night and put Dissident Roar in slot 13 permanently, but slot 13 was my designated MiscGem. During a battle just now I happened to be on the shaman. We had 3 mobs mezzed in camp. When the last actively tanked mob was killed, (but before the MT had awakened another), the shaman put the Dissident Roar back into slot 13. Meanwhile, the MT awoke one of the mezzed mobs and I watched the shaman stand there doing nothing at all until the full 60 second cool-down of Dissident Roar had cycled.

Obviously the fix is simple, I changed the MiscGem to 12 and reloaded the macro, but I point this out simply because I see people report that KISS sometimes seems to stop for no reason and this could be one of them. Going forward I'll be sure to consider the ramifications of spells with long cooldowns!
Click to expand...

This is exactly why we created the MiscGemLW field. LW=Long Wait. If you have a spell you want to cast, but the recast time is longer than 30 seconds. You can use the MiscGemLW to use a secondary Gem Slot that is different than the MiscGem. You can not have both the MiscGem and the MiscGemLW use the same Gem Slot. An example would be set MiscGem=12 and MiscGemLW=13, and when you have a buff you want to cast that has a wait time of longer than 30 seconds, then Gem Slot 13 will be used, but the cast routine won't wait around for the Gem to come ready, it will just keep checking for it to be ready. Once the LW spell is cast, it will re-mem the old spell.
 
Code: 
/varset SpellToC/ast

found this in the mix of things, presumably a typo just throwing it up there for you guys to see.
 
ctaylor22 said:
This is exactly why we created the MiscGemLW field. LW=Long Wait. If you have a spell you want to cast, but the recast time is longer than 30 seconds. You can use the MiscGemLW to use a secondary Gem Slot that is different than the MiscGem. You can not have both the MiscGem and the MiscGemLW use the same Gem Slot. An example would be set MiscGem=12 and MiscGemLW=13, and when you have a buff you want to cast that has a wait time of longer than 30 seconds, then Gem Slot 13 will be used, but the cast routine won't wait around for the Gem to come ready, it will just keep checking for it to be ready. Once the LW spell is cast, it will re-mem the old spell.
Click to expand...


Can this info please be added to the KA wiki, this comes up way to often, and I know I forget it after a few months on the difference between the two, and making sure not to use the same gem slot (didn't even know that till now). Think I've had it set to the same gem all this time.
 
11.001
new sub BardSongOff replacre all
/while (${Me.BardSongPlaying}) {
/if (${Twist}) /squelch /twist off
/stopsong
/delay XXXXXXXXXXXXXXXXX
}
Code: 
| ----------------------------------------------------------------------------
| SUB BardSongOff
| ----------------------------------------------------------------------------
    Sub BardSongOff
        /while (${Me.BardSongPlaying}) {
            /if (${Twist}) /squelch /twist off
            /stopsong
            /delay 5
        }
    /return


bard instant item cast , do not twist off
item click non stable tune , delay change
Code: 
|--------------------------------------------------------------------------------------
| SUB: CastBard
|--------------------------------------------------------------------------------------
    Sub CastBard(string BardSpell,int WhatID,string sentFrom,int CastOnCorpse)
        | Bard song with long refresh is not ready so return and do not interupt twisting.
        /if (${Me.GemTimer[${BardSpell}]}>=1 && ${Me.Book[${BardSpell}]}) /return
        /if (${DebugCast}) /echo \atDEBUGCAST CastBard \awEnter ${BardSpell} ${WhatID} ${sentFrom} ${CastResult} \agLine#: ${Macro.CurLine}
        |---- instant item
        /if (${FindItem[=${BardSpell}].ID} && ${FindItem[=${BardSpell}].CastTime}==0) {
            /if (${Target.ID}!=${WhatID} && ${Spawn[id ${WhatID}].ID}) /call CastTarget ${WhatID}
            /useitem "${BardSpell}"
            /call DoCastingEvents
            /varset CastResult ${castReturn}
            /return ${CastResult}
        }
        |---- instant item end
        /varset WasTwisting ${Twist}
        /call BardSongOff
        /if (${Target.ID}!=${WhatID} && ${Spawn[id ${WhatID}].ID}) /call CastTarget ${WhatID}
        /if (${FindItem[=${BardSpell}].ID}) {
            /if (${Debug}) /echo I am a bard CastBard ${BardSpell}
            /useitem "${BardSpell}"
            /delay 5
            /while (${Me.Casting.ID}==${FindItem[=${BardSpell}].Spell.ID} && ${Window[CastingWindow].Open}) {
                /delay 5
            }
            /call DoCastingEvents
            /varset CastResult ${castReturn}
        } else /if (${Me.GemTimer[${BardSpell}]}==0 && ${Me.Book[${BardSpell}]}) {
            /squelch /twist once ${Me.Gem[${BardSpell}]}
            /delay ${Math.Calc[${Me.Gem[${BardSpell}].MyCastTime}/100 +5]}
            /varset CastResult CAST_SUCCESS
        }
        /if (${WasTwisting} && !${Twist}) /squelch /twist
        /if (${DebugCast}) /echo \atDEBUGCAST CastBard \awLeave ${BardSpell} ${WhatID} ${sentFrom}  ${CastResult}  \agLine#: ${Macro.CurLine}
    /return ${CastResult}
 
Last edited:
ctaylor22 said:
This is exactly why we created the MiscGemLW field. LW=Long Wait. If you have a spell you want to cast, but the recast time is longer than 30 seconds. You can use the MiscGemLW to use a secondary Gem Slot that is different than the MiscGem. You can not have both the MiscGem and the MiscGemLW use the same Gem Slot. An example would be set MiscGem=12 and MiscGemLW=13, and when you have a buff you want to cast that has a wait time of longer than 30 seconds, then Gem Slot 13 will be used, but the cast routine won't wait around for the Gem to come ready, it will just keep checking for it to be ready. Once the LW spell is cast, it will re-mem the old spell.
Click to expand...

Except that on my cleric who was standing around waiting for the Undying Life cooldown that spell was not part of the MiscGem assignment and yet he still waited for that cool down to end before casting anything else. Again, after rebooting and starting over he worked normally. I realize this is maybe impossible to reproduce and that's OK, if I ever can figure out a scenario to invoke it I'll be sure to post it! :)
 
B_I_G__D_A_D_D_Y said:
Except that on my cleric who was standing around waiting for the Undying Life cooldown that spell was not part of the MiscGem assignment and yet he still waited for that cool down to end before casting anything else. Again, after rebooting and starting over he worked normally. I realize this is maybe impossible to reproduce and that's OK, if I ever can figure out a scenario to invoke it I'll be sure to post it! :)
Click to expand...

Yea, that sounds unusual, when casting there are delays put in place for the global cooldowns, but not for the individual Gems to become ready. Even at the top of the CastWhat routine we check for SpellReady, and if the spell is NOT ready, then it gets skipped.

Would like to see someone be able to reproduce this at will, so we could trace it down, as it being a Kiss issue or not..
 
So I am using KA 11.001 and most of my INI files are from 10.x version with NO conditions. First off, I start up the macro and everything loads correctly with the old files, not issues. However, if I try to use the /bc //burn command I get a parse error in the MQ2 window saying it doesnt understand the //burn commands. I am not sure my toons are burning on names, I dont believe so. Is there something I need to be doing to convert the old 10.x file to support burns in 11.x. I thought you only had to convert the conditions if you were using them.

Second issue, I noticed that when a tank is fighting multiple mobs on extending target, has aggro to all of them, once one dies, he briefly will target the next mob on the list, then drop target completely like he is trying to loot the first one. I have loot in combat turned off so why is the tank dropping his target and trying to loot the dead mob? Is this maybe another issue with the ini file. The old version of KA 10.x didnt do this, it waited until all mobs were dead before it looted anything and it would march through the combat order with no issue.

Last question, what about Oh Shits, sorry if I missed it somewhere but are those still in the Server_charname.ini file or ? I am not sure if KA11 is using them and if so can someone confirm this behavior.

Thanks again, I am wanting to change out my ini files to work with KA11 but I am seeing some strange behavior on burns that I need to fix.
 
There is an oh shit section in the new INI files I cut and pasted the ones from the server ini file to the kiss ini .. but still dont understand why echo //burn to server doesnt fire a burn off for the crew... So does the new oh shit section also support down shits... Kind of confusing on what config needs to be moved where.
 
Grindage said:
There is an oh shit section in the new INI files I cut and pasted the ones from the server ini file to the kiss ini .. but still dont understand why echo //burn to server doesnt fire a burn off for the crew... So does the new oh shit section also support down shits... Kind of confusing on what config needs to be moved where.
Click to expand...

make sure your text it teh same in your INI

BurnText=
Code: 
BurnText=whateveryourburntextis
 
Grindage said:
Ok so in the Burn section of your INI you have what for the burn text then ?
Click to expand...
You. An make it whatever you want. You just want it to be the same on all toons

I use /bcaa //echo burnit

So my ini has

Burntext=burnit
 
Yea I tried this and it wont burn, have no idea what the hell is going on. This use to work just fine. You have this working with 11.010?
 
@Grindage, Post your ini file please. Burns are no longer triggered by an event(/echo "Some Phrase"). You have to use the /burn command while running the macro. The burn routine will not continuously run after pressing your hotkey. It will try and execute every Burn entry, but will not wait for global cooldowns and for spell ready. If you have any spells in your burn, that require your spell/gem bar to be ready(SpellReady), they will be skipped if the global cooldown is in effect. An example, if the first 3 entries in your burn are spells, then the first entry May be cast, but the second and third will most likely be skipped.

If you want the burn routine to run more than just once, then keep hitting that hotkey, but don't over do it.
 
@ctaylor22 Yes I understand that, the problem is the /burn command is not being parsed as a valid command, The command is being sent to all toons but they are report a DoCommand error unable to parse /burn. SO its not even recognizing the command /burn which means it wont matter whats in the INI file if they dont run a burn.
 
Code: 
/alias /burn delete

That fixed my KA unrecognized error. /burn was aliased Toggle BurnNow from IHC's macro things I think. Or check if it is set to anything with "/alias list"
 
So I updated my KISS today and I'm noticing something strange on my caster toons......

In the past, my caster bots would only nuke with spells currently memmed on spells gems. ( Good thing)
-- After today's update it now looks like my casters will not only nuke with spells already memed, but now also is cycling through EVERY spell listed in my DPS section of .ini and trying to nuke with those as well.
-- This is not helpful as some mobs are completely resistant to say, fire nukes. so I would only have MR or Cold nukes loaded, but now it not only runs through all the cold nukes I have memmed, but now mems all my Fire nukes one at a time on the MiscGem slot as well. This wastes manner and greatly decreases the caster DPS .

Attaching my .ini for your review
 
Last edited:
thisway said:
Why won't My magi break my chanters Mezz? mezz fade and merc DOA! please help! thank you, happy new year
Click to expand...
If you set your mage to pet tank on KA, it will break mez.

  • Role=PetTank - This role allows for a pet class (Mage/Necromancer/Beastlord) to have their pet tank.
  • Role=PullerPetTank - This role allows for a pet class (Mage/Necromancer/Beastlord) to BOTH pull and have their pet tank.
Code: 
/mac kissassist pettank
targeting yourself on the mage. Rest of group assists the mage.

I'm pretty sure this is the only way you get get a mage to break a mez, unless you do it manually.
 
My bards seem to be getting stuck in the latest kiss in regards to casting items. Currently my bard is set to rebuff an item click which has a cast time and occasionally (pretty frequently) when it casts the item it will get ... stuck... The cast will finish but instead of actually finishing and ending the cast it will just get stuck and say it is casting the item still. Almost like it does if you play a single song and the song stays active, except its not a song its an item buff. I am assuming this has to do with twisting songs and clicking items but the code looks right to me to stop twisting before clicking the item so im not sure.

Either way as a result when it hits this part of CastBard the bard just hangs until I manually kill the spell cast.
Code: 
            /while (${Me.Casting.ID}==${FindItem[=${BardSpell}].Spell.ID}) {
                /delay 5
            }
 
[Fri Jan 11 18:38:36 2019] Zun`Muram Mordl Delt resisted your Turgur's Insects!
[Fri Jan 18 03:10:06 2019] You resist an ukun ravasher's Chaos Claws!

Text for resist messages changed in one of the recent patches it seems. The CAST_RESISTED and CAST_RESISTEDYOU events could use an update for that, not sure if anything else changed resists are the only thing I have noticed thus far.
 
Last edited:
You must log in or register to reply here.
KissAssist Release KissAssist
Next unread thread 🦁

Users who are viewing this thread

Total: 3 (members: 0, guests: 3)
Back
Top
Cart

Cart

Total -