Problem - pull ignore and mezzimmune not functioning

[Residual]

Version of KissAssist.mac?

v11.005

When did your problem start?

11/20 patch

Character Role?

1. PullerTank

What class is having this issue?

1. Warrior

How often does this issue occur?

Always

Can you reproduce the issue?

Always attempts to pull mobs listed on MobsToIgnore

Since the patch on 11/20 Kiss is pulling mobs on the MobsToIgnore list, and attempting to mez mobs on the MezImmune list. Multiple characters affected.

from Kissassist_info.ini

[charasisb]
MezImmune=a guardian golem
MobsToPull=List up to 25 mobs. Use full names i.e. a green snake,a blue tiger,a wide eye ooze or ALL for all mobs
MobsToIgnore=a disenchanted arisen
MobsToBurn=List up to 10 mobs. Use full names i.e. Beget Cube,Helias,Raze or NULL
PullPath=Place holder for path file. Not yet impletmented.
MobsToPullSecondary=NULL

 

[wymranar]

I'm having the same problem!

Also, my MobsToPull is broken as well.

 

[ctaylor22]

Can you get a debug log and PM it to me?

 

[Residual]

I will get you one tonight.

 

[plure]

The issue is related to to the "_I" being added to the end of the zones...

I started up kiss on my bazaar toonn and it creates this

[The Bazaar_I]
MezImmune=List up to 10 mobs. Use full names i.e. a green snake,a blue tiger,a wide eye ooze or NULL
MobsToPull=List up to 25 mobs. Use full names i.e. a green snake,a blue tiger,a wide eye ooze or ALL for all mobs
MobsToIgnore=List up to 25 mobs. Use full names i.e. a green snake,a blue tiger,a wide eye ooze or NULL
MobsToBurn=List up to 10 mobs. Use full names i.e. Beget Cube,Helias,Raze or NULL
PullPath=Place holder for path file. Not yet impletmented.

My guess is this is related to mules addition of information about instanced zones, but I haven't had the time to test.

 

[plure]

I'm pretty sure if they update to the latest version of VV the problem will go away.

 

[Residual]

I think if you re-read the original post this is in Sathers Tomb or charrasisb which is not an instanced zone, and I am updated to the latest VV.

 

[wymranar]

I've updated VV to the latest version, there was one more patch I was missing.

I'm still having the same problem. I'll do some more research and report back

 

[wymranar]

Ok I found a solution!

I followed @ctaylor22 's advice and did /zoneinfo while KA was running. It created a new zone in my KA_info entry.

I already had an entry called [Gnome Memorial Mountain] , but at the very bottom it had created a new entry called [Gnome Memorial Mountain_1] I believe.

After I put my settings into the new zone everything worked! I'm sure you could accomplish the same thing by deleting all the old zone files you have like someone suggested, but have not confirmed that method.

Thanks for the help everyone!!

 

[ctaylor22]

Looks like EQ has changed the way they name zones now, so check the last entry in your KissAssist_info.ini file and see if there is a new entry for the zone you are in. This would be a change made in EQ and not MQ2.

 

[plure]

Ok I found a solution!

I followed @ctaylor22 's advice and did /zoneinfo while KA was running. It created a new zone in my KA_info entry.

I already had an entry called [Gnome Memorial Mountain] , but at the very bottom it had created a new entry called [Gnome Memorial Mountain_1] I believe.

After I put my settings into the new zone everything worked! I'm sure you could accomplish the same thing by deleting all the old zone files you have like someone suggested, but have not confirmed that method.

Thanks for the help everyone!!

My guess is if you update to the latest version of the compile this issue would be fixed. There was an issue with ${Me.InInstance} which is what is causing this issue for you. You can test if I am wrong by typing
/echo ${Me.InInstance}

If you are in an non-instanced zone and it returns true you need to update to the latest version of VV.

 

[wymranar]

So, this is strange. I'm 99% sure I had already updated twice, but I followed @plure 's instructions, and it did turn up an instanced zone. I went back and ran the updater again, and I'll update if this fixes anything. Because, this morning I started having the same problem.

I could just be an idiot, because I swear I updated twice, so take all of this with a grain of salt.

 

[wymranar]

My guess is if you update to the latest version of the compile this issue would be fixed. There was an issue with ${Me.InInstance} which is what is causing this issue for you. You can test if I am wrong by typing
/echo ${Me.InInstance}

If you are in an non-instanced zone and it returns true you need to update to the latest version of VV.

OK, so that fixed everything. I really think I had to run the updater 3 times in total before everything worked. I could just be crazy though.

Thanks everyone for all the help again!