Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

Having the same issue for my /cwtn plugin toons. The other ones seem to be working fine.---------------------------
EverQuest Crash Detected
---------------------------
A crash dump has been written to:
C:\Users\harje\AppData\Local\VeryVanilla\MacroQuest\Release\Logs\Dumps\reports\eqgame_20240519_131427.dmp
---------------------------
OK
---------------------------
I see there is a patch :View attachment 61712
Are you running the latest version? I did NOT yet patch, but I did load up two characters (with plugins).
I was able to turn off my /mq2cleric in the ini and it loads up without the crash.yes.
for some reason the plugin issuing the eq command/xtarget auto onis causing mq to crash (which i can't replicate thus far --- I wonder if those crashing are using the new eq ui engine)
yes, if mq2cleric is unloaded then mq2cleric wouldn't be able to issue the everquest commandI was able to turn off my /mq2cleric in the ini and it loads up without the crash.
/xtarget auto on so since that is what is causing the crash, not doing the thing that crashes would stop it from doing that crashi didnt do the update and is fine here logged um all inI can log in Bard's just fine but anyone toon crashes when I try to log them in.
you cannot 'un-update' or roll back. Just hang tight, when the Crash IDs are posted and sent to the devs, they can see the issue with more info and fix it when they can. Sic is aware of the issue, so all is good. Before you know it, you'll see a red bot post with an update.How do you Un update? Everything was perfect last night until the update. Did EQ update also, so need to update there to?
Thank youyou cannot 'un-update' or roll back. Just hang tight, when the Crash IDs are posted and sent to the devs, they can see the issue with more info and fix it when they can. Sic is aware of the issue, so all is good. Before you know it, you'll see a red bot post with an update.
yes.
for some reason the plugin issuing the eq command/xtarget auto onis causing mq to crash (which i can't replicate thus far --- I wonder if those crashing are using the new eq ui engine)
It's the toons using the class plugins, for me it's warrior and cleric
Sic I can't get to the point where I choose the old UI it crashes way before that.yes.
for some reason the plugin issuing the eq command/xtarget auto onis causing mq to crash (which i can't replicate thus far --- I wonder if those crashing are using the new eq ui engine)
i, so far, can't replicate it with new/old ui on multiple pcs - self compiling or rg build.Sic I can't get to the point where I choose the old UI it crashes way before that.
Thanks as always Sic!i, so far, can't replicate it with new/old ui on multiple pcs - self compiling or rg build.
i imagine it is something that @brainiac might have to look at since it happened with the changes from lasdt night
I logged in each toon and made sure the new (blah) UI was off. That didn't fix it. /shrugyes.
for some reason the plugin issuing the eq command/xtarget auto onis causing mq to crash (which i can't replicate thus far --- I wonder if those crashing are using the new eq ui engine)
/xtarget auto on.i, so far, can't replicate it with new/old ui on multiple pcs - self compiling or rg build.
i imagine it is something that @brainiac might have to look at since it happened with the changes from lasdt night
yes.
for some reason the plugin issuing the eq command/xtarget auto onis causing mq to crash (which i can't replicate thus far --- I wonder if those crashing are using the new eq ui engine)
Cool deal.well - it turns out this is mq2xassist related (a plugin that later-on cwtn plugins unload due to conflicting behavior anyhow).
in the meantime you can skip the crashes by going in your macroquest.ini and turning mq2xassist to =0
I imagine either mq2xassist or mq's handling of "overtaken" aliases will have an update later
This indeed allowed me to log in, thanks man.well - it turns out this is mq2xassist related (a plugin that later-on cwtn plugins unload due to conflicting behavior anyhow).
in the meantime you can skip the crashes by going in your macroquest.ini and turning mq2xassist to =0
I imagine either mq2xassist or mq's handling of "overtaken" aliases will have an update later
not to be a jerk off, but make sure to save the change when you change it to 0, it worked for me.I can log in Bard's just fine but anyone toon crashes when I try to log them in.
