Problem - MQ2Melee locking clients up

[etherealmist]

So for the last couple compiles my clients seem to randomly lock up when starting macros, or just going into melee. Did some testing and when I disable MQ2melee the problem seems to go away. Did MQ2melee get updated recently?

 

[scotsbiker]

have found this problem with the latest release. however dont think its mq2melee, as works ok on 2 computers but not on my main.

2 warriors and 3 monks all lock up when in combat, but if i use /melee off they run ok ( but dont do anything).

i did load a couple of extras such as mq2medley and mq2Viewport so personally think its one of these, but cant check till tomorrow.

 

[etherealmist]

My loaded plugins are currently the default, plus what kissassist loads. The only other plugin besides those that I use is MQ2Autoaccept.

mq2rez
mq2cast
mq2autoaccept
maq2moveutils
mq2melee
mq2map
mq2labels
mq2hud
mq2exchange
mq2custombinds
mq2chatwnd
mq2bzsrch
mq2itemdisplay
mq2eqbc

- - - Updated - - -

I've used mq2medley as well, and mq2viewport (for a little bit), but those aren't currently loaded, and the problem is still there.

 

[Razkle]

trial and error, drop them 1 at a time until you find the culprit ( I do it by splitting the list) but 1 at a time works... I drop half, then if that works, add half of whats left, etc.... you will quickly find who is doing it....

or just tell eqgeek it is there, she can find broken shit faster then a bloodhound at a fox convension

 

[etherealmist]

Yeah I already did that, and MQ2Melee was the culprit :P

 

[mackal]

Toons MQ2Melee INI?

 

[Razkle]

sweet! thanks Etherealmist! I am happy you have narrowed it down, was just getting info to help.... ok now, in melee setting do the same thing, try a toon with NO info in the ini and lets see if it is the add or or a call inside your ini, I use melee all day on 40ish clients with no issues, so my gut tells me you either have a borked copy of mq2melee or a melee setting that is no longer valid causing this....

- - - Updated - - -

So for the last couple compiles my clients seem to randomly lock up when starting macros, or just going into melee. Did some testing and when I disable MQ2melee the problem seems to go away. Did MQ2melee get updated recently?

my client never paused when starting kiss before and in the last 5 or so compiles it stalls the client for about 3-5 seconds while it does whatever, but it always gets to kissing as soon as it loads, but I do also see the pause now...

 

[scotsbiker]

even with a blank fresh melee ini it still locks hence why im not sure its mq2melee

 

[Razkle]

hmmm mine is working perfect, this is a screenie of mine's file details... is your different?


- - - Updated - - -

mq2labels
mq2custombinds

are the only 2 plugins you are using that differ from mine, maybe one of those and melee are having an issue?

 

[Hihi]

KA has always "locked up" for 5ish seconds when I start it up. Is it not supposed to be doing that? :P

 

[etherealmist]

Yeah, I started getting the kiss lockup about 5 months ago too. Like in June? Until about a week ago, (before the new update), my clients just lock up permanently until I issue a BCAA //end and eventually they all unlock after about 5-20 minutes....(there are small splurts of time where they unlock for a split second).

My ini is default.

My MQ2melee properties is exactly the same as Raz

 

[Razkle]

when I get to a point where shit is just WIERD I back it all up, run a FRESH install of mq2 and slowly add shit back in....

- - - Updated - - -

about twice a year I have to do that to get stuff working again, mostly with looting and pulling but ya never know

 

[DriveCrash]

Since MQ2Melee relies on MoveUtils, could there be a config problem in the MoveUtils.ini file in the root?

You said ending EQBC free's up the clients.. perhaps you have a feedback loop in your EQBC system? I don't run EQBC at all, and have never experience any major hangs other than the 1-3 second pause when you first fire up KA.

 

[etherealmist]

Okay so, my process so far, was to completely restart from scratch. I just completely reformatted my computer a couple days ago partially because of this issue, partially because I wanted to rebuild my raid. I typically let kiss load whatever plugins it needs on a fresh install. So my first action was to do that. Everything loaded fine. I readded my inis that I have saved on this site, everything still worked. Loaded up EQBC, went to town boxing. I logged off all my clients because I needed to redo my ISBoxer config, started everything back up, started KISS. Everything locked up. So at this point I have a fresh install (even everquest, as I redownloaded that), only extra plugin loaded is EQBC, and everything worked after loading. Froze once I restarted the clients and started KISS again. I force closed everything, disabled MQ2Melee, starteded kiss again, and everything worked....

Okay so, just so we're clear, it isn't just kiss. I have another macro I run thats for boxing, same thing. I went to use the buystuff.mac, same thing, everything locked up (that doesn't even use MQ2melee does it? lol)

I dunno what else I can do. It might not even be MQ2Melee, but disabling and re enabling it seems to fix it? Hell, I've started just deleting my Macroquest.ini and using the defaults every time I load just to be sure :P (oddly enough, this works!)

 

[scotsbiker]

i deleted my ini and loaded old one and everything is working fine. below is the plugins i have loaded and working

[Plugins]
mq2aaspend=1
mq2autoaccept=1
mq2autoforage=1
mq2autologin=1
mq2cast=1
mq2chatwnd=1
mq2debuffs=1
mq2eqbc=1
mq2eqbugfix=1
mq2events=1
mq2exchange=1
mq2hud=1
mq2itemdisplay=1
mq2map=1
mq2melee=1
mq2moveutils=1
mq2nonagwindows=1
mq2notepad=1
mq2posse=1
mq2raidutils=1
mq2rez=1
mq2spawnmaster=1
mq2tooltip=1
mq2twist=1

 

[Razkle]

last year I had an issue like this over looting and the "fix" was a bad ini, I renamed the old ini, ran the mac to create a fresh one, then I opened the old broken one and only copied the stuff inside the ini. I found it was a file that was actually borked. But yes over time shit dies..... be prepared

- - - Updated - - -

I do think aaspend is causing crashes though! of all my clients the ones AAing with BRUTE are wonky and crash daily and randomly

 

[mackal]

last year I had an issue like this over looting and the "fix" was a bad ini, I renamed the old ini, ran the mac to create a fresh one, then I opened the old broken one and only copied the stuff inside the ini. I found it was a file that was actually borked. But yes over time shit dies..... be prepared

- - - Updated - - -

I do think aaspend is causing crashes though! of all my clients the ones AAing with BRUTE are wonky and crash daily and randomly

Go look at the changes eqmule pushed to the main releases today, it might be related (as in they're working on writing one that uses the new stuff since the old one is crashing :P) I also released my own version of an AA plugin using the new functions

 

[Razkle]

Go look at the changes eqmule pushed to the main releases today, it might be related (as in they're working on writing one that uses the new stuff since the old one is crashing :P) I also released my own version of an AA plugin using the new functions

can you share your aaspend version here? pretty please....

 

[mackal]

can you share your aaspend version here? pretty please....

It requires the newest MQ2 updates which RG compile doesn't have yet.