- Seller
- #1,521
Your group is quite spread on levels, I'm not sure which grind instance will let you in but in my opinion that group would be fine to hit LS -> NoS -> ToL but get out of anything less than TOL.
-
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 hytiek
- Start date
Your group is quite spread on levels, I'm not sure which grind instance will let you in but in my opinion that group would be fine to hit LS -> NoS -> ToL but get out of anything less than TOL.
- Buyer
- #1,522
Hey sorry for late reply but here's 1 voa instance that's pretty populated just need do a few pre-reqs to be able to do it. There's few more I have in mind but I'll update later.
Be awesome to get 1 or 2 missions for each expansion up to current but I appreciate the work you put into this - thanks nonetheless!
- Buyer
- #1,523
Exactly as you stated! The first run they were nut to butt running from the bar to zone in. The next run the 5 sat and waited for tank to obtain quests and run back to zone in. Thank you Brother.
Melwyrm
Active member
- Joined
- Jan 6, 2022
- RedCents
- 660¢
- Pronouns
- He/Him
- Buyer
- #1,525
Similar problems to the ones others have noticed since the last patch.
In GMM I can't seem to get past location 4 any more without stepping in and pretty much driving it myself.
Plugin reports "[mq2grind] [isSafeToMove]Won't move due to [!isGroupTogether()]"
I have set the navDistance in GrindUI to 4 units, same for groupGap.
Sometimes it'll move when I push the "Come to me" button, but not much.
I have put in a full set of new meshes using the built-in mesh updater
This has been happening since the last patch and grind is pretty much non-functioning right now.
In GMM I can't seem to get past location 4 any more without stepping in and pretty much driving it myself.
Plugin reports "[mq2grind] [isSafeToMove]Won't move due to [!isGroupTogether()]"
I have set the navDistance in GrindUI to 4 units, same for groupGap.
Sometimes it'll move when I push the "Come to me" button, but not much.
I have put in a full set of new meshes using the built-in mesh updater
This has been happening since the last patch and grind is pretty much non-functioning right now.
- Buyer
- #1,527
Im doing the darkness howls with a bunch of 113 - 115 characters (dont have the flags needed for stratos one) and the group keeps stopping and the mq window spams "stuck gem detected - true" untill i manually run to the next mob
any ideas?
any ideas?
- Joined
- Aug 19, 2020
- RedCents
- 30,704¢
- Buyer
- #1,528
That sounds like your automation (kiss bard?) is doing the checkforstuckgem=1.
- Buyer
- #1,529
im using pluggins rather than kiss, but what do i do to fix it please?
- Seller
- #1,531
Would you mind talking me through what you did there? That's one of those errors no one ever expects to ever be present.
- Seller
- #1,532
Honestly 4 units of groupGap is going to cause you huge problems every single time. What this setting does is it gets referred to before moving to the next location to ensure that a group mate has not been left behind and it's safe to proceed. I would highly recommend at least 50 units for groupGap. The navDistance ... also I would adjust but it's not detrimental where you have it.
Grind should be as hands off as possible. Please let me know how the adjustments to those settings works out for you.
- Seller
- #1,533
I have never seen a roamer at the end of Shei Vinitras, that's why the toons get parked in that spot. It is a safe location or at least was. I'll review the instance and see if they have changed something. Thank you for letting me know about this.
In regards to full mana outside vs inside, I'll give it thought. A knee jerk reaction to a once off problem is never the right approach. Rather I'll review the instance and make adjustments as possible for safety.
- Seller
- #1,534
Which class toon is doing this and which automation tool (rgmercs/cwtn/ka/etc?)
- Seller
- #1,535
I have this fixed, I'm hoping to push an update later tonight. Weekends are busy family time sorry!
If you haven't configured your classes to act right, they won't. That being said I am aware of the door targeting and clearing of target.
- Seller
- #1,536
The next time your toon behaves like they are on strike or a phone call, please enable debug (/grind debug) and share with me what it's complaint is.
- Buyer
- #1,537
If it does it again I'll do that.
Last edited:
- Buyer
- #1,538
I ran my group up to the quest giver, ran /grind start hf. That's it. It grabbed quest, ran the team to the doorway and presented that error.
- Buyer
- #1,539
thanks boss for all your hard work, you the best!
- Buyer
- #1,540
i am seeing it on my tank, assist , ldr I keep the same char in control so i dont get confused, he is a SK
I swapped to the GD mission ( forgot its name) and it is doing it there aswell, to continue, on i have to manually move to the next bunch of mobs, the /grind then keeps running back to old spots where there are no mobs (when it comes up moving to spot X/32 )
I am using plugin MQ2eskay on him
- Buyer
- #1,542
can confirm this wipe, from time to time, in the shei grind since it was released. Very Low percentile, but does happen
- Buyer
- #1,543
I've been thinking on it further, the group was killing rather slowly, 45kph avg. Could it be repops? I added my zerker and pulled my chanter we're up to 59 KPH now and havent had the problem arise since.
- Buyer
- #1,544
I bought a new hard drive ( a super fast m2) yesterday so reformatted and set eq and MQ up in that
ran through the restless assualt mission a couple of times, keeping an eye on what was going on.
now, I dont know if i am a window missing ( likely, the screen doesent quite look the same) but i didnt see the "stuck gem detected - true" message
But, I noticed that the team was running back to spots and then just staying there.
From what I can tell it seems to be that if the team progresses to a location [moving to location X/32] kills whatever is there but moves out of the circle in the fight ( adds or push or whatever) they run back to that location, then move on
but if during that fight the push or whatever gets an add from the next location, the team moves back to the previous location, then moves to the next and stays there, never to move
Now it doesetn happen at every mobless location so I guess there is a bit more to it, but so far that is what I have spotted
ran through the restless assualt mission a couple of times, keeping an eye on what was going on.
now, I dont know if i am a window missing ( likely, the screen doesent quite look the same) but i didnt see the "stuck gem detected - true" message
But, I noticed that the team was running back to spots and then just staying there.
From what I can tell it seems to be that if the team progresses to a location [moving to location X/32] kills whatever is there but moves out of the circle in the fight ( adds or push or whatever) they run back to that location, then move on
but if during that fight the push or whatever gets an add from the next location, the team moves back to the previous location, then moves to the next and stays there, never to move
Now it doesetn happen at every mobless location so I guess there is a bit more to it, but so far that is what I have spotted
- Seller
- #1,545
If it stops enable debug (/grind debug) to see what the hold up is. I would assume that your group gap is the cause. Meaning that you have this value set very low and your group is spread out further than the group gap value.
- Seller
- #1,546
That error is presented when there is no Target or the Target is not Shalowain nor Elisel. Now this could be because of a few reasons, effectively losing target of the quest mob. When you `/grind start hf` or `/grind start ff` the plugin will acquire target and request the instance. If your toon isn't pause it's very likely that you might target self for a buff if in an active state.
I've done some testing this morning, 5 flips of HaF, no issues.
The screen shot above displays the Grind.Instance of 17; related the to enum to the right of LSHaF; just for added visibility.
Not being at your KB I'm not sure what your toon was doing.
- Seller
- #1,547
that's a very low kill rate. The end of the instance is marked as a red X on this map:
there are no roamer that go there.
If you do encounter one, I'd like to see a picture of the map with spawns visible please. I've flipped this instance several hundreds if not thousand times. The reason the exit was placed there, was because it is safe.
Are you by chance using a Lua or LEM which is pausing Grind prior to the exit to regain mana mid-instance?
- Seller
- #1,548
I'm going to need more than what you are providing here. I've just tested the Shei grind and there's no stopping occurring. Also the fact that a few folks here are saying there is some random roamer at the end, would negate that this is a global problem.
When you return to Shei to perform a test, enable debug with `/grind debug` and share what it complains about please. I suspect a group distance issue. Also please share your MQ2Grind.ini file with me in message and let me know how you control your group classes, for instance Warrior = MQ2War, Bard = RGMerc, etc.
Thanks in advance.
- Seller
- #1,549
Stuck gems is an EQ problem. It's been around for quite a while. That's why some automation detects it and attempts to resolve it for you. If it's not being automatically corrected, best to give your system a restart. Sounds like a lame answer, but it's the only one I can offer for that problem.
- Buyer
- #1,550
to be fair, i did more than reboot my computer, i totally rebuilt it ( new hard drive, new op system) and that seems to be resovled
Putting the team on Follow - seems to reduce the going to a spot and staying there ( doesent eliminate it but does reduce it)
- Buyer
- #1,551
mq2 class plugins don't spam stuckgem detected - that is a kissassist error message
- Seller
- #1,552
Having them on follow is defeating what the plugin is doing and bypassing finding out what the problem is.
- Buyer
- #1,553
why is it defeating the plugin? they follow the tank doing their thing, wizard nukes, mage send pet and nukes, cleric heals, chanter mezzes adds etc etc.
As far as finding out what the problem, is, you tell me what logs or how to turn them on or watever logging function there is, and i will of course do it and send you the results
- Seller
- #1,554
Simply: /grind debug (as a toggle, which means that command will also disable the debug output)
That will present to your screen additional information. It's very verbose, and as such I'm certain it will tell you what precisely the problem is when it doesn't move.
- Buyer
- #1,555
Well, I do have an answer to my issue. Just not sure why it was an issue. I normally buff up on guild hall, pause everyone, go to zone/quest giver and /grind start. For hero's forge, if I'm paused when I start the grind, I get that error.
So if I want to run this one, I'll just do things a touch different.
So if I want to run this one, I'll just do things a touch different.
- Seller
- #1,556
That just doesn't make sense to me. HaF and FF use the same logic.
- Seller
- #1,557
hytiek updated MQ2Grind with a new update entry:
Additional update for LS entry and group tethering decisions
Read the rest of this update entry...
Additional update for LS entry and group tethering decisions
Read the rest of this update entry...
- Buyer
- #1,559
I 'm not using a Lua or lem to pause to med but I did have several deaths during those runs. I'm thinking those coupled with the low kill rate sealed my doom. Now that I've fix the problems on my toons and upped my kill rate it hasnt happened. . I had the suicidal bard and shaman, come to find out they were chasing too closely so they'd overshoot even without selo's. If you ever need a beta tester to see just how bad an idiot can do, let me know! Sorry for the headache.
- Buyer
- #1,560
Debug reports Won't move due to isGroupTogether. I am using all CWTN plugins for 2 mages, SK, Enc, Clr, and Rogue. All of the chars report they are navigating to the tank and reached destination. Four of the chars at 58+ feet away from tank.
Like I said earlier this is not an issue for the GD mission.
Like I said earlier this is not an issue for the GD mission.