• 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
MQ2Grind

Release MQ2Grind 3.1.52471.11

Overview Instructions F.A.Q. Updates (94) Reviews (81) History Discussion Terms and conditions
So fun little tip for something that has been around since the build. If your low level char you are powerleveling dies sometimes from aggro - just block the run speed buffs. In my case I blocked selos. Pretty much guaruntees he is there for xp but never there for the mob attacking them. have not had a death since doing it and it's such a simple tweak.

Just remember to unblock once you hit the top levels.
 
Meatball_Sammich said:
i was wondering if there is a way to get this to pause to let group members med, and resume on its own?
Click to expand...

Somebody smarter than me could probably write this in reacts. The interesting thing though is if you resumegrind in reacts not sure how you would stop that.
 
Just used this to do Goblins and Fools in Frontier Mountains (EoK)
Ran flawlessly
I wasn't sure what to expect, but it wasn't something this smooth.
At level 107, wearing TBM level 100 augs insides level 70 armor/weapons, I blew through the instance in approximately 20min earning 20% of a level experience.

10/10 will continue to watch in amazement
 
Naeeldar said:
So fun little tip for something that has been around since the build. If your low level char you are powerleveling dies sometimes from aggro - just block the run speed buffs. In my case I blocked selos. Pretty much guaruntees he is there for xp but never there for the mob attacking them. have not had a death since doing it and it's such a simple tweak.

Just remember to unblock once you hit the top levels.
Click to expand...
This works and for GMM i also found that having a caster in my group do group invis and then blocking it on all my other chars works well also, you can even add the block spell / remove block spell lines to your grind start / end parameters. This also helped me a ton figured i'd pass it along!
 
Hytiek may I make a suggestion.

Can you put the group in tank / assist mode when waiting to exit grind.

I'm doing the grind in Gnome Memorial Mountains and when the crew reaches the end sometimes a roamer is moving about and just starts chopping away at the group, and because they are all paused no one fights back and the whole crew could wind up dying.
 
rdawgemfl said:
Hytiek may I make a suggestion.

Can you put the group in tank / assist mode when waiting to exit grind.

I'm doing the grind in Gnome Memorial Mountains and when the crew reaches the end sometimes a roamer is moving about and just starts chopping away at the group, and because they are all paused no one fights back and the whole crew could wind up dying.
Click to expand...
Hey there - thanks for letting me know about this. I'll look into a solution for this asap.
 
Sorry if this has been answered. I didn't look through every page. 2 questions.
1st. When ever any of my group members die, it just pauses the grind and never resumes. What might I be doing wrong. I have tried setting the pause during death for 60 seconds and 0 seconds. no change. it just pauses then I have to manually resume every time which is a pain.
2nd. I am running 2 groups, 1 with a SK tank, and one with a War tank. however when I set say the War tank to CWTN War. it changes it on my SK grind as well, so it jacks it all up if I ever stop, can now My sk is working off of WAR CWTN commands Vice Vrs.. is there a way for each character that runs the grind for it to be independent to that character?
 
I asked this in Grind and didn't get a response. So I apologize.
I am running 2 groups, 1 with a SK tank, and one with a War tank. however when I set say the War tank to CWTN War under tank. it changes it on my SK grind to war as well, so then is messes my sk up cause its sending cwtnwar commands, now My sk is working off of WAR CWTN commands Vice Vrs. if I switch it to SK. is there a way for each group that runs the grind for it to be independent to that character, or group and not change it for everyone?
 
classifyde said:
I asked this in Grind and didn't get a response. So I apologize.
I am running 2 groups, 1 with a SK tank, and one with a War tank. however when I set say the War tank to CWTN War under tank. it changes it on my SK grind to war as well, so then is messes my sk up cause its sending cwtnwar commands, now My sk is working off of WAR CWTN commands Vice Vrs. if I switch it to SK. is there a way for each group that runs the grind for it to be independent to that character, or group and not change it for everyone?
Click to expand...
Crating a new thread knowing it shouldn't be it's own thread isn't the answer tho.

Can repost in here or msg @hytiek

Grind doesn't auto resume - it is intended to be automate grinding while being attended
 
classifyde said:
I asked this in Grind and didn't get a response. So I apologize.
I am running 2 groups, 1 with a SK tank, and one with a War tank. however when I set say the War tank to CWTN War under tank. it changes it on my SK grind to war as well, so then is messes my sk up cause its sending cwtnwar commands, now My sk is working off of WAR CWTN commands Vice Vrs. if I switch it to SK. is there a way for each group that runs the grind for it to be independent to that character, or group and not change it for everyone?
Click to expand...
I run a WAR and SHD groups as well. Currently you would configure (press 1 button) to configure the Tank that you want to start with. Get that group up and going. Then on the other tank, reconfigure as applicable and start. At no time would the two configurations overlap unless you run a reload on the 1st group - which would then take on the configuration of the second.
 
Sic said:
Crating a new thread knowing it shouldn't be it's own thread isn't the answer tho.

Can repost in here or msg @hytiek

Grind doesn't auto resume - it is intended to be automate grinding while being attended
Click to expand...
Thanks, didnt know about the own thread rule. before you say go read the rules. I will read them. My bad, and thank you for the response. The delay after rezing tab makes it seem like it is a function. That is why I asked. No worries.

hytiek said:
I run a WAR and SHD groups as well. Currently you would configure (press 1 button) to configure the Tank that you want to start with. Get that group up and going. Then on the other tank, reconfigure as applicable and start. At no time would the two configurations overlap unless you run a reload on the 1st group - which would then take on the configuration of the second.
Click to expand...
Thank you!
 
my grind seems to be getting hung up on doors at 32/54 and 52/54 in "The Call"

Does anyone have a MQ2Nav file that fixes this issue?
 
Hey there, been running this for the passed couple of days with MQcleric, MQShammy, MQZerk, and MQEskay along with kissassist for my RNG and BRD. I have noticed that my party will simply NOT stop to med up for some wierd reason. All the settings on MQEskay are setup as I normally have them when Im doing like FM or something, but here they just won't stop to med. Any way to fix this PLEASE lmk.
 
Dojer9484 said:
Hey there, been running this for the passed couple of days with MQcleric, MQShammy, MQZerk, and MQEskay along with kissassist for my RNG and BRD. I have noticed that my party will simply NOT stop to med up for some wierd reason. All the settings on MQEskay are setup as I normally have them when Im doing like FM or something, but here they just won't stop to med. Any way to fix this PLEASE lmk.
Click to expand...
The settings for the cwtn plugins to stop pulls would be if you were using the plugins for pulling - you are using mq2grind, which currently doesn't have functionality to do that.
 
Dojer9484 said:
Yes but it asks me to use mq2eskay when I setup the tank, shouldn't that refer it to the eskay to allow the group to med?
Click to expand...
Mq2grind works with all the automations, not just cwtn plugins, and if the cwtn plugin isn't doing the pulling and such, then the cwtn plugin isn't going to stop pulling to med
 
So should I use the CWTN to do the pulling on the tank? Would that allow it to Med? Im sorry, im not totally familiar with how cwtn plugin works ( or if that stands for the MQ2Eskay pluging )

Also, side note...watched your videos on so many things and wanted to say thank you for being awesome! They have helped me understand quite a bit about other plugins and macros!
 
Dojer9484 said:
So should I use the CWTN to do the pulling on the tank? Would that allow it to Med? Im sorry, im not totally familiar with how cwtn plugin works ( or if that stands for the MQ2Eskay pluging )

Also, side note...watched your videos on so many things and wanted to say thank you for being awesome! They have helped me understand quite a bit about other plugins and macros!
Click to expand...
No. U are using mq2grind - if you wanted the cwtn plugins (including mq2eskay) to do the pulling you wouldn't be using grind :p

Some people choose to use a react or Lua to pause while medding
 
First of all thank you for this plugin it's absolutely fantastic!

Somewhere earlier in the thread someone mentioned having to make a /grind resume script because it kept pausing and I think I tracked down the issue.

Using a Shaman (CWTN plugin). If a char dies, it summons them back to corpse during battle, but after the mobs are dead MQ2Grind pauses (group member corpse detected) because shaman can't use rez unless out of combat, so it has to wait out the timer before rez, this causes it to require a manual /grind resume to continue. Is there any way to have it auto-unpause and after like a 2min check to see if that group member corpse has been taken care of and auto-resume after that first (group member corpse detected)? Maybe a check for corpse and pause and a re-check for corpse after 2mins loop?

I know the CWTN plugin is working as it's supposed to, but with a CLR the grind plugin doesn't have the same behavior because the CLR rez's during combat so MQ2Grind doesn't get to the "group corpse member detected" check and never has to pause.
 
ralen said:
First of all thank you for this plugin it's absolutely fantastic!

Somewhere earlier in the thread someone mentioned having to make a /grind resume script because it kept pausing and I think I tracked down the issue.

Using a Shaman (CWTN plugin). If a char dies, it summons them back to corpse during battle, but after the mobs are dead MQ2Grind pauses (group member corpse detected) because shaman can't use rez unless out of combat, so it has to wait out the timer before rez, this causes it to require a manual /grind resume to continue. Is there any way to have it auto-unpause and after like a 2min check to see if that group member corpse has been taken care of and auto-resume after that first (group member corpse detected)? Maybe a check for corpse and pause and a re-check for corpse after 2mins loop?

I know the CWTN plugin is working as it's supposed to, but with a CLR the grind plugin doesn't have the same behavior because the CLR rez's during combat so MQ2Grind doesn't get to the "group corpse member detected" check and never has to pause.
Click to expand...
It intentionally doesn't auto resume. It is intended for attended play. Some folks made mq2reacts to do that or other things, but it isn't a skill limitation, it is a design choice.

I do, however, 100% suggest getting a rez stick for your shammy
 
Sic said:
It intentionally doesn't auto resume. It is intended for attended play. Some folks made mq2reacts to do that or other things, but it isn't a skill limitation, it is a design choice.

I do, however, 100% suggest getting a rez stick for your shammy
Click to expand...

Just started a new team and noticed this behavior while I was watching. I thought it wasn't as intended due to the behavior not being the same as with CLR in group.

I'm running some ridiculously undergeared chars right now, so the deaths pile up :)

Totally understand the situation, thanks for the response!
 
I was having some issues with my lvl 111 toon greeting death around stop 17 or 18, paired with a 120 SK /Shaman & 3 mercs when doing Shei Vinitras. <- that is not the problem. I looked to set the "exit early at location number" to 16, to prevent the issue.

Alas the drop down only goes to 13 of 23. :-).

Clearly not an urgent update - just putting it out there for future improvements.

Thanks.

1654757376462.png
 
Here's a view of the auto-resume feature, I intentionally wiped my group, ran my healer back and began to rez, once the last corpse was rezzed, this is what the plugin now does for you:

1655828968002.png
So as you can see, the plugin detected that all PC corpses were resolved and instead of remaining in a paused state, it took over and resumed automatically.

While this scenario is extreme, the more common is where a single toon dies and gets rezzed but remains in a paused state. I know some have created MQ2Events and even MQ2Reacts - you should disable those which cover this update.

Please keep in mind, this update does NOT use campfire and zone you back in automatically on a full wipe; you need to handle that still.
 
ralen said:
First of all thank you for this plugin it's absolutely fantastic!

Somewhere earlier in the thread someone mentioned having to make a /grind resume script because it kept pausing and I think I tracked down the issue.

Using a Shaman (CWTN plugin). If a char dies, it summons them back to corpse during battle, but after the mobs are dead MQ2Grind pauses (group member corpse detected) because shaman can't use rez unless out of combat, so it has to wait out the timer before rez, this causes it to require a manual /grind resume to continue. Is there any way to have it auto-unpause and after like a 2min check to see if that group member corpse has been taken care of and auto-resume after that first (group member corpse detected)? Maybe a check for corpse and pause and a re-check for corpse after 2mins loop?

I know the CWTN plugin is working as it's supposed to, but with a CLR the grind plugin doesn't have the same behavior because the CLR rez's during combat so MQ2Grind doesn't get to the "group corpse member detected" check and never has to pause.
Click to expand...

The scenario you raised here, is now automatically handled.

Also I'm aware that some have written scripts to detect a full wipe and perform a number of actions to fully recover from a wipe --- the most recently update is NOT designed to remedy that and I will not ever provide such a feature.
 
Everquest02 said:
I was having some issues with my lvl 111 toon greeting death around stop 17 or 18, paired with a 120 SK /Shaman & 3 mercs when doing Shei Vinitras. <- that is not the problem. I looked to set the "exit early at location number" to 16, to prevent the issue.

Alas the drop down only goes to 13 of 23. :-).

Clearly not an urgent update - just putting it out there for future improvements.

Thanks.

View attachment 40255
Click to expand...

Thanks for letting me know about this short-coming. While I published an update today, the fix is not available in it, but will be in the next update after 6/22/2022.
 
1655859737584.png

This happens every time I zone into Restless Assault. No one is gating, porting, etc, but is possible they are zoning in. So it will never auto resume. Usually, it would retry for late/random zoners, but now it straight pauses. How do we revert?

Additionally, it never had a PC camp radius check before, but does now? I have not changed anything on my end except update the plugin. At least I have never seen it on my Bard go off before and cause the plugin to end. There is an afk group that sits right there at the zoneout point. Constantly. Never had an issue before, but since updating, it does.

Edit - Reduced my CampRadius in KA to 5. Still blurts out the PC Check on bard, but at least it will now continue to zone people in, instead of ending the grind.

Edit 2 - It does appear that my Driver (SK) will say ready before another toon randomly. I looked though the settings, nothing I can see to change to fix this behavior. In the past, the plugin would just have people say ready and wait. Now it pauses and will not resume.
 
Last edited:
Shadow said:
This happens every time I zone into Restless Assault. No one is gating, porting, etc, but is possible they are zoning in. So it will never auto resume. Usually, it would retry for late/random zoners, but now it straight pauses. How do we revert?

Additionally, it never had a PC camp radius check before, but does now? I have not changed anything on my end except update the plugin. At least I have never seen it on my Bard go off before and cause the plugin to end. There is an afk group that sits right there at the zoneout point. Constantly. Never had an issue before, but since updating, it does.

Edit - Reduced my CampRadius in KA to 5. Still blurts out the PC Check on bard, but at least it will now continue to zone people in, instead of ending the grind.

Edit 2 - It does appear that my Driver (SK) will say ready before another toon randomly. I looked though the settings, nothing I can see to change to fix this behavior. In the past, the plugin would just have people say ready and wait. Now it pauses and will not resume.
Click to expand...

The changes that were introduced do not relate with what you are experiencing.

There were 3 changes.

1) Added variable to be displayed to avoid a crash (red = old, green = what is now)
1655870723877.png

2) Replaced statically defined group members being sent a taskadd; despite possibly being a merc
1655870814919.png
Essentially what you see above is the removable of the EzCommand in green and red, addition of manage_group("taskadd"); which checks for group member being a merc or not.

3) Lastly, added a chunk of code specifically to handle the auto-resume when a group member dies and is rezzed. Too much code, not sharing it.

None of the changes nor additions relate to the problem you are sharing.
 
hytiek said:
The changes that were introduced do not relate with what you are experiencing.

There were 3 changes.

1) Added variable to be displayed to avoid a crash (red = old, green = what is now)
View attachment 40511

2) Replaced statically defined group members being sent a taskadd; despite possibly being a merc
View attachment 40512
Essentially what you see above is the removable of the EzCommand in green and red, addition of manage_group("taskadd"); which checks for group member being a merc or not.

3) Lastly, added a chunk of code specifically to handle the auto-resume when a group member dies and is rezzed. Too much code, not sharing it.

None of the changes nor additions relate to the problem you are sharing.
Click to expand...
Thank you for speaking with me on Discord and pointing out that it most likely is a client memory issue. Restarted PC, and attempting again.
 
I would like to know if this will work with lower level groups - around 78.

Thanks!
 
redmq2 said:
I would like to know if this will work with lower level groups - around 78.

Thanks!
Click to expand...

Hey there, thanks for finding the resource. There's quite a lot of information available at https://www.redguides.com/community/resources/mq2grind.1967/

But to save you time, here is a list of available Grinds as of today: (starting at level 95+)

1655990986792.png

I've considered looking at TLP related, but most of them require changes to the core engine that I'm not sure I want to do at this time.
 
I appreciate teh
hytiek said:
Hey there, thanks for finding the resource. There's quite a lot of information available at https://www.redguides.com/community/resources/mq2grind.1967/

But to save you time, here is a list of available Grinds as of today: (starting at level 95+)

View attachment 40528

I've considered looking at TLP related, but most of them require changes to the core engine that I'm not sure I want to do at this time.
Click to expand...
I appreciate the response - I will level my chars a little more - thanks!
 
I'm having a problem that I can't figure out. I am running this from my SK, and it will go to each spot and target the mob from distance then just stand there trying to attack until I manually move my character forward then it will engage as normal. Is there a setting somewhere I need to change?
 
You must log in or register to reply here.
Release MQ2Grind
Next unread thread 🦁

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top
Cart

Cart

Total -