KissAssist Release KissAssist 7.3.5 BETA CLOSED

[Maskoi]

This a beta release purely for testing. CLOSED Official 7.3 released http://www.redguides.com/community/showthread.php/28451-KissAssist-7-Updated-06-13-2014-v7-3

I have adjusted Kiss now to use MQ2Cast_spell_routines.inc. It is a hybrid inc file that helps keep the macro in sync but still utilizes the functions of MQ2Cast

You will need to download MQ2Cast_spell_routines.inc and put it in your macro folder.

KissAssist 7.3.5 BETA
More spell casting tweaks
Fixed same spell/AA names casting like Chanters - Azure Mind Crystal
Fixed buffs |mana tag not casting AAs or items
/kisscheck will now check GoM section

GoM now supports 2 spells in case first is down on refresh.
YOU MUST CHANGE YOUR INI FILE FROM GomSpell= to GomSpell1= OR THE GOM SECTION WILL NOT WORK

[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSpell1=Gift of Mana Spell
GoMSpell2=Gift of Mana Spell

KissAssist 7.3.4 BETA
Fixed heal delays - thanks thenomadman

KissAssist 7.3.3 BETA
Fixed plugin check error for mq2cast
More debugging clean up

KissAssist 7.3.2 BETA
Incorprated MQ2Cast_spell_routines.inc in KissAssist for smoother and consistent spell casting using MQ2Cast.

 

[TheNomadMan]

Re: KissAssist 7.3 BETA

In the previous thread, you mention a fix to item casting. I was planning to bring this up after the recovery time bit was sorted; but, is it possible to distinguish between items and AA's with the same name? I know MQ2Cast had a function for this, but I'm as yet unfamiliar with sell-routines (will read it, today). I ask because I noticed that there's a couple of enchanter AA's to summon items of the same name as the AA. One for HP one for Mana, if I recall correctly. In previous versions of KA, an attempt to have KA summon such an item thru the AA and then try to click the item in inventory would fail due to MQ2Cast being unable to distinguish between the AA and the item by name (item/spell/aa arugments for mq2cast not supported in the macro).

 

[Maskoi]

Re: KissAssist 7.3 BETA

You need to tell kiss to summon the item with AA and cast the item. they are different entries and that is how kiss tells the difference. I would need to know what AA you are talking about though.

Call of the wild is an item and AA. It had to be hard coded but both would be the same. Kiss always tries to cast an item first.

 

[TheNomadMan]

Re: KissAssist 7.3 BETA

Casting time does seem a bit quicker. Not all DPS spells are being reported to the MQ2 window. Some few cast and land fine, but the MQ2 window made no mention of them (normal mode, not /debug). Most are reported fine, tho. Heals are... odd. Seems, like they wait for DPS to finish. So the early part of the fight, after "ATTACKING -> <mob x>" there are no heals at all. Then they start casting as if they were waiting in line, rather than being relevant to the current HP situation; and quickly get bogged down in the DPS, again.

 

[Maskoi]

Re: KissAssist 7.3 BETA

I think I fixed the dps spell not showing when landing and Kiss will show the spell if its resisted as well.

I just uploaded a new file

 

[TheNomadMan]

Re: KissAssist 7.3 BETA

Got the new inc file. Do we need a new KA? Or; is the last one still relevant? Guess I'll find out when I try it in a few mins lol

 

[Maskoi]

Re: KissAssist 7.3 BETA

Heals will always suffer if your main healer is trying to dps. Kiss checks heals before every dps spell. I do see the delay you are talking about though and i am looking at it now.

 

[TheNomadMan]

Re: KissAssist 7.3 BETA

Looks like they're all reporting now. And; it appears that DSPOn=2 now repeats the spells in the same order everytime, so long as the spells in question are not on recast cooldown, rather than going to a DPSOn=1 type bit after the 1st round. I'll need to run it a few more times to be sure of either. But I gotta say, if that's what's happening, that's awesome; it should make for more predictable spellweaves.

- - - Updated - - -

Say; I'm being a bit hasty testing this. Sorry for that... the newest upload still has some pause between casts. That's not unexpected, all told. I know yer still tweaking. But I keep expecting it to toss a heal in those pauses, as the HP situation demands it. It's not tho. The HP situation can call for a heal, but it'll finish casting it's current DPS spell, pause for a moment, then go on to another DPS; rather than healing. It gets around to healing later and often not with the heal that's expected, given the current HP.

 

[Maskoi]

Re: KissAssist 7.3 BETA

Is your heal section set up correctly?

 

[TheNomadMan]

Re: KissAssist 7.3 BETA

Using a very stripped down ini for testing the interplay of heals and DPS. Settings other than what's listed below are at default.

[General]
KissAssistVer=7.3.2
Role=Assist
CampRadius=30
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=1
ChaseDistance=25
MedOn=1
MedStart=15
MedCombat=0
LootOn=1
RezAcceptOn=1
AcceptInvitesOn=1
GroupWatchOn=0
EQBCOn=0
IRCOn=0
MiscGem=12
HoTTOn=1

[Melee]
AssistAt=99
MeleeOn=0
FaceMobOn=1
MeleeDistance=75
StickHow=snaproll
AutoFireOn=0

[DPS]
DPSOn=2
DPSSkip=10
DPSInterval=2
DPS1=Sunbeam Blessing|99|MA
DPS2=Clutch of Ro|98|Once
DPS3=Surge of Spineburrs|97|MA
DPS4=Nature's Withering Wrath|96
DPS5=Summer Suncrest|95
DPS6=NULL

[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
Heals1=Protection of Direwood|80|Tap
Heals2=Survival of the Fortuitous|25
Heals3=Vivification|40
Heals4=Lunassuage|0
Heals5=Stemfang Rush|70
Heals6=Sterivida|90
Heals7=Promised Recovery|99|MA
Heals8=NULL
Heals9=NULL
Heals10=NULL
XTarHeal=1
AutoRezOn=1
AutoRezWith=Rejuvenation of Spirit

- - - Updated - - -

I'm also not seeing Promised Recovery fire, anymore. I know it was working in 7.0.2. I do not believe it worked in 7.2. Will verify.

- - - Updated - - -

The XTarHeal=1 isn't relevant to this test and should've been =0. Will switch that for the next round.

- - - Updated - - -

When you say that heals are checked before every DPS. Do you mean that it does a heal check in between each DPS cast? Or; does it do a heal check, array a few DPS spells (in this case all 5 for DPSOn=2), send the array to cast, and then do another heal check?

- - - Updated - - -

7.2, with the :tryagain loop, is displaying the same heal and dps behavior as 7.3. This is what's making me think that an array of dps is being sent down and must complete casting before a heal can go in.

 

[Maskoi]

Re: KissAssist 7.3 BETA

I mean it does a health check before it continues on every dps entry. 8 dps spells = 8 health checks

 

[TheNomadMan]

Re: KissAssist 7.3 BETA

More on that: Once ATTACKING -> is displayed, it will not cast two heals in a row w/ dps on. I get several DPS, one heal, several DPS, one heal, several DPS, one heal, and so on. Out of combat it'll cast as many heals as needed, in a row.

 

[Maskoi]

Re: KissAssist 7.3.3 BETA

Thats what I am trying to track down now as I make other fixes.

 

[TheNomadMan]

Re: KissAssist 7.3.3 BETA

After reaching the DPSkip HP, however, heals do work normally in combat.

 

[Maskoi]

Re: KissAssist 7.3.3 BETA

Once this issue is solved it should be pretty solid

 

[TheNomadMan]

Re: KissAssist 7.3.3 BETA

Much agreed!

 

[Rahz]

Re: KissAssist 7.3.3 BETA

Not sure if related but one thing that delays with (beta included) is if i do not have spell memmed, for dps, and it tries to cast that spell i get something like 9098492898MQ2Cast Aborting Mem Cast Spell and takes a while to recover from that and never mems that spell. Not sure if its related at all, or just a bug with me, but if i dont have a spell memmed and its DPS, i get that error with MQ2Cast and never mems it, if its buff, works flawless using the gem specified.

 

[william12]

Re: KissAssist 7.3.3 BETA

Not sure if related but one thing that delays with (beta included) is if i do not have spell memmed, for dps, and it tries to cast that spell i get something like 9098492898MQ2Cast Aborting Mem Cast Spell and takes a while to recover from that and never mems that spell. Not sure if its related at all, or just a bug with me, but if i dont have a spell memmed and its DPS, i get that error with MQ2Cast and never mems it, if its buff, works flawless using the gem specified.

ya its suppose to try and mem the dps spell in your miscgem slot.

 

[TheNomadMan]

Re: KissAssist 7.3.3 BETA

Say, right in front of our faces?

/if (!${SingleHeal[${i}].Length} || ${SingleHeal[${i}].Arg[2,|].Equal[0]} || !${Me.SpellReady[${SingleHeal[${i}].Arg[1,|]}]}) /goto :SNextHeal

Before adding the global check w/delay to castwhat, DPS skipped unintentionally for lack of knowing what to do. Heals, however, have a separate "if not ready check". This check tells it to skip the spell. If this check goes off for the available heals during the global CD, the heals won't fire and the macro will move on to the next dps. Winner?

- - - Updated - - -

Bingo! Made the following changes and suddenly heals and DPS are firing off just as pretty as you please, with very little delay.

| If heal is null or off |0 or spell/aa/item not ready skip it
            /if (${DebugHeal} || ${DebugAll}) /echo DEBUGHEALS SingleHeal Spell ${i}: ${SingleHeal[${i}]}  ${SingleHeal[${i}].Arg[1,|]}   ${SingleHeal[${i}].Arg[2,|]}   ${SingleHeal[${i}].Arg[3,|]}
            /if (${DebugHeal} || ${DebugAll}) /echo DEBUGHEALS SingleHeal SpellSkip: !${SingleHeal[${i}].Length} || ${SingleHeal[${i}].Arg[2,|].Equal[0]} || !${Me.SpellReady[${SingleHeal[${i}].Arg[1,|]}]}
            /if (!${SingleHeal[${i}].Length} || ${SingleHeal[${i}].Arg[2,|].Equal[0]} || !${Me.SpellReady[${SingleHeal[${i}].Arg[1,|]}]}) /goto :SNextHeal

to

 | If heal is null or off |0 skip it
            /if (${DebugHeal} || ${DebugAll}) /echo DEBUGHEALS SingleHeal Spell ${i}: ${SingleHeal[${i}]}  ${SingleHeal[${i}].Arg[1,|]}   ${SingleHeal[${i}].Arg[2,|]}   ${SingleHeal[${i}].Arg[3,|]}
            /if (${DebugHeal} || ${DebugAll}) /echo DEBUGHEALS SingleHeal SpellSkip: !${SingleHeal[${i}].Length} || ${SingleHeal[${i}].Arg[2,|].Equal[0]} || !${Me.SpellReady[${SingleHeal[${i}].Arg[1,|]}]}
            /if (!${SingleHeal[${i}].Length} || ${SingleHeal[${i}].Arg[2,|].Equal[0]}) /goto :SNextHeal

and

| Delay 1.8 secs if global cooldown active
            /if (!${IAmABard} && !${Me.SpellReady[${Me.Gem[1].Name}]} && !${Me.SpellReady[${Me.Gem[2].Name}]} && !${Me.SpellReady[${Me.Gem[3].Name}]} && !${Me.SpellReady[${Me.Gem[4].Name}]}) /delay 18

to

| Delay if global cooldown active
	     :thenomadloop
            /if (!${IAmABard} && !${Me.SpellReady[${castWhat}]} && !${Me.SpellReady[${Me.Gem[1].Name}]} && !${Me.SpellReady[${Me.Gem[3].Name}]} && !${Me.SpellReady[${Me.Gem[5].Name}]} && !${Me.SpellReady[${Me.Gem[7].Name}]}) {
	        /delay 2
		/goto :thenomadloop					
	}

Clearly these changes need a more experienced hand to clean up and make pretty (safe? lol). But it works.

- - - Updated - - -

[2014/06/06 05:16:53] MQ2Log :: Logging is ON

[2014/06/06 05:18:16] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:18:17] [MQ2] ATTACKING -> an ursarachnid <-

[2014/06/06 05:18:22] [MQ2] ** Sunbeam Blessing on >> My_Tank <<

[2014/06/06 05:18:28] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:18:34] [MQ2] ** Clutch of Ro on >> an ursarachnid <<

[2014/06/06 05:18:40] [MQ2] ** Surge of Spineburrs on >> My_Tank <<

[2014/06/06 05:18:46] [MQ2] ** Nature's Withering Wrath on >> an ursarachnid <<

[2014/06/06 05:18:53] [MQ2] ** Summer Suncrest on >> an ursarachnid <<

[2014/06/06 05:18:58] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:19:03] [MQ2] ** Sunbeam Blessing on >> My_Tank <<

[2014/06/06 05:19:08] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:19:15] [MQ2] ** Nature's Withering Wrath on >> an ursarachnid <<

[2014/06/06 05:19:21] [MQ2] ** Summer Suncrest on >> an ursarachnid <<

[2014/06/06 05:19:26] [MQ2] ** Sunbeam Blessing on >> My_Tank <<

[2014/06/06 05:19:32] [MQ2] ** Summer Suncrest on >> an ursarachnid <<

[2014/06/06 05:19:37] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:19:43] [MQ2] ** Sunbeam Blessing on >> My_Tank <<

[2014/06/06 05:19:47] [MQ2] Stemfang Rush on  >> My_Tank <<

[2014/06/06 05:19:52] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:19:58] [MQ2] ** Nature's Withering Wrath on >> an ursarachnid <<

[2014/06/06 05:20:03] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:20:10] [MQ2] ** Summer Suncrest on >> an ursarachnid <<

[2014/06/06 05:20:15] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:20:20] [MQ2] ** Sunbeam Blessing on >> My_Tank <<

[2014/06/06 05:20:24] [MQ2] Stemfang Rush on  >> My_Tank <<

[2014/06/06 05:20:30] [MQ2] ** Surge of Spineburrs on >> My_Tank <<

[2014/06/06 05:20:36] [MQ2] ** Nature's Withering Wrath on >> an ursarachnid <<

[2014/06/06 05:20:41] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:20:52] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:20:57] [MQ2] Sterivida on  >> My_Tank <<

[2014/06/06 05:20:57] [MQ2] SLAIN >> an ursarachnid << EXP: 0.00% AAEXP: 0.00%

 

[Maskoi]

Re: KissAssist 7.3.4 BETA

I think you pretty much nailed it.

 

[Maskoi]

Re: KissAssist 7.3.3 BETA

KissAssist 7.3.4 BETA
Fixed heal delays when DPS is on - thanks thenomadman

New file uploaded

 

[ctaylor22]

Re: KissAssist 7.3.4 BETA

| Delay if global cooldown active
:thenomadloop
/if (!${IAmABard} && !${Me.SpellReady[${castWhat}]} && !${Me.SpellReady[${Me.Gem[1].Name}]} && !${Me.SpellReady[${Me.Gem[3].Name}]} && !${Me.SpellReady[${Me.Gem[5].Name}]} && !${Me.SpellReady[${Me.Gem[7].Name}]}) {
/delay 2
/goto :thenomadloop
}

Why are you using spell gems 1,3,5,7? Is this based on your spell setup or is there a different reason?

Ctaylor

 

[TheNomadMan]

Re: KissAssist 7.3.4 BETA

Just to avoid the off chance that someone'll manage to lock out gems 1, 2, 3, and 4 at the same time with their normal spell casting sequence. This way, it checks every other gem. I had used up to gem 10; 'til Maskoi pointed out that, that'd be bad for chars with only 8 gems.

- - - Updated - - -

That's actually in addition to checking the spell gem attempting to be cast, as well. So four to five gems are checked, each round, as a means to detect global cd.

 

[tehfeer]

Re: KissAssist 7.3.4 BETA

I have had some strange issues with the beta version. Zombie skin rk. II wouldn't cast on my SK. I ran kisscheck it showed not found. My sham and bst wouldnt cast any mana regen skills (Paragons or cannibalize). Switched back to the the non beta and zombie skin casts and is no longer on kisscheck. Sham and bst are casting mana regent agian

 

[Maskoi]

Re: KissAssist 7.3.4 BETA

Rk. II not found are you on a silver account?

The canni and paragon are known issues and fixed now. I will be releasing an official 7.3 later today or tomorrow.

Thank you for the feedback

 

[tehfeer]

Re: KissAssist 7.3.4 BETA

It works now in both. Perhaps it was user error!

 

[ctaylor22]

Re: KissAssist 7.3.4 BETA

Ok now I realize why I was waiting on my Shaman so much. was so busy trying to figure out other issues I missed he wasn't using Canni. I guess I will just have to wait for release later today or tomorrow.

Thanks Maskoi.

Ctaylor

 

[Maskoi]

Re: KissAssist 7.3.4 BETA

I will upload the latest beta now.

 

[Maskoi]

Re: KissAssist 7.3.4 BETA

KissAssist 7.3.5 BETA
More spell casting tweaks
Fixed same spell/AA names casting like Chanters - Azure Mind Crystal
Fixed buffs |mana tag not casting AAs or items
/kisscheck will now check GoM section

GoM now supports 2 spells in case first is down on refresh.
YOU MUST CHANGE YOUR INI FILE FROM GomSpell= to GomSpell1= OR THE GOM SECTION WILL NOT WORK

[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSpell1=Gift of Mana Spell
GoMSpell2=Gift of Mana Spell

New Kiss uploaded

 

[needmymq2]

Re: KissAssist 7.3.5 BETA

Thank you for getting this issue of spells not casting when they are suppose to cast and in the correct order. I have seem a big improvement in how my enchanter and wizzy work with my mage. Mobs are dyeing faster, mezz's are going off on time and saving the group or at least making the fight much easier. With the mez working as it should the effect has been a lot less healing required and a overall saving of mana in general. The Wizzy is now casting all of her spells and not just the first 3 as before thus the mobs die faster. Wonderful work. Thank you so much TheNomadMan and all others involved in this fix.

 

[william12]

Re: KissAssist 7.3.5 BETA

This version does seem way more responsive especially with heals and mezzes. The Wand of Phantasmal Modulation fix in the PM is going to be huge for people who uses mages with kiss. We could never use it before now.

 

[Sinn69]

Re: KissAssist 7.3.5 BETA

My level 100 Bard is getting spammed with this while idle in her Mq2 window:

[2014/06/08 12:46:58] Unmatched bracket or invalid character following bracket found in index: ''

[2014/06/08 12:46:58] kissassist.mac@1417 (CheckBuffs): /delay 15s ${Me.Gem[${MiscGem}].Name.Equal[${1stPart}}

[2014/06/08 12:46:58] kissassist.mac@568 (Main): /call CheckBuffs

[2014/06/08 12:46:58] Unmatched bracket or invalid character following bracket found in index: ''

 

[tehfeer]

Re: KissAssist 7.3.5 BETA

I have been testing the newest build. Today I got around to doing the first mission in Tainted west karana. When i got to killing the lava rents it seemed to cause all my bots to lock up when one died. I didn't notice until people started dying and nothing was getting mezzed. After restarting kissassist on all the chars everything worked again until I killed the next lava rent. Same issue occurred. On a different note so far my pet gem summon spell has gone to the correct location with this build.

 

[PeteSampras]

Re: KissAssist 7.3.5 BETA

My level 100 Bard is getting spammed with this while idle in her Mq2 window:

[2014/06/08 12:46:58] Unmatched bracket or invalid character following bracket found in index: ''

[2014/06/08 12:46:58] kissassist.mac@1417 (CheckBuffs): /delay 15s ${Me.Gem[${MiscGem}].Name.Equal[${1stPart}}

[2014/06/08 12:46:58] kissassist.mac@568 (Main): /call CheckBuffs

[2014/06/08 12:46:58] Unmatched bracket or invalid character following bracket found in index: ''

line 1417:
/delay 15s ${Me.Gem[${MiscGem}].Name.Equal[${1stPart}}

to

/delay 15s ${Me.Gem[${MiscGem}].Name.Equal[${1stPart}]}

- - - Updated - - -

In case people havent ever really read into error messages, here is an example of how to read them:

Subroutine LootNPCs not found.
bot.mac@93(Rest): /if (${LootNPCs}) /call LootNPCs
/call Cast "French Toast" gem1 Blue
/echo ${Group.Member[1].CoolnessLevel}

All you really need is the line number and actual error message , but the first line of code is useful so you dont have to guess.

Colors mean:
The actual error
The macro name
The line number
The subroutine it's in
The actual line of code
Filler code that you don't need unless call stack is wicked deep.

 

[Maskoi]

Re: KissAssist 7.3.5 BETA

My level 100 Bard is getting spammed with this while idle in her Mq2 window:

[2014/06/08 12:46:58] Unmatched bracket or invalid character following bracket found in index: ''

[2014/06/08 12:46:58] kissassist.mac@1417 (CheckBuffs): /delay 15s ${Me.Gem[${MiscGem}].Name.Equal[${1stPart}}

[2014/06/08 12:46:58] kissassist.mac@568 (Main): /call CheckBuffs

[2014/06/08 12:46:58] Unmatched bracket or invalid character following bracket found in index: ''

Post your bards ini file

 

[brizors]

Re: KissAssist 7.3.5 BETA

Tehfeer, your bots lock up on lava rents because they don't despawn. They stay there, invisible, at 0% health. If you're using EQBC, "/bcaa //switch" will tell all of your toons to stop attacking the invisible lava rent.

 

[tehfeer]

Re: KissAssist 7.3.5 BETA

Hmm that could be it. Though why would they stop mezzing and healing? If I have nothing targeted will they just resume normal mode?

 

[brizors]

Re: KissAssist 7.3.5 BETA

As soon as you /switch, it changes your target, and the lava rent drops from your hate list. The macro will resume once that happens, including healing/mezzing as if you were out of combat. Then it will pick up any adds, if they are still up or respawn.

 

[wackawacka]

Re: KissAssist 7.3.5 BETA

Quick suggestion, How hard would it be to add the ability for kiss to /hidecorpse when corpse is > 20 or every 20 mins or something like that to help reduce lag when boxing. Then add it to line in kiss INI under Hidecorpses=1 or 0.

I think it would be a nice feature.

I was also thinking maybe for it to to have an option also to loot corpses when they are > then a number or after 20 mins. Kind of a timed loot rather then looting every single time and wasting med time. I have the same kind of deal in the INI with LootTime=# the number representing either time or number of corpses whatever is easier.

 

[ctaylor22]

Re: KissAssist 7.3.5 BETA

Here is what it would take to do what you ask. I HAVN'T TESTED THIS CODE, so take that into consideration.

First you will need to add these lines in the General INI Section. Add the highlighted lines.

    /call LoadIni General MedCombat             int         0
    /call LoadIni General LootOn                int         0

    /call LoadIni General LootTime		int	    0
    | Hidecorpses 0=Ignore, 1=Just me, 2=Everyone, 3=Everyone but Me
    /call LoadIni General HideCorpses           int         0

    /call LoadIni General RezAcceptOn           int         0
    /call LoadIni General AcceptInvitesOn       int         1

Add this 1 Line that is highlighted you will need to find the lines above it and add the line below the Banestrike

    /declare HealsSize              int         outer       ${Heals.Size}
    /declare CureSize               int         outer       ${Cure.Size}
    /declare Banestrike             string      outer
    /declare LootTimer              timer       outer       ${LootTime}m

Now go to the SUB LootStuff and make these changes

    Sub LootStuff
        /if (!${LootOn} || ${AggroTargetID} || ${DMZ} || ${LootTimer})  /return
        /if (${Debug}) /echo DEBUG LootStuff: Enter
        /if (${Me.FreeInventory}==0) {
            /echo Inventory is full. Looting OFF
            /varset LootOn 0
            /return
        }
        /doevents
        /if (${HideCorpses} && ${HideCorpses}<3) /squelch /hidecorpse looted
        /if (${HideCorpses}>1 && ${EQBC.Connected} && ${doeqbc}) /bca //hidecorpse
        /call LootMobs
        /if (${LootTime}) /varset LootTimer ${LootTime}m
        /if (${Debug}) /echo DEBUG LootStuff: Leave
    /return

Now make sure you go into your Kissassist_ CharcterName.ini file and add the LootTime=0 and HideCorpses=0, 1, 2, or 3. 0=Ignore, 1=Me only, 2=Everyone, 3=Everyone but Me. LootTime is in minutes so put whole minutes 1 to whatever.



Like I said I am not at home, So I can't test this, there could be something I overlooked, but this is what it would take to do what you asked.

Good Luck

ctaylor