• 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 (1 Viewer) 3.1.52471.24

so since this morning the shaman will not sit down. i did not change anything other than do an update this morning. Yester day it was working fine however so much sure what changed

View attachment 77634
in assist mode we sit after combat (no mobs on xtarget) - we go back to our camp and then sit back down.

there's no setting or anything here that would change that - I would make sure you didn't set your camp floating up in the air with levitation

would make sure you dont have mobs on xtarget

do a /makemefall then /shm resetcamp and see if it sits

also deleting your image since you have toon names in it
 
I think i might have figured it out. Form of great bear i think can mess with it. I started with that on and it wore off. when it wore off he would slow and dot but little else. not sure all the odds and ends but thats what i was able to reproduce the results with.
 
Is it possible for MQ2Shaman (and/or CWTN Class plugins in general) to parse spell did not land (Blocked by another spell) situations in a way where that tells the routine to stop trying to cast that spell on that mob? At level 80, Crippling Spasm is almost always blocked in raid by a chanter's Shattered Consciousness III. Shaman continues to try to land spell until mob is dead. Would adding this be too much work or break other things that CWTN class plugins do? Currently addressing it by unmemming Crippling Spasm from spell gem mid-combat once I'm aware it's not landing. I know I can BYOS, but wasn't sure if adding "stop casting the thing that won't land" is a solution that works for multiple cases across different classes. If it's more work than it's worth, or would have other unintended consequences that are detrimental to how the class plugins work as a whole, I get that and am fine with continuing to fix on the fly. Just curious if this is a possibility.
 
No, that's not something we're doing at this time. There are a whole bunch of reasons for it, but that's just not something we want to do

cripple is an annoying thing - I really dont want it to be a toggle/option/setting because it is used for such a short period of time - byos or byos-custom is the correct choice.
 
Plugin - MQ2Shaman

Users who are viewing this thread

Back
Top
Cart