-
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! 👋
- Thread starter Sic
- Start date
MQ2Shaman was my gateway drug to the CWTN Plugins. After having the ability to beta this plugin and see how well it worked with my Shaman, I moved the rest of my dudes over to running them. Purchasing this today was a no-brainer! Happy to support you guys and your effort to maintain the current collection and build new ones for the remaining classes!
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
We really appreciate the kind words from all, and the support from all of the users. Please take the time to go to the reviews section and leave a review about the plugin if you get a chance.
www.redguides.com
Thank you!
Combat Assist - MQ2Shaman - Reviews
www.redguides.com
Thank you!
Love mq2shaman, has so many options! Ranging from full healer mode to hybrid or dps - it covers all bases. It's super easy to adjust some specifics in the ui window to your liking - such as if you will slow, malo etc. Gives you the ability to tailor things to your liking which is awesome!
Only thing I'd request is for intervention aa (emergency heal) as well as chestplate clicky (similarly an emergency heal, which you can add to your clicky lineup using the slash commands) to be set at a higher threashold of hps on main tank (or possibly for it be able to be edited in the ui). When playing with my sk or paladin I'm never in risk of dying as I can emergency heal myself. However, on my warrior I don't have that luxury after having used flash or fortitude to "save myself". I feel like the threshold trigger of hp's could use a bump up (sure it'll use it more often but i've died several times by it never triggering as I was lingering just slightly above the threshold for it to trigger.
Regardless of the above request, it's a easy 10/10 plugin. Super well done and thanks for your superb efforts giving us suck kickass plugins to use!
Only thing I'd request is for intervention aa (emergency heal) as well as chestplate clicky (similarly an emergency heal, which you can add to your clicky lineup using the slash commands) to be set at a higher threashold of hps on main tank (or possibly for it be able to be edited in the ui). When playing with my sk or paladin I'm never in risk of dying as I can emergency heal myself. However, on my warrior I don't have that luxury after having used flash or fortitude to "save myself". I feel like the threshold trigger of hp's could use a bump up (sure it'll use it more often but i've died several times by it never triggering as I was lingering just slightly above the threshold for it to trigger.
Regardless of the above request, it's a easy 10/10 plugin. Super well done and thanks for your superb efforts giving us suck kickass plugins to use!
- Seller
- #768
well as mentioned in a few places - the clickies are going to get a revamp at some point - the group health clicky value isn't currently adjustable - and that will be sometime in the future.
I won't likely be adjusting the intervention heal and intervention aa heal - and even less likely to add it to be adjustable --- not everything is going to be a toggle or an adjust and that is on purpose.
if your warrior is just hanging out that low, I would double check what stance you're in (which designates the spell set to load). I have a hard time imagining you're just hanging out barely above the intervention threshold and have all 3 reckless on cooldown
Totally understandable that it won't be. Shaman is in heal mode stance, not in byos etc. It does seem to sometimes when/if growth wears off that it typically goes for rebuffing that rather than continuing on heals. Perhaps I should just uncheck that and rebuff it manually instead!
I did change recklessma to 99, and mendingma to 98 and sthotma to 97. All the notma's are at default values. I also have unchecked slow, ae slow, malo and aemalo. Still using squall. No melee. Have also tried without but with heavy ae that isnt recommended as recourse seems to be set to a pretty low health value before it uses that vs other heals. Have also tried unchecking dots but that seems non-issue as it prioritizes heals over dots 9/10 times with my settings mentioned. Nukes I've played around with. Noticed that it only does gift nuke if that is checked, if I have unchecked squall.
Maybe I've played around too much with settings! haha Again, thanks for an awesome plugin never the less. Beats me using isboxer
- Seller
- #770
nah, the things you said aren't true.Totally understandable that it won't be. Shaman is in heal mode stance, not in byos etc. It does seem to sometimes when/if growth wears off that it typically goes for rebuffing that rather than continuing on heals. Perhaps I should just uncheck that and rebuff it manually instead!
I did change recklessma to 99, and mendingma to 98 and sthotma to 97. All the notma's are at default values. I also have unchecked slow, ae slow, malo and aemalo. Still using squall. No melee. Have also tried without but with heavy ae that isnt recommended as recourse seems to be set to a pretty low health value before it uses that vs other heals. Have also tried unchecking dots but that seems non-issue as it prioritizes heals over dots 9/10 times with my settings mentioned. Nukes I've played around with. Noticed that it only does gift nuke if that is checked, if I have unchecked squall.
Maybe I've played around too much with settings! haha Again, thanks for an awesome plugin never the less. Beats me using isboxer
it checks for heals before checking for growth 10/10 times, and it checks both of those before checking if it should nuke or dot 10/10 times. it checks all of these things faster than you or i can count. if it is supposed to do a thing, in that moment, it does the thing. so if you don't need a heal or they're not ready, and we get through all of our checks and now only thing left to do is growth or dot/nuke - we're going to start doing that.
and no recourse isn't set low either, but we're also ensuring you don't have forbearance before re-casting it, and it is used as a group heal
- Seller
- #772
no, the adjustable things are made so they can be adjusted - if you want your reckless values to be higher or lower you should set them how you want
this is what my settings look like
reckless default is 90, I keep mine at 90
reckless not ma default is 80, i keep mine at 70
ive done all missions in all 3 spell loadout stances with these settings
- Joined
- Aug 26, 2015
- RedCents
- 420¢
Been very busy at work this week and finally getting off for the weekend.
Thank you @ChatWithThisName & @Sic for all the great work!
Now it makes sense why I was getting a recompile error msg... Purchasing asap.
The testing I have done with this before it was paid for was significant and tried out a lot of things.
I'm loving it.
/queue up Ministry "Just One Fix"
Thank you @ChatWithThisName & @Sic for all the great work!
Now it makes sense why I was getting a recompile error msg... Purchasing asap.
The testing I have done with this before it was paid for was significant and tried out a lot of things.
I'm loving it.
/queue up Ministry "Just One Fix"
- Joined
- May 9, 2016
- RedCents
- 0¢
Hello was curious if maybe i could be helped out here for some reason when things are getting heated. The shaman will chose to cast roar over a group heal. Ive tried to change the setting around to see if it will help but there always a time when he will be casting another spell or trying to mem a spell rather than spamming group heal / squall. Any help with this would be aweeeesome .... Love the plugin !
- Seller
- #775
roar is checked after all the heal checks/verification and these checks happen more frequently than we can count - it is likely just a timing issue of cooldown and the checks
- Seller
- #779
it went "full release" 3 days ago
unfortunately, the launcher doesn't currently have a way to remove out of date plugins if they are removed or go "full release". You will want to delete that mq2shaman.dll file, or change mq2shaman=1 to mq2shaman=0 in your macroquest2.ini to make mq2 stop trying to load the out of date dll.
Last edited:
- Seller
- #781
:p thanks for the support, cwtn and i sincerely appreciate itCan also do what I did: buy it, go and download it from the main page, then replace the current .dll file with the newly downloaded one. Presto - back in action!
Wassamassaw
Member
- Joined
- Jan 23, 2015
- RedCents
- 49¢
Is there anyway to make mq2shaman more aggressively use Reckless heals? Even set to 90 for reckless MA, the program is prioritizing other spells first. As long as my warrior has flash up, this is fine. But, on my warrior, if flash is down it many times leads to a wipe.
For example, my warrior, set to MT and MA, initiated a pull of many mobs, and his health dropped down to 60%. While the warrior's health was at 60%, and my Shaman is set to RecklessMA 90, my shaman cast order was silent casting, wintry gift, pact of the wolf, composite roar, communion of the cheetah, and finally reckless. During all these castings my warrior's health never went above 90% until the reckless heal was cast.
In most cases, this is fine. But, when I have a group of Mez immune mobs, it's just not casting Reckless fast enough to save the warrior when the warrior's defensives are on cooldown.
*Shaman was in Heal stance
**Yup, like Sic says below me, this program works very well, but the class needs to get the HoT's rolling before large pulls when all the warrior's defensives are on cooldown. This is where the weakness of the warrior comes into play compared to the SK and Paladin. The SK and Paladin have a ton of abilities to constantly roll through to help this gap. The warrior has only a few, but they work very well. Once flash, fortitude and ultimate stand are down if you just pre-cast the hots the shaman can heal perfectly fine on all the pulls. Sic and I went through a ton of pulls verifying this, and I greatly appreciate all the time he went above and beyond with me to make sure I understood exactly what was going on. As it stands now, the program is basically doing what a shaman does before a pull at the beginning of the fight, and once those are up it reacts with reckless heals faster than I can manually.
For example, my warrior, set to MT and MA, initiated a pull of many mobs, and his health dropped down to 60%. While the warrior's health was at 60%, and my Shaman is set to RecklessMA 90, my shaman cast order was silent casting, wintry gift, pact of the wolf, composite roar, communion of the cheetah, and finally reckless. During all these castings my warrior's health never went above 90% until the reckless heal was cast.
In most cases, this is fine. But, when I have a group of Mez immune mobs, it's just not casting Reckless fast enough to save the warrior when the warrior's defensives are on cooldown.
*Shaman was in Heal stance
**Yup, like Sic says below me, this program works very well, but the class needs to get the HoT's rolling before large pulls when all the warrior's defensives are on cooldown. This is where the weakness of the warrior comes into play compared to the SK and Paladin. The SK and Paladin have a ton of abilities to constantly roll through to help this gap. The warrior has only a few, but they work very well. Once flash, fortitude and ultimate stand are down if you just pre-cast the hots the shaman can heal perfectly fine on all the pulls. Sic and I went through a ton of pulls verifying this, and I greatly appreciate all the time he went above and beyond with me to make sure I understood exactly what was going on. As it stands now, the program is basically doing what a shaman does before a pull at the beginning of the fight, and once those are up it reacts with reckless heals faster than I can manually.
Last edited:
It's true, I've seen and reported this kind of behaviour myself before (doing "other" stuff instead of healing when it absolutely needs to....)
Wassamassaw now seeing the same also.
Oddly enough, all of us are running a Warrior.
Honestly, I love and own your other plugins, I really wanted to give you my money for this one too.... but I can't if it's just gonna decide to let me die on occasion while it casts buffs
- Seller
- #787
re: "its true" - no it's not.
I don't want any of this to turn into an argument like last time.
I've explained this all before in the shaman thread, but will explain it again.
heals are checked multiple times a second, we handle it the same way in cleric that we do in shaman. it checks heals and if none of the conditions are met to do any healing (health is fine, things are on cooldown, gems not ready, we're stunned/silenced etc), we keep rolling checks until we *can* find something to do. this is why in the cwtn plugins you can usemelee on your healers and not die. If we check all our heals conditions and nothing is needed, then we continue on to check our other stuff.
This is how frequently we enter and process our entire heals sub section - which includes - you guessed it, every one of our heal checks, it checks EVERYTHING in this time - checks all emergency heals, checks all non emergency heals, checks things you wouldn't think of to check - all several times a second.
you can see here each time it enters the heals section (we have it setup to check twice a second), the timestamp, and then the health of the group member (0 being the shaman 1 being the tank).
now these are just when we actually go into the heals - not the frequency of the check for the heal section (which happens more frequently, but we limit it to twice a second to complete the full sub)
healing sub gets called any time you're in combat (by combat its actively fighting, so like usemelee on) - or any other time that you are either not invis, or you have a camp set. this covers breaking invis to heal - we won't break invis to heal if you don't have a camp set (so like manual mode) - where if you did have a camp set, like assist mode, you would break invis to heal.
i tossed some extra stuff in here so you can see it in combat. it is meleeing and casting stuff.
in the first "In Heals" line it shows G1 at 85% health - but we were currently casting a spell, by the time we finished casting the spell, the tank was above my 90% threshold for reckless.
in the red circled one you can see the tank went to 80, and that half-second we instantly started casting reckless renewal.
Shaman's cast time for their regular stuff is different than a cleric - I suspect your issue (assuming what you said about your tank being set to MA is accurate) is that it was either stunned/silenced - or it was just casting other stuff when you finally met the condition to heal.
I would also recommend if you're going from "my dudes are chilling" to "now i am fighting 6 mobs instantly" that maybe you pre-hot or pre use a defensive - like a real player would. jumping from no combat with no hots running, to 6 mobs beating you when we have a bunch of stuff to get rolling is also likely a possibility. keep in mind shamans are not clerics.
if it cast silent casting it is because its burn condition was met (likely burncount since you said you were pulling lots of mobs - if you don't want it doing burn spells - then you can increase your burncount to something like 99. but if it has stuff to cast, and gets to the conditions that it should cast it - it does.
it doesn't interrupt anything to cast something else instead
I spent several hours last night trying to find any abnormalities - and only found the stuff I already knew about - if its casting another spell when you get some spike dmg etc.
I'm sorry you're having trouble and I'm sorry if you're unsatisfied.
This plugin had been in pre-release for several months, and since it just released if you're unhappy with the product I can have a refund issued to you
Let me know.
edited to elaborate on some PM conversations about this:
Keep in mind if you go from 0 mobs to 5 mobs, you have a whole bunch of stuff that you need to start rolling to get "caught up" automation doesn't know that you're going to be pulling 5 mobs, or that you may or may not pull a horde of tizmacs who can stomp you with their proc for 50-100k each instantly.
when you get into combat and start fighting stuff you have stuff you need to get rolling to keep up with buffs and heals - that is how this class functions and that is how i designed this plugin.
Just like rolling into a big mob / named / raid encounter and you want to ensure you have defensives/buffs/heals/hots/wards/kitchen sink up ahead of time - if you know you're about to do something risky, you have to think about that yourself, otherwise you're not allowing the automation and the class to react appropriately.
I don't want any of this to turn into an argument like last time.
I've explained this all before in the shaman thread, but will explain it again.
heals are checked multiple times a second, we handle it the same way in cleric that we do in shaman. it checks heals and if none of the conditions are met to do any healing (health is fine, things are on cooldown, gems not ready, we're stunned/silenced etc), we keep rolling checks until we *can* find something to do. this is why in the cwtn plugins you can usemelee on your healers and not die. If we check all our heals conditions and nothing is needed, then we continue on to check our other stuff.
This is how frequently we enter and process our entire heals sub section - which includes - you guessed it, every one of our heal checks, it checks EVERYTHING in this time - checks all emergency heals, checks all non emergency heals, checks things you wouldn't think of to check - all several times a second.
you can see here each time it enters the heals section (we have it setup to check twice a second), the timestamp, and then the health of the group member (0 being the shaman 1 being the tank).
now these are just when we actually go into the heals - not the frequency of the check for the heal section (which happens more frequently, but we limit it to twice a second to complete the full sub)
healing sub gets called any time you're in combat (by combat its actively fighting, so like usemelee on) - or any other time that you are either not invis, or you have a camp set. this covers breaking invis to heal - we won't break invis to heal if you don't have a camp set (so like manual mode) - where if you did have a camp set, like assist mode, you would break invis to heal.
i tossed some extra stuff in here so you can see it in combat. it is meleeing and casting stuff.
in the first "In Heals" line it shows G1 at 85% health - but we were currently casting a spell, by the time we finished casting the spell, the tank was above my 90% threshold for reckless.
in the red circled one you can see the tank went to 80, and that half-second we instantly started casting reckless renewal.
Shaman's cast time for their regular stuff is different than a cleric - I suspect your issue (assuming what you said about your tank being set to MA is accurate) is that it was either stunned/silenced - or it was just casting other stuff when you finally met the condition to heal.
I would also recommend if you're going from "my dudes are chilling" to "now i am fighting 6 mobs instantly" that maybe you pre-hot or pre use a defensive - like a real player would. jumping from no combat with no hots running, to 6 mobs beating you when we have a bunch of stuff to get rolling is also likely a possibility. keep in mind shamans are not clerics.
if it cast silent casting it is because its burn condition was met (likely burncount since you said you were pulling lots of mobs - if you don't want it doing burn spells - then you can increase your burncount to something like 99. but if it has stuff to cast, and gets to the conditions that it should cast it - it does.
it doesn't interrupt anything to cast something else instead
I spent several hours last night trying to find any abnormalities - and only found the stuff I already knew about - if its casting another spell when you get some spike dmg etc.
I'm sorry you're having trouble and I'm sorry if you're unsatisfied.
This plugin had been in pre-release for several months, and since it just released if you're unhappy with the product I can have a refund issued to you
Let me know.
edited to elaborate on some PM conversations about this:
Keep in mind if you go from 0 mobs to 5 mobs, you have a whole bunch of stuff that you need to start rolling to get "caught up" automation doesn't know that you're going to be pulling 5 mobs, or that you may or may not pull a horde of tizmacs who can stomp you with their proc for 50-100k each instantly.
when you get into combat and start fighting stuff you have stuff you need to get rolling to keep up with buffs and heals - that is how this class functions and that is how i designed this plugin.
Just like rolling into a big mob / named / raid encounter and you want to ensure you have defensives/buffs/heals/hots/wards/kitchen sink up ahead of time - if you know you're about to do something risky, you have to think about that yourself, otherwise you're not allowing the automation and the class to react appropriately.
Last edited:
- Joined
- Jun 14, 2017
- RedCents
- 1,962¢
Hi,
I have had a new problem start since the last update. My Shaman is level 85 and is running on a TLP Server. Seems the Shaman will get into a cycle will it will just buff "Talisman of the Unity Rk II", "Ancestral Obligation" and "Talisman of the Foresight Rk II" over and over. I see a message that Talisman of Foresight Rk II has been overwritten while this is going on. Would this be user error or something on your end that needs looking into? If you need anymore info from my end let me know. If there is something I need to set or block on my end please let me know. Thanks, AnotherJohn
I have had a new problem start since the last update. My Shaman is level 85 and is running on a TLP Server. Seems the Shaman will get into a cycle will it will just buff "Talisman of the Unity Rk II", "Ancestral Obligation" and "Talisman of the Foresight Rk II" over and over. I see a message that Talisman of Foresight Rk II has been overwritten while this is going on. Would this be user error or something on your end that needs looking into? If you need anymore info from my end let me know. If there is something I need to set or block on my end please let me know. Thanks, AnotherJohn
Wassamassaw
Member
- Joined
- Jan 23, 2015
- RedCents
- 49¢
Thank you Sic for all the help you provided me. I appreciate it.
- Seller
- #792
howdy anotherjohn good to see ya
well ancestral obligation if your cannibalize spell - so its doing that for mana
talisman of unity is your group focus
the talisman of foresight was the GAgi (Group Agility) i was asked to add. I suspect that, they are overwriting each other.
what is strange is on a 115 with no other buffs i can't get that to occur, but i did have someone lower lvl who had a similar experience.
in the mean-time you will likely just want to block the group agility "Talisman of Firesight" ability
Last edited:
- Seller
- #793
our conversation was a good one, I think we each have a better understanding of what the other was trying to communicate.
I have some ideas to help possibly address what you're talking about
@Sic Unity @ 81/85 will have a lesser version of Talisman of Foresight, which is why Foresight is overwriting.
This will fix itself once HoT releases (and 86+ unity is gotten)
- Seller
- #795
yeah i understand that - but it shouldn't re-focus to apply the lesster foresight - this is one of those "middle spells" that mq2 has issues with
- Seller
- #797
unfortunately mq2 has some spells - almost exclusively in the "low/middle" range where the stacking can change depending on who checks it (level included)
example:
/echo ${Spell[Valor].StacksWith[Protection of Nature]} this should always be no - some lower lvl clerics it says true lol
- Seller
- #799
oh yeah, want something crazy?
/noparse //bcaa ${Spell[Celerity].StacksWith[Exceptional Velocity]} Everyone except beastlords will say false! beastlords will say true