Yup, all set. Autogroup sets the group up with MA/MT on the warrior.MA/MT set ingame?
Nothing has changed on my end. It was all working and then the next time I logged in it wasn't.
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.

Yup, all set. Autogroup sets the group up with MA/MT on the warrior.MA/MT set ingame?
there are quite a few folks who use this thing, and no others (including the 3-4 shaman i run daily) having this issue.Yup, all set. Autogroup sets the group up with MA/MT on the warrior.
Nothing has changed on my end. It was all working and then the next time I logged in it wasn't.
that means you docked the imgui window to the top of your screen (all imgui windows allow you to do that unless specifically disabled in them). you can also dock them to top, bottom, left, and rightI've been using the MQ2Shm plugin for some time now but somewhat recently the UI window for the plugin's behavior changed. It is now locking itself to parts of my screen and I can no longer move it away. Currently the menu is stuck to the top of my interface spanned across the entire screen. I can toggle it off and on or resize it like a curtain but I cannot get it to let go of the screen to be resized as a window again. Ideas?

Yw, all sorted?Ty for the prompt assistance

since we don't randomly do anything - I can't tell youI just had the weirdest thing happen. I'm not running anything except default settings for MQ with MQ2Shaman and MQ2AutoLoot enabled. Also MQ2Eskay in group. Others are non MQ players. Completely out of the blue my Shaman resets camp to the next zone over and, naturally, runs there!
I'm in zone 815, The Overthere. 791 is Frontier Mountains, next door.
I've never been to Frontier Mountains (791 version) and I wasn't even at the keyboard when it happened. Nor was anyone at home. Don't have cats, or a poltergeist!
What on earth could cause this?
View attachment 59301
I said I'm not running anything except default settings. So those plugins which are enabled by default. I should've posted this in the main MQ discussions though. It wasn't meant as an MQ2Shaman post. I'll do that and add some clarifications.since we don't randomly do anything - I can't tell you
since you were afk (which is not condoned) - you can't tell me
"not running anything" - this is always not only incorrect, but often comes across as a "don't look elsewhere because this is a YOU problem not a me problem". if you did /plugin list you would probably see 30-50 plugins loaded - not saying it is something else (because nothing else can set our camp, other than a hotkey/cfg etc) but saying there is nothing other than mq2shaman and mq2autoloot is just incorrect and wastes time/focus/energy.
the plugins can't randomly pick a zone to say they're in - we get that information from MQ which gets it directly from eq.
we don't have a way to set camp in another zone, and we don't run to other zones. if you zoned/gated/whatnot in a mode with a camp, we reset your camp while you are there. it sounds like you were bound somewhere and died, or gated/ported
we also don't randomly update your camp
it almost sounds like you evac'd or gated to that zone, then went back - obviously there are no timestamps and your screen snip of what mq2shaman is doing is pretty slim.
don't afk mang, it isn't worth it, and it is bad for MQ/EQ
well no, mq2shaman's camp is getting updated - so this should be in mq2shaman (or at least cwtn section - it shouldn't be elsewhere). there's nothing that should be doing that which you didn't enable/update/turn on like a LEM or react or some script (Lua/macro), unless your toon zoned via some method like death, gate, portal, or zoningI said I'm not running anything except default settings. So those plugins which are enabled by default. I should've posted this in the main MQ discussions though. It wasn't meant as an MQ2Shaman post. I'll do that and add some clarifications.
okiesI didn't die, I wasn't ported, evacuated or anything like that. I was only afk a few seconds to take a leak and when I came back I was zoning. My party confirms my character ran there.
There's nothing else in the log before the change of the camp co-ordinates other than casting spells and AA's as we fought mobs. No one else is in my DanNet network and no one in the party was in the zone the camp moved to, nor had been.
My SK didn't get their camp updated so it was definitely a local decision rather than a broadcast one.
nah, i'd rather we just leave it at the "okies" i posted, as always i'm going to see if i can replicate, but it really looks like something like - nav pathing went sideways and zoned, or mob warped and nav'd to the mob which resulted in zoning etc.could you post your running luas from the lua interface thingy in /mqsettings
and your list of plugins from the [plugins] section in your macroquest.ini from the config folder
no, they recently fucked shamans by entirely removing twincast from applying to squall - which means giftDD is near uselessI have a more useful question about MQ2Shaman gameplay. I'm catching up on years of class development and I'm unsure whether my character ought to be memorizing the Gift DD line and whether the conversations about proccing the twinheal with Squall are still relevant. I've set the plugin to Heal/Hybrid/DPS, turned DoT and Nuke and Squall settings on and off and my character never memorizes my Gift DD. Meanwhile it casts Squall pretty much on cooldown even when no one is under the healing threshold.
Also Squall is not an instant heal (maybe it used to be?) so it's excluded from TwinHeal procs anyway.
So my question is what is the expected behaviour for using Gift, Squall and twinheal procs?

also what logs? we intentionally don't log our mq2nav movementsI see something unexpected in the MQNav logs where the location being navigated to after combat shifts ever so slightly without me interacting with it.
There's mq2nav.txt in Macroquest/Release/Logs. It's only logging what it does though, not what it was told.also what logs? we intentionally don't log our mq2nav movements
unless you have mq2log turned on (which isn't default and you didn't mention :p)
I 2024-03-21 11:38:02.192172 [MQ2Nav] Navigating to loc: (-86.17, -2087.37, 12.34) (C:\agent\_work\1\s\plugins\MQ2Nav\plugin\MQ2Navigation.cpp:1581)
I 2024-03-21 11:38:02.193095 [MQ2Nav] Navigating to loc: (-2087.37, -86.17, 12.34) (C:\agent\_work\1\s\plugins\MQ2Nav\plugin\MQ2Navigation.cpp:1581)
I 2024-03-21 11:38:02.820300 [MQ2Nav] Reached destination at: (-2087.37, -86.17, 12.34) (C:\agent\_work\1\s\plugins\MQ2Nav\plugin\MQ2Navigation.cpp:1164)
I 2024-03-21 11:39:04.285923 [MQ2Nav] Navigating to loc: (-93.95, -2094.73, 6.31) (C:\agent\_work\1\s\plugins\MQ2Nav\plugin\MQ2Navigation.cpp:1581)
I 2024-03-21 11:39:04.310881 [MQ2Nav] Navigating to loc: (-2094.73, -93.95, 6.31) (C:\agent\_work\1\s\plugins\MQ2Nav\plugin\MQ2Navigation.cpp:1581)
I 2024-03-21 11:40:46.882272 [MQ2Nav] gSuccessfully loaded mesh for mfrontiermtnsb x (C:\agent\_work\1\s\plugins\MQ2Nav\plugin\NavMeshLoader.cpp:80)
cwtn plugins don't log nav movements. we use "log=off" for all navigation movementThere's mq2nav.txt in Macroquest/Release/Logs. It's only logging what it does though, not what it was told.
I see this repeatedly as my characters are sent to their spots after each fight:
Then after many many identical lines there is this slight shift which I didn't initiate:
Then my character runs off and zones:
The log line doesn't include the ZoneId but if some sort of memory mix up hypothetically altered three of the four values then it's likely it altered the other one.

what i'm saying is, when we issue the nav command we issue it withThe MQ2Nav Tools dialogue shows Log level is set to 'info' for me, out of the box so to speak. So if "log=off" is being passed from CWTN to MQ2Nav in the navigation request perhaps it doesn't respect it. Anyway, I can't reproduce this so feel free to move on. I'm going to turn MQ2Nav logging up to debug and if it does happen again maybe I'll capture something more useful.
Thanks for the info on Gift.![]()
/nav loc y x z log=off which means, the cwtn plugins shouldn't be generating any nav logs| log=<level> | Adjust log level for command. can be trace, debug, info, warning, error, critical, or off. The default is info. this can be added to navigation commands above to alter their behavior |
this would imply that the issue is entirely unrelated to what i've been working through this evening, and since no other changes to heals have happened, it would mean it maybe never has ever healed - which means im gonna need some more specificsi fixed the clr issue by updating the mq2 cleric plugin to a older version but doing this to the shm has had no effect.
Yes, this is your problem. Load Ahnkaul's Mending and it should be doing it's thing. You'll want to pay attention when you level up and then scribe new spells on what spell or group is being replaced with a thing. Perhaps even turning off BYOS/BYOS Custom after scribing spells to see what gets replaced with what.I can’t test right now but now that I say that it may be related - like it may be skipping that cuz it wants me to mem anhkuls ? Idk I will get more data for you when I get home
if you are randomly willy nilly memorizing things that the plugin doesn't say it uses, yep. it isn't going to use it.I can’t test right now but now that I say that it may be related - like it may be skipping that cuz it wants me to mem anhkuls ? Idk I will get more data for you when I get home

I asked for this information yesterday, because it really sounded completely unrelated - and still didn't get that information as asked for either.this would imply that the issue is entirely unrelated to what i've been working through this evening, and since no other changes to heals have happened, it would mean it maybe never has ever healed - which means im gonna need some more specifics
could you be specific about
- what level you are
- what spell you are expecting it to cast as heals/heals but it isn't
-- if you are byos, is this a spell the plugin says it uses
- what your mendingMA value is
- what your mendingNotMA value is
- what your recklessMA value is (assumign you have reckless)
- what your recklessNotMA value is (assuming you have reckless)
- now if byos, you can memorize any of the heals/heals spells with "Mending" in the name
- - and you will use them at your MendingMA/MendingNotMA values
Sic I’m so sorry it was a goose chase man I didn’t do it intentionallyI asked for this information yesterday, because it really sounded completely unrelated - and still didn't get that information as asked for either.
:'(
but yes, sounds entirely related to byos'ing things that the plugin doesn't say it'll use
cleric has some spells that works a little bit differently with byos, but "by and large" if it doesn't say it uses it, it isn't going to use it.
I can take a look at and see if that spell specifically we can just use it - but prolly not right now.
Patch.I have had mq2 shaman for 2 days. I cant get it to cast any heals it will slow dps and buff but will not heal to save my life. I am new to red guides and boxing can anyone help
does the lvl of my shaman matter at all i am only lvl 40 does that matter at allYes check your settings. It sounds like you have a BYOS on. You should use the standard spells to start out. No BYOS. Which is sounds like you have a BYOS with no heals.
