- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
- Seller
- #1,401
-
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 ChatWithThisName
- Start date
Updated mq2war today, then did a raid, then I notice my warrior will not move to a mob when I change target midfight in sictank mode. also, can walk away from mob and it wont nav back to it. Is this a new feature, bug, or did I turn something off? I tried with stick on and off, had no effect.
no it is not a new feature, there were no changes there.
I'd suggest that you are in the mode that you want to be in, the mob is within the condition for you to do stuff to it (inside camp etc), and your settings are how you want them.
I'd suggest being in tank mode (4) if you want that behavior (or clear your target, re-aquire and turn on attack)
Well... I have been using Sictank mode for actual months and it has been doing exactly as I have said it has. I do not use tank mode as its atrocious for my play style. I dont want to be stuck anywhere. You told me to use sictank mode and it has been servicable since. now its not doing what it used to do.
again. like every time i answer your questions and you want to argue "I am not going to go 50 rounds with you".
I dunno what to tell you bud, Sictank mode hasn't changed.
you are probably just confused about how sictank works.
if you are in mode 4, tank mode, you will continually re-stick (with a small timer).
if you are in mode 7, you don't continually stick, just the initial target gain + attack on - so if you cleared your target, swapped, and turned on attack, you'd initiate a new stick, or the mob died and then you initiated combat again, you'd do a new stick - but if you have your attack on and are fighting and such - it isn't going to re-stick you
and that particular code has been in place since 6/4/2020
now your comment could be "i wish it did this but it does this instead" - which would still be a "that's how the mode is intended to work, use tank mode if you want to do that", but to double and triple down on saying it changed in the past few days is just inaccurate and leaves no room for any actual discussion about things.
you did this same thing when you thought that manual mode was selecting targets and facing mobs for 6-8 months, despite ABWar, myself, and cwtn telling you it doesn't - and you STILL double-downed that despite writing the darn thing and looking at the code, that cwtn and i were wrong.
you do this every time.
I am respectfully asking you to just stop with the 50 rounds. if there is a behavior that you don't like - mention that, if there is an adjustment you would like to see - mention that, if there is something you are unclear about - mention that.
sometimes things get adjusted or changed, sometimes they don't, but i will not continue this with you every time you post.
I'm having a bit of a problem with getting aggro on incoming mobs. I have the war set up in tank mode and pulling with bard. The Pulls usually run right through me, the the war has to chase it. Some times the bard or healer or healer are dead almost instantly. If I manually click blast of anger, it grabs aggro instantly and has no problem. Is there any adjustments I can make to grab aggro faster?
- Joined
- Feb 9, 2017
- RedCents
- 1,387¢
Having this random issue with huntertank, toon targets the mob (128 ft) away and the melee and range button are depressed but nothing is happening. If I hit the melee or range attack button it resumes as normal. Mob is in plain line of site. Any experience with this?
Edit: Ok I disablepullability on, thinking the warrior was trying to pull with Bristle.
Edit: disblepulability quit using bow, not good.
Edit: disblepulability quit using bow, not good.
Last edited:
you could make camp bigger on war
you could make your bard use fading memory when entering camp
you could have your cleric not heal bard whilst pulling
adjust your campradius.
we start grabbing aggro the moment your conditions are met - inside camp, on xtarget etc.
make sure to watch the mq2war vid and the "how i move my toons" vid, i go over pulling and how to manage your tank there.
again. like every time i answer your questions and you want to argue "I am not going to go 50 rounds with you".
if you argue i'm just going to ban you from these threads - > as you just completely ignored what i said two days ago. <
no, nothing changed where you switch targets to hit named mobs.
if you are in a tank mode, like sictank, when you acquire a new target, you will target the named mob - you are not locked to it, but you will always grab that as the new mob first, always.
if you don't want to do this, be in manual mode.
yes it did this before yesterday
in fact - the latest our repo will go back is 12/16/2019 when we moved to a new structure - and the code for this hasn't changed since then.
well - there you go again. Enjoy your warning.
no. that behavior is not different from yesterday.
No crash to report, just a difference in behavior of my plugins.
This is not a big deal to me, but just something I thought I would share if you care to look into it. If not no biggie, I still complete the functions I do everyday without issue. It's more of just a QoL thing for me to not be lazy and someone else may encounter it in the future :p
Key notes:
Plugins in question: MQ2War, MQ2Eskay (possibly any plugin that uses tankmode as well but these are the two I know for sure.) Details below:
Previous behavior dating back atleast 1 year: Tank Mode on, Mob Engaged, Ported away/Knocked back (100-200 feet), automatically navigate back to mob and continuing tanking in same fashion as it started in.
Description of problem:
Been using CWTN plugins for a long time now but noticed a little difference with a few things I do recently. Today I went to do some content I've been doing for over a year now using my Warrior and also my SK. They've always behaved the exact same, zero variation until this 64 bit patch DBG did. When I would activate tank mode, get knocked back or ported away from the mob, my Warrior or Sk would be tanking, instead of automatically navigating back to the mob and tanking it as it normally would, it did not do so.
Instead the Warrior or SK will sit there where it's been knocked back or ported to (say it's 100-200 feet away) spamming auto attacking and not moving or navigating back.
I've tested this at various distances out of curiosity, it seems to not navigate back at any of them if you move away from it while auto attacking.
It will return to camp if you turn auto attack off and run away, but it will not navigate back to the mob you are attacking in tank mode if too far away.
Thanks.
This is not a big deal to me, but just something I thought I would share if you care to look into it. If not no biggie, I still complete the functions I do everyday without issue. It's more of just a QoL thing for me to not be lazy and someone else may encounter it in the future :p
Key notes:
Plugins in question: MQ2War, MQ2Eskay (possibly any plugin that uses tankmode as well but these are the two I know for sure.) Details below:
Previous behavior dating back atleast 1 year: Tank Mode on, Mob Engaged, Ported away/Knocked back (100-200 feet), automatically navigate back to mob and continuing tanking in same fashion as it started in.
Description of problem:
Been using CWTN plugins for a long time now but noticed a little difference with a few things I do recently. Today I went to do some content I've been doing for over a year now using my Warrior and also my SK. They've always behaved the exact same, zero variation until this 64 bit patch DBG did. When I would activate tank mode, get knocked back or ported away from the mob, my Warrior or Sk would be tanking, instead of automatically navigating back to the mob and tanking it as it normally would, it did not do so.
Instead the Warrior or SK will sit there where it's been knocked back or ported to (say it's 100-200 feet away) spamming auto attacking and not moving or navigating back.
I've tested this at various distances out of curiosity, it seems to not navigate back at any of them if you move away from it while auto attacking.
It will return to camp if you turn auto attack off and run away, but it will not navigate back to the mob you are attacking in tank mode if too far away.
Thanks.
can you confirm you didn't turn off usestick?
Thanks for the reply. This particular content I'm doing was one that I've needed to have stick turned off for since I have been doing it which is about a year. During that period the behavior has worked as intended for the content. The reason I turn stick off is because if I leave it on it seems to overwrite, or atleast overlap, the pathing MQ2Nav would otherwise dictate. The pathing MQ2Nav uses leads me directly back to the mob on the pathing to complete the event. But if I use stick it will run through a giant area and get stuck on a wall.
So that would be my reasoning for leaving stick off in that particular scenario.
So that would be my reasoning for leaving stick off in that particular scenario.
thank you for your writeup, this was really good information.
I found the issue - which was introduced in january. I'll submit a fix
nah my approach is *always* the same - even if i *KNOW* the answer, i always go and look at the code at that spot, and then try and recreate the steps to see if a: it is different than it should be or b: works as expected etc.
in this case - you laid out specifically what and where and why so i can go "well if you move back you should restick to the mob) so i went to check it - and it didn't so i was like "hrm why are we not doing this thing"
Haha for sure, I'm glad I could make it a little easier. I thought it was odd behavior cause every other feature in the CTWN plugin set have been insanely efficient and way better than anything I've used in the past. I usually do a lot of work manually playing with the plugins back and fourth window switching through tanks and what not but that one I had gotten used to doing it that way. So I was like wait a minute let me drop this here see if they can reproduce anything or helps.
I'm having an issue that I'm only noticing lately (maybe the last week or so) where Flash of Anger will not allow itself to be popped sometimes. And by sometimes I mean session based. One login sessions it will work, meaning I can manually pop it and all's well. Another login session I cannot pop it, even if I set the war to manual or pause it, no joy.
I can't say how long ago this started but I can say that prior to ToL it worked every time I tried.
Is there something/somewhere I can look to see if something's in the way?
Thanks.
I can't say how long ago this started but I can say that prior to ToL it worked every time I tried.
Is there something/somewhere I can look to see if something's in the way?
Thanks.
make sure you are not using a 2hander as @ASmith50 said.
it should go without saying that if you can't unload the plugin or pause the plugin and do something manually - not related to the plugin =p
Ive asked this very question twice. From what I can tell, you can turn off stick to reduce it, put it in manual mode, or just live with it.
no there isn't. the automation is going to use the UW
you can scroll out, or turn off stick.
Try using a dummie in your GH. Auto attack and /autoskill bash....Take a nap if it works. I have noticed some skills not getting improves but a lot of melee skills have...Go back to nap if it doesn't
Put bash on one of your regular hotbars. Hold right click and check auto-activate. EQ usually fires these auto activatable options before MQ/cwtn plugins can.
Just keep in mind doing that takes away from the plugins doing what it needs and wants to do. So yes while that is a thing, you should probably just unload the plugin or pause it and go skill up that way because otherwise now you have something else doing things and we're going to get the inevitable "it doesnt work"
Rufus
Active member
- Joined
- Dec 19, 2020
- RedCents
- 348¢
I've run MQ2WAR & MQ2Eskay and I have not come across a setting to watch bard endurance. Here is what I've done to get around it some;
- First, if you are killing so much and so fast that your bard is OOE, you are probably doing pretty well at that camp. Bard endurance may not be effecting the group as much as the bard's indivdidual DPS>
- Once you start getting the spam from KA, put your WAR into /war mode 7 (anything non-pulling) and watch the bard recharge. You may need to pause the bard to get it to sit more consistently to med.
- Get your Unity Horn / Phoenix Feather from the Anniversary Events (coming up really soon) and add those clickies to fire automatically based on conditions, or set up hotkeys to fire them off manually by toon.
/dex toonname /useitem phoenix[/CODE]
no, not at this time
Ty. Didn’t know about those items.
Many_Whelps
WoW was the first MMO
- Joined
- Jul 22, 2018
- RedCents
- 762¢
stop using boastful bellow and vainglorious shout. They are serious endurance hogs and are definitely not worth it to spam on group content mobs that die super fast. Both of these require 18 seconds to fulminate and do full damage. If you are using both of these on refresh, you are most certainly wasting some casts on mobs that will die before the ability completes it's cycle.
Many_Whelps
WoW was the first MMO
- Joined
- Jul 22, 2018
- RedCents
- 762¢
bard dissident sucks so I wouldn't worry about not being able to use that.