- Joined
- Aug 19, 2020
- RedCents
- 30,704¢
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.

Can you list them so Brainiac has more info to work with?Okay was able to log one toon in after 0'ing out a few more plugging from above.
Just tried that.. same thing , straight CTD no error nothing.. and that was just right click anywhere on group window, even without a group formedIve noticed if i Rt click on group window to change lead or roles i immediately crash w/ no information about it
I wouldn't have noticed this as I always have groupinfo unloaded. I hated the buttons, and wanted a smaller footprint, instead choosing to have those as regular buttonmaster hotkeys.Just tried that.. same thing , straight CTD no error nothing.. and that was just right click anywhere on group window, even without a group formed
Edit: Unloading MQ2Groupinfo will remove the crashing..
Edit2 : I am only having crashing on right click actions for this.. my buttons below (the come to me , mimic, follow) all still work, as do the custom ones i added in the row above it..
my bad, i didn't know about this thread but thank youyou don't upload the crash dmp, it is automatically sent
this is related to the test build - you can see in this thread about it.
the mq devs will be continuing to work on it
I wouldn't have noticed this as I always have groupinfo unloaded. I hated the buttons, and wanted a smaller footprint, instead choosing to have those as regular buttonmaster hotkeys.
I am patiently waiting for a newer update for MQ on test before I delve into it.
Well 0ing those 2 items out also helped allow me to get past the crashing. thanks for the help!!Okay was able to log one toon in after 0'ing out a few more plugging from above.
With the following - I was able to autolog in a toon using MQ2. It looks to be mq2easyfind and mq2itemdisplay.
mq2aaspend=1
mq2autoaccept=1
mq2autologin=1
mq2cast=0
mq2chatwnd=1
mq2easyfind=0
mq2eqbc=1
mq2dannet=1
mq2eqbugfix=1
mq2exchange=1
mq2itemdisplay=0
mq2map=0
mq2melee=1
mq2moveutils=1
mq2nav=1
mq2portalsetter=1
mq2rez=1
mq2targetinfo=1
MQ2Posse=1
mq2advpath=1
MQ2autoloot=0
MQ2Lua=1
MQ2GroupInfo=1
MQ2XTarInfo=1
mq2cleric=0
mq2CWTNBuffs=1
MQ2war=0
mq2shaman=0
mq2mage=0
mq2monk=0
I was able to log in and move around a single zone by changing these in the INI, but I still crashed when zoning into the guild hallOkay was able to log one toon in after 0'ing out a few more plugging from above.
With the following - I was able to autolog in a toon using MQ2. It looks to be mq2easyfind and mq2itemdisplay.
mq2aaspend=1
mq2autoaccept=1
mq2autologin=1
mq2cast=0
mq2chatwnd=1
mq2easyfind=0
mq2eqbc=1
mq2dannet=1
mq2eqbugfix=1
mq2exchange=1
mq2itemdisplay=0
mq2map=0
mq2melee=1
mq2moveutils=1
mq2nav=1
mq2portalsetter=1
mq2rez=1
mq2targetinfo=1
MQ2Posse=1
mq2advpath=1
MQ2autoloot=0
MQ2Lua=1
MQ2GroupInfo=1
MQ2XTarInfo=1
mq2cleric=0
mq2CWTNBuffs=1
MQ2war=0
mq2shaman=0
mq2mage=0
mq2monk=0
yeah same it allowed me to do a few things but not much. just gotta wait for the fixI was able to log in and move around a single zone by changing these in the INI, but I still crashed when zoning into the guild hall
Does anyone know if there's something about this build that would suddenly make Bitdefender flag and quarantine the program AND everquest? It never has before.
@direraven I am also a BitDefender user. I have always had to add exceptions to the Advanced Threat Defense settings. My exceptions are:
eqgame.exe (all three sliders and all three tick boxes under the AV slider)
settings.dat (all three tick boxes under the AV slider)
MacroQuest.exe (all three tick boxes under the AV slider and the Advanced defense slider)
******.exe (all three tick boxes under the AV slider and the Advanced defense slider)
The ***** is the number and letter exe found in the same folder as MacroQuest.exe
One interesting thing happened the other day on a new installation. The firewall blocked eqgame.exe so also check the firewall settings.
Be well.
I appreciate the response. It's just odd because it's never caused a problem before.
April 2, 2023:
- test: Fix WindowOverride implementation. Fixes crashes in MQ2Map, MQ2ItemDisplay, etc.
Same issue here. Everything works great, except class plugins are not using auto attack.Thanks for the quick fixes, you've saved me from the Sunday Scaries.
If you're still looking for bugs to exterminate, MQ2GroupInfo is crashing when I right click the group window.
CrashID: bda5bb71-03d6-4d1f-9930-79e9a287852f
Also having issues with class plugins not turning on auto-attack when they are assisting. No crashes from them and they seem to be working perfectly fine other than just not turning on attack.
Thanks again for all the time and effort!
I think some are ok. My dps classes on assist or chase mode seemed to be doing fine. My tank on the other hand was not auto attacking in manual, vorpal or puller tank modes. not sure about any others, i'd have to check again tomorrowSame issue here. Everything works great, except class plugins are not using auto attack.
Melee characters should not attack automatically in Manual mode. Vorpal isn't a tank mode, it's an assist mode, I'm honestly not surprised they don't do tank engagements (initiate combat for others to join in on) in vorpal mode. in puller tank, they would pull and return to camp once they detect they have something on xtarget, and then engage once both them and the mob in question is inside of the camp. It's my understanding there's some stuff that's still a little bit funky, but limited information other than "they don't auto attack". If others can collaborate your experience or give more information on situations where melee characters are engaging it would be helpful so that the exact cause can be tracked down.I think some are ok. My dps classes on assist or chase mode seemed to be doing fine. My tank on the other hand was not auto attacking in manual, vorpal or puller tank modes. not sure about any others, i'd have to check again tomorrow

Thanks for the responses, will try to take time to look at the test server stuff. Been up all night and physical therapy today, but will try to squeeze it in.
Melee characters should not attack automatically in Manual mode. Vorpal isn't a tank mode, it's an assist mode, I'm honestly not surprised they don't do tank engagements (initiate combat for others to join in on) in vorpal mode. in puller tank, they would pull and return to camp once they detect they have something on xtarget, and then engage once both them and the mob in question is inside of the camp. It's my understanding there's some stuff that's still a little bit funky, but limited information other than "they don't auto attack". If others can collaborate your experience or give more information on situations where melee characters are engaging it would be helpful so that the exact cause can be tracked down.
It's my understanding there's some stuff that's still a little bit funky, but limited information other than "they don't auto attack". If others can collaborate your experience or give more information on situations where melee characters are engaging it would be helpful so that the exact cause can be tracked down.
They don't use stuff because they don't think they're fighting since autoattack isn't being detected as on.Some more testing tonight:
I dont have the same issue with things not turning attack on, though I do have a 'hit this now' button i use about 3 seconds into any fight, which I now realize might have inadvertently fixed the problem pre-emptively for some classes.
Paladin - Will never turn autoattack on. Paladin will cast spells in the same priority it did before the patch. In groups, it wasnt using discs with timers except for Deflection. It did fire Valor Rage on burns, and it did keep maximum uptime on Repudiate, but seemed to only fire combat abilities and aa's with a toggle in the plugin (Beacon, Hallowed, Heroic Leap on cooldown, LoH if it was low) and did not use abilities, aa's, or item clicks otherwise (0 uses in 6 hours of: Reflexive Redemption, Righteous Censure, Inquisitors judgement, Epic 2.0, BP, diplomatic papers, Spire, timer 2 skills, Ageless Enmity, Vanquish the Fallen, Gift of Life, Hand of Piety). I can only guess that those are handled differently than the ones without toggles in terms of checking for their use. Interesting note, it will use bash, taunt and disarm on cooldown.
Eskay - Similar to paladin. Will cast, will send the pet in, will not attack, will not use discs other than deflection, will not use aa/combat ability/items with no specific toggle in the plugin.
Berserker - When set to assist, will turn attack on, and fire discs/combat abilities as expected. When set to any other mode, Berserker will stick to mobs and use blood pact, desperation, juggernaut surge, relentless/magnified frenzy, Discerning discipline, and Uuncanny resilience. It will use disarm, intimidate, frenzy, cry carnage and frothing rage when otherwise put into combat. It will not attack.
Beastlord - Beastlord is functioning like Berserker in a group/assist setting, where nothing is noticeably different. It also functions like SK in a tank mode, where it is more than happy to cast spells and send the pet in, but will not attack or use any offensive abilities.
Notes: I would see this every so often since starting to use these plugins with Dracoliche sized mobs in ToV/CoV.
yesAre we still waiting for the fix for Combat Auto Attacking?
Thank you very much I had been looking for an answer on here and couldn't find anythingcheck pages 15 and 16. known issue, and some work arounds.
This means you're on the test server, which the test macroquest build had some things that still needs fixing.Useing cwtn none of my characters are auto attacking with assist, they will use skills and spells but not attack, any help would be appreciated
