-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
Release MQ2Heals
- Thread starter jimbob
- Start date
I was excited to see a fix posted yesterday, but I'm still having the same results. Issuing a /heals settings upon entering game on my cleric shows zerkerhealpoint at 85. I then issue a /heals zerkerhealpoint 70 and do a settings check again and it reflects 70. Opening my clerics INI, it shows 70. If I then unload and reload the plugin, then issue a settings command, once again shows it at 85. But it did not change the setting in the INI file that I still have open in Visual Studio. It's acting like it's not reading the INI file on load up?
On another note, for the first time ever, it put my cleric on her mount!
On another note, for the first time ever, it put my cleric on her mount!
I'll look at it some more. I found one place where it was saving the wrong setting. Maybe it's reading the wrong setting too. I'll let you know what I find.
Edit: I found the problem. It was just using the default instead of reading from the .ini. I'll get it updated soon.
Last edited:
I'm back.... sorry!
A couple things I've noticed with the current version. The not saving ZerkerHealPoint is back, it now reverts back to 85 everytime I relog my cleric. And if full mana, I have to pause the plugin to be able to camp, cleric immediately stands and cancels the /camp otherwise.
Always appreciate all your hard work!
A couple things I've noticed with the current version. The not saving ZerkerHealPoint is back, it now reverts back to 85 everytime I relog my cleric. And if full mana, I have to pause the plugin to be able to camp, cleric immediately stands and cancels the /camp otherwise.
Always appreciate all your hard work!
The best, but I am biased.
So I'm new to the whole automation thing. So far I've played around with Kissassist and I like it in groups. But I was thinking to find some simpler and not dependent on having a MA for my shaman for healing on raids. Like if all I really wanted him to be focused on would be healing. I just stumbled across this plugin and read though this thread and can see people saying they are using it for their shaman as well. I was just curious if there was a good way to get the specifics on which settings are controlling which shaman spells/aa? So for a lvl 90 shaman I would guess the group heals would be Qirik's recourse and ascendants intervention. It just wasn't as clear as to which would then control Qirik's mending and reckless mending, since reckless is both faster cast and a bigger heal. I believe I saw in this discussion that this will also use the soothsayer's aa and that was under the clicky heals? Kissassist you would specify which xtar slots to check for healing, does this just check the health and heal any xtar slot that's been assigned to an out of group character?
Yes, this will play your shaman and XTarget heal (or group heal, or both). I don't know how to play a shaman (not well anyway), so if you have ideas for improvement, I am open to them. I know people used to use this a ton for Clerics, and I use it for my cleric, druid, and shaman in group settings. It does look at health percentage to determine who needs to be healed when.
This was working till I updated MQ this morning,,,,
Now I've gotten this 3 times in a row
Now I've gotten this 3 times in a row
Code:
---------------------------
EverQuest Crash Detected
---------------------------
MacroQuest caught a crash:
Process ID: 9656
Version: 3.1.0.2393
Location: C:\Users\dvrea\Desktop\MQNext\Plugins\mq2heals.DLL+000000000000657D
CrashID: 80bc28f5-58c2-479a-a065-0ff84c5afb5e
You can either:
* [RETRY] Continue execution and hope for the best.
* [CANCEL] Write a crash dump and terminate EverQuest.
Copy the contents of this dialog to your clipboard by pressing Ctrl+C
---------------------------
Retry Cancel
---------------------------Sorry about that, but I do have a fix. I'll push it up.This was working till I updated MQ this morning,,,,
Now I've gotten this 3 times in a row
Code:--------------------------- EverQuest Crash Detected --------------------------- MacroQuest caught a crash: Process ID: 9656 Version: 3.1.0.2393 Location: C:\Users\dvrea\Desktop\MQNext\Plugins\mq2heals.DLL+000000000000657D CrashID: 80bc28f5-58c2-479a-a065-0ff84c5afb5e You can either: * [RETRY] Continue execution and hope for the best. * [CANCEL] Write a crash dump and terminate EverQuest. Copy the contents of this dialog to your clipboard by pressing Ctrl+C --------------------------- Retry Cancel ---------------------------
Last edited:
Was looking at what Faycite Shards I would need to get/uprade for LS and noticed the spell list that pops up when unloading/reloading mq2heals on my cleric.
It doesn't appear to be updated for LS? Or is there a place that I'm supposed to be configuring this?
It doesn't appear to be updated for LS? Or is there a place that I'm supposed to be configuring this?
Those are just automatic spells detected by some code PeteSampras donated to me. They'll only get used if the class is not supported (not a cleric, druid, or shaman), or if none of those classes' expected spells are memorized.
Basically, for a cleric, you can ignore that.
I currently am experiencing an issue with MQ2heals:
I've tried unload / load, but it persists and internet search isn't bringing me to anything useful for a fix.
When loaded, I get red text:
DoCommand - Couldn't parse '/casting "${Spell[Avowed Remedy].RankName}" -targetid¦25410
I assume it's a DoCommand issue? and something must be wrong with the macro somewhere... any help?
I've tried unload / load, but it persists and internet search isn't bringing me to anything useful for a fix.
When loaded, I get red text:
DoCommand - Couldn't parse '/casting "${Spell[Avowed Remedy].RankName}" -targetid¦25410
I assume it's a DoCommand issue? and something must be wrong with the macro somewhere... any help?
/plugin mq2cast load
super star! Thanks.
jimbob updated MQ2Heals with a new update entry:
10/30/2025
Read the rest of this update entry...
10/30/2025
Commits
Read the rest of this update entry...