• 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! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
MQ2Shaman

Plugin - MQ2Shaman 3.1.52471.11

I am hoping a moderator can help me. New to the CWTN Class Plugins. On EMU Project Lazarus. Have RedGuides Very Vanilla. Have paid for MQ2Shaman, MQ2War, MQ2Monk, MQ2Rogue, MQ2Cleric. Have used "/plugin mq2shaman load" to try to load (and the same for the other classes) and I get the error "plugin 'mq2shaman' could not be loaded: loadlibrary failed with error 0x0000c1: %1 is not a valid win32 application." I have read on other posts that you state that the error is because I am out of date and need to patch. I used RG Loader to 'reinstall' veryvanilla... but I did not see a way to patch. What am I missing?
and they "where" free as is for EMU's, didnt have to buy =-(
 
it was not on emu that he used cwtn plugins. IIRC at the time he was on Rizlona doing those videos.
 
So this video was posted Oct 1, 2022 and he was using CWTN Plugins in the Video; then, on the forum post linked above Sic promised to release CWTN for EMU eventually.... was there a patch or update at that time that broke things? In other words, how was it working in this video and then not working now?
Read the link I posted (specifically the last line of Sic's post) - They work on Lazarus free of charge with Level 2, on the Legacy MQ build, not the new one - it tells you how to go back to Legacy
 
So this video was posted Oct 1, 2022 and he was using CWTN Plugins in the Video; then, on the forum post linked above Sic promised to release CWTN for EMU eventually.... was there a patch or update at that time that broke things? In other words, how was it working in this video and then not working now?
Please see >>> Getting Started with CWTN plugins! (Movement, UI Window, Clickies, Pulling, ETC) Check Here First! <<<

did you click the link that was shared above or the info in this "check here first"? It is explained


it was not on emu that he used cwtn plugins. IIRC at the time he was on Rizlona doing those videos.
He is talking about the person in the vid (not me) who was using the cwtn plugins on the legacy mq2 build, not the MQ build
 
Hi guys so a couple of things I've been seeing looking at parses/trying to chase down behavior-wise that could be potential feedback/help isolate things not working as intended etc.
1) Previously mentioned shamans not casting their aura (Pact of the Wolf) in raid format: With raid mode turned on the shamans will not recast their Aura, they will if in a raid but without raid mode turned on
2) Recourse Grp Heal Line: Both in raid and grp setting the shamans are not casting this spell at all but are loading it in your default load outs. Across nearly 4 hrs of heavy AE heavy content shamans never once cast the spell despite grps being hit heavily and this isn't just due to squall healing covering it (I'll get to this as part of another point)
3) AA Intervention (Soothsayer's Intervention) not showing up on spell cast parse data for shamans with raid mode turned on but is showing up on spell count parses (of much shorter duration) if raid mode is turned off.
4) Consider building the shaman BP line into the plugin itself, with the restrictions of the healgroup addclicky function (HealthGroup - Used when a group member is below 60 health (currently not adjustable, part of future updates), the functionality of this ability is somewhat limited within the plugin and also works functionally the same as both the intervention spell and intervention AA
5) Can a toggle for the Call of the Ancients AA (Healing totem) be added, this would bring it in line with the functionality you have done with the cleric plugin for their equivalent (Exquisite Benediction/Ward of Purity, Toggle on Cleric plugin is "UseWardAA). If not is it possible to move it so it's not part of the prepackaged burn setup?
6) Forceful Rejuvenation: Currently if the shaman goes into Burn mode it instantly pops Forceful rejuvenation even if all spell gems are currently unlocked, possible to add a slightly more intelligent usage or remove it from the burn so people can craft a LEM/React/Event of their own to adjust the usage?
7) Consider adding Rabid Bear AA line into the triggered burn. This ability increases melee benefits to the shaman (relevant for those using usemelee), adds a proc for the shaman that does a DD plus heals for 15k to everyone in the group, and adds a stacking HOT on the shaman
8) Adding in Spiritual Channeling usage to the shaman. This line works like Bloodmagic which is implemented in the necro plugin (and potential feedback changes as well could be relevant here). Ideally, could this be implemented either with an adjustable % that the user can set (Necro is currently hardcoded and honestly is too low) or if not instead be implemented into the burn when things like heavy dot casts which chew mana heavily for shamans (and for necros) to maximize the effectiveness? An example for usage with shamans or necros in a group setting would be an overpull with a large number of mobs in camp not being mezzed and the group being manually steered by the tank, trigger burns, and then cycle through mobs getting the best dots onto each one before cycling through to apply the next. In these situations the mana draw down is heavy, alternative solution would be to create a toggle allowing users to build their own preferred functionality around these abilities to fit their playstyle.
9) Currently, if Twinheal isn't up the squall line isn't cast at all. This can be problematic (especially since the recourse line also isn't casting) in a scenario where AE's are happening but you may want to hold dps for a specific event mechanic by having the MA target themselves. In this scenario, no squall line group heals are being cast because the twinnuke can't be cast. In group content, the twincast additionally can be substantial over heal and for some people could be dropped entirely to allow loading of an alternative spell in byos sets (e.g. another dot or other alternative spell option).

If you have any questions or unsure of something I'm more then happy to discuss, clarify or try to provide more data.
 
Last edited:
I'm not really super interested in a back and forth with you about these things. the last time I pm'd you, you just ignored it entirely. I did offer you a refund after you spent some time being very generous with your opionions on the plugins and about my person. I'll give each of your points genuine consideration, but I am not interested in a back and forth about it at all. So if each of us can just kindly consider this a "i've read it and will take a look" and move on. otherwise it is going straight to fippys.

I do appreciate the writeup and your explainations

1 - as i likely mentioned previously, there is nothing at all about raidmode for usage of pact of the wolf, and i've not been able to reproduce it, if i can, i'll take a look at it --- I tried before and I was unable to reproduce it

2 - i can take a look at adjusting when this fires, but it does fire as it is currently intended. since we need to check for forbearance and stacking issues, some of it requires toons that would be checked to be local toons on cwtnbuffs so we know if they have it or not, also another reason to make sure that toons don't have full buffs with "shadow of nonsense" type fluff, if they weren't local toons on cwtn buffs we would say "they already have this"

3 - set to fire on group MA at 30 health, I've been thinking about going back and changing some of these things to allow checking raidma 1, 2, and 3, this would be one of them since it is a "target group" ability, but as of now it is just MA at 30 health.

4 - k

5 - yes, that makes good sense and would be in line with other things like you mentioned

6 - you would required to have mobs on xtarget, be burning, and progressivespell (dissident roar) on cooldown. There's nothing to indicate this isn't working like that - and the "must be burning and must have targets on xtargets" would have to be met before the "is dissident on cooldown" would fire those things are impossible to be not working as described - if something changed and the "is this spell on cooldown" is having issues i'll take a look at it, because it would affect the other plugins that use forceful rejuvenation

7 - we already use rabid bear, you must be meleeing.

8 - I do know how this works, I intentionally left it out, but i can revisit it at some point --- to the point about necros, if 80 is "hardcoded and too low" then adjust the manaAAConversion which is adjustable and defaulted at 80 health

9 - this is inaccurate. the "spammy" non-health check'd fires when you have twincast, but there is another "if more than 2 members are 75% or lower health then and twincast is available, fire" this one only has a group MA and self check for LoS, but I can add a Raid MA check first as well. have zero intention of dialing back twincast usage - not everyone is eltai86's super pimpted out mega raid groupteam of awesomeness, try and remember that.

any of the things that you say aren't working, that i say are working i will spend the time to double check - as i always do.
 
An option to still have spammy Squall without the Gift nuke would be handy tbh. The old TBL one kinda needed twincast since it wasn't upgraded for a while, but the new squall heals a butt load without twincast. Would free up a spell gem for something else ;)
 
An option to still have spammy Squall without the Gift nuke would be handy tbh. The old TBL one kinda needed twincast since it wasn't upgraded for a while, but the new squall heals a butt load without twincast. Would free up a spell gem for something else ;)
no sorry about that, don't plan on making that change because we already allow to use two gifts so we can keep twincast up

they are a 10 (squall) and 12 (hybrid) second reuse and in heal/hybrid we actually use 2 gifts so we can keep twincasting
 
I do appreciate the writeup and your explainations

1 - as i likely mentioned previously, there is nothing at all about raidmode for usage of pact of the wolf, and i've not been able to reproduce it, if i can, i'll take a look at it --- I tried before and I was unable to reproduce it

2 - i can take a look at adjusting when this fires, but it does fire as it is currently intended. since we need to check for forbearance and stacking issues, some of it requires toons that would be checked to be local toons on cwtnbuffs so we know if they have it or not, also another reason to make sure that toons don't have full buffs with "shadow of nonsense" type fluff, if they weren't local toons on cwtn buffs we would say "they already have this"

3 - set to fire on group MA at 30 health, I've been thinking about going back and changing some of these things to allow checking raidma 1, 2, and 3, this would be one of them since it is a "target group" ability, but as of now it is just MA at 30 health.

4 - k

5 - yes, that makes good sense and would be in line with other things like you mentioned

6 - you would required to have mobs on xtarget, be burning, and progressivespell (dissident roar) on cooldown. There's nothing to indicate this isn't working like that - and the "must be burning and must have targets on xtargets" would have to be met before the "is dissident on cooldown" would fire those things are impossible to be not working as described - if something changed and the "is this spell on cooldown" is having issues i'll take a look at it, because it would affect the other plugins that use forceful rejuvenation

7 - we already use rabid bear, you must be meleeing.

8 - I do know how this works, I intentionally left it out, but i can revisit it at some point --- to the point about necros, if 80 is "hardcoded and too low" then adjust the manaAAConversion which is adjustable and defaulted at 80 health

9 - this is inaccurate. the "spammy" non-health check'd fires when you have twincast, but there is another "if more than 2 members are 75% or lower health then and twincast is available, fire" this one only has a group MA and self check for LoS, but I can add a Raid MA check first as well. have zero intention of dialing back twincast usage - not everyone is eltai86's super pimpted out mega raid groupteam of awesomeness, try and remember that.

any of the things that you say aren't working, that i say are working i will spend the time to double check - as i always do.
1) Alright, I have been able to recreate this across multiple machines and multiple shamans include new to machine shamans. It specifically only occurs for me when in a raid and the raidmode on setting is turned on, if they are in a raid but raidmode is turned off they will still cast the aura.
2) Alright that explanation alone explains why I'm not seeing it happen as I run my healers on 1 machine and my melee dps on a different machine them checking for buffs would be the reason I wasn't seeing it get cast. Might have to shift my load up configurations somewhat to work around this.
3) Alright that explains the behavior I've been seeing then and at least gives me a semi-workaround idea for usage in its current form, in raidmode it would still look for the check on a group MA being at 30% health yes?
4/5) Awesome
6/7) I'll dig on these a bit more and see if I can get more refined data to share.
8) Thanks for considering adding this in to the shamans. I'll try tweaking on that setting, I've just noticed them casting/using it at much lower mana values. I'll dig into this more and see if I can get more data.
9) Just to make sure I am understanding the second check usage you described, it will only fire that second check if there is a grp MA set and 2 or more group members are under 75% and twincast is available or did you mean that there is a second check that exists that fires if there is a grp MA set and 2 or more group members are under 75% regardless of twinheal status? The scenario I've run into this isn't a problem with it being spammy in its cast but casting no squall at all because if the RMA has themself targeted the shamans don't get the twinheal trigger. As far as the gearing aspect it is something I am aware of, which I completely understand isn't the case for everyone.
 
appreciate the pm followup

1. me, nor a few others (at least 5 folks) can't replicate that specifically, but spending more time with it it did bring up a point that isn't "it doesn't recast the aura if it doesn't have the aura". it brought up "if a group member who is on cwtnbuffs does not have the group buff, or somehow the shaman doesn't have the solo buff but does have the aura, it won't cancel the aura and recast it so everyone gets a fresh group/solo buff". Unfortunately, EQ won't let you cast the aura over itself, so you also have to cancel the existing aura to recast. I have a resolution for this.
The cool thing with shaman aura is that it'll go on a group member wherever - unfortunately after a death and respawn it doesn't always apply like it is supposed to

2. yeah multi-PC is still not something directly supported, we were originally going to incorporate dannet, but was under the impression a new and improved dannet system was coming so we were waiting on that - there are, however, some work arounds if this is an absolute DIRE situation for you, i can pm you

3. the update will check MA, RaidMA you have selected, then raidma 1, 2, and 3 (yes redundant on the raidma you have selected)

4. can you give me a rough circumstance you would use this and how you imagine the plugin handling it- in place of an additional emergency like soothsayer situation?

5. yep np

6. testing this it appears to function as expected. if progressive spell has a timer, and we're fighting and burning - we'll hit it to squeeze out another progressive spell once we no longer have the buff

7. yep

8. the necro uses it after death bloom and BM specifically we only use while fighting (so as not to waste). for shm we'll use it while fighting and be adjustable in the same manner except it will be during burns only since it is a 20m reuse and we only have the 1

9. the "check for MA" means it'll check and try and cast it on the MA first, and if they don't have LoS or some other reason they'll cast it on themselves instead. understood about the twincast / giftdd part. We should only be casting gift if the MA's target is an NPC, so that can get fixed. I suspect being in hybrid/heal loadout and the adjustment for recourse to stay up during combat the same as renewal does, will hopefully be enough. I'll give this some more thoughts
 
appreciate the pm followup

1. me, nor a few others (at least 5 folks) can't replicate that specifically, but spending more time with it it did bring up a point that isn't "it doesn't recast the aura if it doesn't have the aura". it brought up "if a group member who is on cwtnbuffs does not have the group buff, or somehow the shaman doesn't have the solo buff but does have the aura, it won't cancel the aura and recast it so everyone gets a fresh group/solo buff". Unfortunately, EQ won't let you cast the aura over itself, so you also have to cancel the existing aura to recast. I have a resolution for this.
The cool thing with shaman aura is that it'll go on a group member wherever - unfortunately after a death and respawn it doesn't always apply like it is supposed to

2. yeah multi-PC is still not something directly supported, we were originally going to incorporate dannet, but was under the impression a new and improved dannet system was coming so we were waiting on that - there are, however, some work arounds if this is an absolute DIRE situation for you, i can pm you

3. the update will check MA, RaidMA you have selected, then raidma 1, 2, and 3 (yes redundant on the raidma you have selected)

4. can you give me a rough circumstance you would use this and how you imagine the plugin handling it- in place of an additional emergency like soothsayer situation?

5. yep np

6. testing this it appears to function as expected. if progressive spell has a timer, and we're fighting and burning - we'll hit it to squeeze out another progressive spell once we no longer have the buff

7. yep

8. the necro uses it after death bloom and BM specifically we only use while fighting (so as not to waste). for shm we'll use it while fighting and be adjustable in the same manner except it will be during burns only since it is a 20m reuse and we only have the 1

9. the "check for MA" means it'll check and try and cast it on the MA first, and if they don't have LoS or some other reason they'll cast it on themselves instead. understood about the twincast / giftdd part. We should only be casting gift if the MA's target is an NPC, so that can get fixed. I suspect being in hybrid/heal loadout and the adjustment for recourse to stay up during combat the same as renewal does, will hopefully be enough. I'll give this some more thoughts
1) So strange, I'll try and think of a way to capture the behavior. Friend who also uses the shm plugin saw the exact same behavior off of his shaman as well. Following a total wipe, they don't recast it and when i do a "/dgrae /shm raidmode off" they all instantly will cast it and then i put them back into raidmode. Thats the workaround I've been using for the last several months since I discovered it.
2) Yep, knew you guys didn't support multipc buff recognition but also something I didn't even think about as the potential trigger for the non-casting I was thinking of is with itself so in my head would have just checked the shamans buff state and gone from there.
3) Adjusting this to trigger off the raid MA wouldn't make sense as then it may misfire when the group doesn't need it at all and would do nothing for the raid MA on top of it if they were out of group. In stuff I've written for usage I actually have it just check for any group member below a threshold and use it in that use case, in a grouping situation this is predominantly going to be the tank but also covers for situations where another group member may get wacked for some reason (bard/shm for example on incoming pull). For time being, I think the workaround for me in a raid is going to just need to set group MA's as the lowest max hp group member or biggest aggro whore in the group (I'll have to have a think on which might work better).
4) Basically what I have looked at doing is looking at if anyone in the group is at the declared emergency heal threshold and then have it check through the Spell>BP>AA lineup if they are ready and to use it basically in an if else checkdown for priority. I use the spell line first (3 min recast) as it shares the same cooldown as AA (also 3 min recast) but can only be cast when spells are off the global cooldown, then I have it check BP (10 min reuse so get that timer started first) which can be fired when other spell based heals aren't available then AA for the same reason. If you need more clarity on my usage thoughts let me know and happy to try and clarify.
6) Alright, I'll do a little testing on my end and see if it was just a fluke the time I saw it or something more going on.
7) Just tested off firing shm burns manually with usemelee on, single mob in camp, assisting tank ma. Rabid bear did not fire for me. It fired off Dampen Resistance, Focus of Arcanum, CAll of the Ancients, Spire of Ancestors, Silent Casting, Fleeting Spirit and Spiritual Blessing.
9) I'd need to look and see if it's actively trying to cast the twin nuke or not but I know that if there isn't an NPC target by the MA it won't land the twinheal portion which then has it skip using squall entirely. I run all the shms in a heal or where I put the shms to more dps hybrid with a byos spell set that drops a few things that are redundant in raidmode with multiple shamans on the plugin (melancholy, growth and coalition) as well as Ander's Bite since it just is weak overall comparatively. The addition of recourse firing would likely do enough most of the time but hard to say with 100% certainty until I go test it out
 
1. yeah dunno
3. I haven't gone through it yet - was just talking out loud, we wouldn't want to fire on someone who didn't need it - I didn't recall if intervention was target or self group only, but even then, should probably save it for our own group anynow

4. cool thanks for the explain i'll take a look and see what makes sense.

7. dunno, only thing i can think of is that it is checking if your attack is on, which means if you have a bad UI that doesn't reflect that information correctly, it can cause MQ issues.
image.png


9. (dont forget usegrowth is an option, usealliance is an option)
 
3) Totally get it, the intervention line and the BP are all self group only heals.
4) No worries and if you have any follow up questions can shoot me a message.
7) Hmm, I basically use a default minus buff/song window. What would be the equivalent TLO check so I can see if that debugs it.
9) I know :) Just was listing some of the tweaks I do just in case that created any of the behavior I was seeing.
 
3) Totally get it, the intervention line and the BP are all self group only heals.
4) No worries and if you have any follow up questions can shoot me a message.
7) Hmm, I basically use a default minus buff/song window. What would be the equivalent TLO check so I can see if that debugs it.
9) I know :) Just was listing some of the tweaks I do just in case that created any of the behavior I was seeing.
well the attack window is your personal window that flashes red when your auto attack is on
 
Sic updated MQ2Shaman with a new update entry:

7/19/2023

- DissidentRoar is now "Progressive Spell"
- for non-twincast usage of squall we will now check RAMA
-- this is the same as the group check with more than 2 members fewer than 75% health
- Made a work around for the EQBug where the shaman has their aura up, but it didn't apply to a group member
-- as with usual group buff stuff, this requires the toon on cwtnbuffs
- will now check all group for usage of soothsayer (aa), intervention (spell)
- added direct usage of shaman BP (that has...

Read the rest of this update entry...
 
With this patch my shaman is stuck in a loop of casting "Using AA :Pact of the Wolf"
I'm running a warrior, shammy, cleric, bard, mage x2 using KA and CWTN plugins.
Shammy does nothing else when the plugin is un-paused.

I have no clue where to even start to look for the issue. Can anyone point me in the right directions please?

Thanks,
BB~
 
Last edited:
With this patch my shaman is stuck in a loop of casting "Using AA :Pact of the Wolf"
I'm running a warrior, shammy, cleric, bard, mage x2 using KA and CWTN plugins.
Shammy does nothing else when the plugin is un-paused.

On dicord there have been a few users with issues there - for one, checking their blocked spells helped (did not only have illu but also effect blocked), the other had <100 toons with 120 in group, maybe that also causes issues. However, check if you are really casting that pact AA or if you are using "Improved Pure Spirit" AA.
 
On dicord there have been a few users with issues there - for one, checking their blocked spells helped (did not only have illu but also effect blocked), the other had <100 toons with 120 in group, maybe that also causes issues. However, check if you are really casting that pact AA or if you are using "Improved Pure Spirit" AA.
i didn't make any changes with cures, so if there is an issue there it might be mq or even EQ. but i'd like to see where it is actually casting it in the shaman window while usecures is off like stated on discord, because that doesn't sound like mq2shaman is doing it

With this patch my shaman is stuck in a loop of casting "Using AA :Pact of the Wolf"
I'm running a warrior, shammy, cleric, bard, mage x2 using KA and CWTN plugins.
Shammy does nothing else when the plugin is un-paused.

I have no clue where to even start to look for the issue. Can anyone point me in the right directions please?

Thanks,
BB~
make sure your aura window is open is the only thing that comes to mind, and if that is causing it, the plugins will have to make sure to open the aura window at least once
 
can't reproduce the described bug.
1. clicked off the aura on non shaman, shaman recasted.
2. blocked it on non shaman, shaman rightly ignored.
2.1 clicked off shaman in the previous step, shaman recast for themself.
2.2 removed from blocked spell list, shaman recasted (as seen in snip).

image.png


I tried with shammy groups, I had someone else test with multiple shammy groups

would need more information as it appears working as expected
 
can't reproduce the described bug.
1. clicked off the aura on non shaman, shaman recasted.
2. blocked it on non shaman, shaman rightly ignored.
2.1 clicked off shaman in the previous step, shaman recast for themself.
2.2 removed from blocked spell list, shaman recasted (as seen in snip).

image.png


I tried with shammy groups, I had someone else test with multiple shammy groups

would need more information as it appears working as expected
Not that I'm very technical so take this with 2 grains of salt-

Looks like it's on the EQ end. I deleted all my toons blocked buffs manually in the EQ folder <toonname>_<server.ini> under the [BlockedSpells] section.

Then re-blocked the pact of the wolf in game and it's working with no issues on all toons now.

Yay! I don't know what I'm doing but having fun and it works.

Thanks for checking into it guys.

BB~
 
can't reproduce the described bug.
1. clicked off the aura on non shaman, shaman recasted.
2. blocked it on non shaman, shaman rightly ignored.
2.1 clicked off shaman in the previous step, shaman recast for themself.
2.2 removed from blocked spell list, shaman recasted (as seen in snip).

image.png


I tried with shammy groups, I had someone else test with multiple shammy groups

would need more information as it appears working as expected
Narrowed it down.

1. It was only occuring with one or two 103 level toons in the party.
2. The shaman is applying aura 51377 to the 103 toons, and 53780 to the 120 toons.
3. When blocking 51377 on the 103 toons, issue still occurs.
4. When blocking 53780 on the 103 toons, issue no longer occurs.

The shaman seems to want to reapply the aura AA if one or more of the party members aura buff ID is not equal to 53780.
 
Narrowed it down.

1. It was only occuring with one or two 103 level toons in the party.
2. The shaman is applying aura 51377 to the 103 toons, and 53780 to the 120 toons.
3. When blocking 51377 on the 103 toons, issue still occurs.
4. When blocking 53780 on the 103 toons, issue no longer occurs.

The shaman seems to want to reapply the aura AA if one or more of the party members aura buff ID is not equal to 53780.
This wasn't the case for me. I've deleted the blocked spell data but all toons were 120 except a level 119 cleric.
 
Not that I'm very technical so take this with 2 grains of salt-

Looks like it's on the EQ end. I deleted all my toons blocked buffs manually in the EQ folder <toonname>_<server.ini> under the [BlockedSpells] section.

Then re-blocked the pact of the wolf in game and it's working with no issues on all toons now.

Yay! I don't know what I'm doing but having fun and it works.

Thanks for checking into it guys.

BB~
I'm still pretty much a noob at MQ. How did you "re-blocked the pact of the wolf in game " ? My shammy is doing the same thing to the point that I'm now playing with only 5 toons it was so annoying
 
I'm still pretty much a noob at MQ. How did you "re-blocked the pact of the wolf in game " ? My shammy is doing the same thing to the point that I'm now playing with only 5 toons it was so annoying
In the Aura window R-click one time and it'll show a new menu. Can choose to Add this spell to list of blocked spells
 
Narrowed it down.

1. It was only occuring with one or two 103 level toons in the party.
2. The shaman is applying aura 51377 to the 103 toons, and 53780 to the 120 toons.
3. When blocking 51377 on the 103 toons, issue still occurs.
4. When blocking 53780 on the 103 toons, issue no longer occurs.

The shaman seems to want to reapply the aura AA if one or more of the party members aura buff ID is not equal to 53780.
that's good information.

unfortunately, what-the-actual-shit dbg! we're checking if folks have the spell that the spell says it casts :( the spell definitely doesn't say "well cast some other spell entirely if the person is low"

I don't know how dbg/eq applies where to get that, but I'm going to put a "within 5 levels" check. this might not resolve it, but hopefully it does


oh - and it turns out, if the aura buff is too low to even apply on someone - there is no red error message, failure, warning, indication at all. cool
 
Sic updated MQ2Shaman with a new update entry:

7/20/2023

- presumtive fix for aura chain casting when you have a much lower level toon in your group
-- we will now only check and cast aura on someone who is within 5 levels below or above us.
--- it turns out, eq will decide what spell gets applied to them based on their level, and not the shaman's level
---- wut?!

Read the rest of this update entry...
 
I have it as well. The re-casting issue. I had my Shm as buffbot. FOrmed group with new 100 necro, 113 SK, 113Enc, and 114Shm. Shm just went into a pact of wolf chain. My necro was kicking it off, and re-casting something of her own. SO I added to a block list, and that stopped the re-casting on the necro.. but the shaman kept chain casting the AA.
SO checking.. I discovered.. If I have my group WITHOUT the 100 Necro everything is fine. Soon as I add the 100 necro, Chain casting Group Pact of the Wolf VI. SO I blocked it on my necro. Kept casting.. but it was hitting the necros PET. So Added Group to the block list for the pet.. Then the shammy changed over to Invoke Pact of the Wolf XIII. Blocked that one on my Necro and the Necro pet.. but it just kept casting it.
Drop necro from group.. Shammy calms down. Hope that helps troubleshoot the interaction. BTW, 3 seconds between re-casts on the aura.
Thanks again for all the hard work!

Crap. Will download update and edit this post as needed LOL.
 
I have it as well. The re-casting issue. I had my Shm as buffbot. FOrmed group with new 100 necro, 113 SK, 113Enc, and 114Shm. Shm just went into a pact of wolf chain. My necro was kicking it off, and re-casting something of her own. SO I added to a block list, and that stopped the re-casting on the necro.. but the shaman kept chain casting the AA.
SO checking.. I discovered.. If I have my group WITHOUT the 100 Necro everything is fine. Soon as I add the 100 necro, Chain casting Group Pact of the Wolf VI. SO I blocked it on my necro. Kept casting.. but it was hitting the necros PET. So Added Group to the block list for the pet.. Then the shammy changed over to Invoke Pact of the Wolf XIII. Blocked that one on my Necro and the Necro pet.. but it just kept casting it.
Drop necro from group.. Shammy calms down. Hope that helps troubleshoot the interaction. BTW, 3 seconds between re-casts on the aura.
Thanks again for all the hard work!

Crap. Will download update and edit this post as needed LOL.
we don't check for pet having it or not. just the toon.

but yep, please patch.
 
Yep was typing up the reply with info when you updated it. Re-patched works proper. Thank you again!!!!
 
SO im not sure if this is a shammy issue or a mage issue or a im an idiot issue. shammy is constantly casting pact of the wolf aa and the mages are constantly removing it from the songs window. i have tried blocking said buffs but to no avail the shammy continues to cast it and mages continue to remove it ignoring the fact that its on their banned buffs list. me as said idiot continues to drool hoping that the puddle on my desk will span insight.
 
patch. should fix it.

please make sure to :
a: post in the right place
b: check before posting
c: be patched
d: don't drool on the desk

1689894402615.png

your mage is likely not the one removing anything, patch up and should be fixed
 
ChatWithThisName submitted a new resource:

MQ2Shaman - Much. Squall.



Read more about this resource...
I purchased this. I downloaded the vanilia. I ran the plug in and watched it. When I do the mq i did the /plugin mq2shaman load. it seems like it loads, then at the end it says in white plugin mq2shaman unloaded then whenever i try a command like /shm help or /shm mode, or any command all it comes back as is DoCommand couldnt parse and then the command. Can anyone help me?
 
I purchased this. I downloaded the vanilia. I ran the plug in and watched it. When I do the mq i did the /plugin mq2shaman load. it seems like it loads, then at the end it says in white plugin mq2shaman unloaded then whenever i try a command like /shm help or /shm mode, or any command all it comes back as is DoCommand couldnt parse and then the command. Can anyone help me?
there is nothing to watch. plugins you have access to, you will have on the redguide's launcher

you need to download the plugin via the launcher and then load the plugin when you are in game (with mq loaded).

the game and mq doesn't magically know mq2shaman, you have to download it.

make sure you check out the sticky after you get it loaded

Please see >>> Getting Started with CWTN plugins! (Movement, UI Window, Clickies, Pulling, ETC) Check Here First! <<<
 
there is nothing to watch. plugins you have access to, you will have on the redguide's launcher

you need to download the plugin via the launcher and then load the plugin when you are in game (with mq loaded).

the game and mq doesn't magically know mq2shaman, you have to download it.

make sure you check out the sticky after you get it loaded

Please see >>> Getting Started with CWTN plugins! (Movement, UI Window, Clickies, Pulling, ETC) Check Here First! <<<
I did download it, and its under plugins on the launcher. I ran it like the video said /plugin mq2shaman load and it loaded then in white it unloaded? and then every command i did i got that dot command error. Are you saying to download it again?
 
I did download it, and its under plugins on the launcher. I ran it like the video said /plugin mq2shaman load and it loaded then in white it unloaded? and then every command i did i got that dot command error. Are you saying to download it again?
Sorry I misread.

If it automatically unloaded, it probably told you that you're trying to use mq on a truebox server, which is unsupported.

it puts a message across your screen for 60 seconds saying "MacroQuest is not supported on Truebox Servers. MQ2Shaman will now unload."

MQ is not supported on Truebox servers. If/When a server transitions into "relaxed truebox" or complete removal of truebox restrictions, MQ support would be added at *sometime* afterwards.

> Here is the link to the sticky <

Other tools such as MySEQ and IonBC are available for truebox servers.
 
Last edited:
Plugin - MQ2Shaman

Users who are viewing this thread

Back
Top
Cart