• 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
Hi! So I bought MQ2Grind a couple of weeks ago and finally got the chance to start messing around with it. I was watching the overview by Sic which seems very helpful except I can't get the /grind UI window where it seems like you're able to adjust settings and let MQ2Grind know if you're running kissassist or MQ2 etc. I was able to see most of the commands but in Sic's video under General commands he shows a /grind show|ui|gui which, as you can, I don't have. I tried just typing it in but it won't come up. Now oddly enough, I did type in /grind start and off I went into the mission but it's not really running correctly. My tank ran into the caves of GD and started fighting wurms 3 at a time while cleric and necro were still at zone in. Also, zerker won't auto engage mob without me clicking target and hitting the attack button but I'm thinking that because I never got the chance to use the set-up page with /grind show gui it's not running right.

Any help here?

1641673190081.png
 
Hoggins said:
Hi! So I bought MQ2Grind a couple of weeks ago and finally got the chance to start messing around with it. I was watching the overview by Sic which seems very helpful except I can't get the /grind UI window where it seems like you're able to adjust settings and let MQ2Grind know if you're running kissassist or MQ2 etc. I was able to see most of the commands but in Sic's video under General commands he shows a /grind show|ui|gui which, as you can, I don't have. I tried just typing it in but it won't come up. Now oddly enough, I did type in /grind start and off I went into the mission but it's not really running correctly. My tank ran into the caves of GD and started fighting wurms 3 at a time while cleric and necro were still at zone in. Also, zerker won't auto engage mob without me clicking target and hitting the attack button but I'm thinking that because I never got the chance to use the set-up page with /grind show gui it's not running right.

Any help here?

View attachment 36748
Click to expand...
Are you using Next? I think /grind show gui will only work in that version
 
I do not use MQNext as I am not 100% on what it is or how to use it tbh.
So knowing that, should my next course of action be to install "Next" and then try?
 
Hoggins said:
I do not use MQNext as I am not 100% on what it is or how to use it tbh.
So knowing that, should my next course of action be to install "Next" and then try?
Click to expand...
Absolutely. Install Next ASAP.
I was having issues with grind because I am too stupid to properly set my Tank & character configs up properly. With Next and the /grind ui, I had everything running great as soon as I did the upgrade. Literally just had to click a couple buttons for each character and that was it.
Sic's Next migration video is wonderful and will have you up and running quickly and painlessly. Seeing as how RG won't be supporting the current MQ2 in the future and Grind and other plugins already require it for most of their enhancements, you're gonna have to do it soon anyway.
 
My SK hit 117. I bought all of his spells and tomes, but now when I try to run MQ2Grind, I get this:
1641687287067.png

I can't see what spell it is that he is trying to cast. I've tried clicking the BYOS in the settings, but that didn't help.

Any ideas?

On a positive note - I've worked my archery skill to max while trying to figure out what is going on.

🤣
 
Colonel - USMC Retired said:
My SK hit 117. I bought all of his spells and tomes, but now when I try to run MQ2Grind, I get this:
View attachment 36754

I can't see what spell it is that he is trying to cast. I've tried clicking the BYOS in the settings, but that didn't help.

Any ideas?
Click to expand...
I had this same issue. tried everything, blocking the chanty mind crack spell, block this spell, and looked up the spell in his book, and realized it was also an illusion form...I went to settings in MQ2ESKAY and clicked off "autoremoveillusion". Lo and behold....issue went away...I unblocked the spells I had blocked...and he went right back to tanking....after group wiped of course....
 
Holy smokes.

That worked.

I never would have guessed that was what the issue was. Thanks, Stregg!

Nevermind - it didn't work. It went a couple steps further in Grind and stopped again, trying to cast something that I didn't have memorized...
 
your "you don't have this spell memorized" This is an mq2grind configuration issue.

configure your grind.

re: your other part, check the faq for mq2eskay.
 
Success!
Thank you for the help and want to say Thank you to Sic for all the videos posted. It really does help tremendously.

-Hoggs
 
Sic said:
your "you don't have this spell memorized" This is an mq2grind configuration issue.

configure your grind.

re: your other part, check the faq for mq2eskay.
Click to expand...
Thanks Sic.

I've been successfully running Grind for weeks; it's been configured and I've had no issues until my SK hit 117.

I'd previously watched the video and read the FAQ countless times, but finally figured that it was the Voice of Sagacity line that was causing the conflict from my 117 Chanter. Blocked that spell and now it (again) runs with no issues. I still don't know why it only started having this affect at 117 and not from 114, but any solution is a good solution. 😉

Thanks for pointing me back in the right direction - as always!
 
yes, because you hit 117, you would have been using the spell that was previously in your going configuration.

upon leveling and getting as new spell that mq2eskay is memorizing, you need to update the mq2grind configuration to use that new spell, and not try to use a spell from a previous tier
 
Sic said:
yes, because you hit 117, you would have been using the spell that was previously in your going configuration.

upon leveling and getting as new spell that mq2eskay is memorizing, you need to update the mq2grind configuration to use that new spell, and not try to use a spell from a previous tier
Click to expand...
Thanks - Since I started with a consistent spell, I never saw the difference.

As always, you rock!
 
how do you do this?

"upon leveling and getting as new spell that mq2eskay is memorizing, you need to update the mq2grind configuration to use that new spell, and not try to use a spell from a previous tier"

there is no spell section in the config file
 
wynge said:
how do you do this?

"upon leveling and getting as new spell that mq2eskay is memorizing, you need to update the mq2grind configuration to use that new spell, and not try to use a spell from a previous tier"

there is no spell section in the config file
Click to expand...
in your tank configuration of your /grind ui under your GTDistPullCmd

i think future updates it defaults to a /cast 9 for the cwtn plugins since for all the grind levels of the cwtn plugins we would use that gem slot
1641858023918.png

if it says /cast "some old spell you don't have memorized" update that to /cast "some spell you do have memorized"

it is the hard coded configuration of casting a spell that is causing the issue

or you can just update it to /cast 9
 
I'm considering buying this plugin but my crew is only level 90. Does this support any missions in this level range?
 
BTW SHDs (and some day PALs): you can smack the MQ2Eskay (or MQ2Paladin eventually!) on the Tank configuration and it will change the command to /cast 9 which is where the CWTN plugin will have it's pull spell.
 
I am having a bit of an issue with the plugin not resuming after rezing one of the group. Any help would be appreciated :)
 
Esiah said:
I am having a bit of an issue with the plugin not resuming after rezing one of the group. Any help would be appreciated
Click to expand...
I recall reading it somewhere but at a quick glance i didn't see it. My recollection is that after a death/rez you will need to issue the command /grind resume
 
Oldman66 said:
I recall reading it somewhere but at a quick glance i didn't see it. My recollection is that after a death/rez you will need to issue the command /grind resume
Click to expand...
Yeah, I assumed the delay after rez would resume the plugin. But that is not doing what I thought it would.
 
Here is the mq2react I made:

Resumegrind:
action: /grind resume
condition: "${Grind.Paused} && !${Group.AnyoneMissing} && !${SpawnCount[pccorpse]}"
sleep_frames: 15
 
Last edited:
Esiah said:
Here is the mq2react I made:

Resumegrind:
action: /grind resume
condition: "${Grind.Paused} && !${Group.AnyoneMissing} && !${SpawnCount[pccorpse]}"
sleep_frames: 15
Click to expand...
This is the first time I've tried to use MQ2React.

Do you just paste this into the yaml file? When I do a "/react list", it still only shows the example.
 
I have been running grind successfully for a week or so now, but suddenly, a new issue has popped up and I'm not sure what is causing it. I am using it on Goblins and Fools, four toons and two actual mercs (laptop struggles running 6 EQ clients). Upon entry to the instance, it appears that the tank is stuck in a loop trying to check people have auto accepted. My MQ box is saying

[MQ2Grind] Group member(s) are missing. Trying to get them here, stand by.
[ -->(group_server_charactername) ] /autoaccept add charactername
[MQ2AutoAccept :: User Charactername already exists

Then, it goes and does that for all of the group members. Everyone is loaded into the zone after having successfully accepted the shared task, loading in, etc. I noticed that it acted a little weird the first run through in this session. All but one character loaded in as normal, but my bard was delayed about 60 seconds during the zone in process. He eventually zoned in and it went through one cycle of this autoaccept loop. After that it worked as normal. Then, after exiting the instance at its designated checkpoint, it got stuck in this loop as soon as they reentered.

I have checked to make sure everything is loaded, updated etc. What am I missing / not doing?

Thanks for any advice!
 
asplinteredcell said:
I have been running grind successfully for a week or so now, but suddenly, a new issue has popped up and I'm not sure what is causing it. I am using it on Goblins and Fools, four toons and two actual mercs (laptop struggles running 6 EQ clients). Upon entry to the instance, it appears that the tank is stuck in a loop trying to check people have auto accepted. My MQ box is saying

[MQ2Grind] Group member(s) are missing. Trying to get them here, stand by.
[ -->(group_server_charactername) ] /autoaccept add charactername
[MQ2AutoAccept :: User Charactername already exists

Then, it goes and does that for all of the group members. Everyone is loaded into the zone after having successfully accepted the shared task, loading in, etc. I noticed that it acted a little weird the first run through in this session. All but one character loaded in as normal, but my bard was delayed about 60 seconds during the zone in process. He eventually zoned in and it went through one cycle of this autoaccept loop. After that it worked as normal. Then, after exiting the instance at its designated checkpoint, it got stuck in this loop as soon as they reentered.

I have checked to make sure everything is loaded, updated etc. What am I missing / not doing?

Thanks for any advice!
Click to expand...

I'm not sure what to suggest here yet, but I wanted to let you know that I'll look into what might cause this, tonight. If you're able to debug a bit, once your group is all in the instance, what's the output of: /echo ${Group.AnyoneMissing} ?
 
Colonel - USMC Retired said:
This is the first time I've tried to use MQ2React.

Do you just paste this into the yaml file? When I do a "/react list", it still only shows the example.
Click to expand...
Here is how my yaml file looks. Of course you will want to replace your server name and character name. I attached a copy of the file below because yaml needs formatting.

globals:
{server name here}:
{character name here}:
Resumegrind: enabled
reacts:
Resumegrind:
action: /grind resume
condition: "${Grind.Paused} && !${Group.AnyoneMissing} && !${SpawnCount[pccorpse]}"
sleep_frames: 15
 

Attachments

Last edited:
hytiek said:
I'm not sure what to suggest here yet, but I wanted to let you know that I'll look into what might cause this, tonight. If you're able to debug a bit, once your group is all in the instance, what's the output of: /echo ${Group.AnyoneMissing} ?
Click to expand...
I just typed the echo command in to the MQ box and it says "FALSE"

I got everyone in to the instance upon initial /grind start and it works fine for the first time. It is doing this upon re-entry, just to clarify.
 
asplinteredcell said:
I just typed the echo command in to the MQ box and it says "FALSE"

I got everyone in to the instance upon initial /grind start and it works fine for the first time. It is doing this upon re-entry, just to clarify.
Click to expand...

I found some time and have done some testing, I've hit a really odd scenario that I have no explanation about. I had 4 PC and 2 MERC; after the 5th run of Goblins and Fools; TOON #2 dropped the main group on it's own during a zoning and it's MERC remained in the main group. Are you sure all of your toons are in the group or did you run into this same thing?
 
hytiek said:
I found some time and have done some testing, I've hit a really odd scenario that I have no explanation about. I had 4 PC and 2 MERC; after the 5th run of Goblins and Fools; TOON #2 dropped the main group on it's own during a zoning and it's MERC remained in the main group. Are you sure all of your toons are in the group or did you run into this same thing?
Click to expand...
Yep, I just physically clicked on each client, walked them around manually while checking their group status. It did make me wonder if the mercs are affecting it. I am about to run it without them to see if I get the same error. I'll update soon.
 
Ok, this was odd. After I manually walked them around inside the Droga spawn in area, I was typing my previous message and saw them start running around killing things. 🤨 That is really weird. I have had them sitting there stuck in that loop while I was working for the last couple hours... they never once moved an inch.
 
asplinteredcell said:
Ok, this was odd. After I manually walked them around inside the Droga spawn in area, I was typing my previous message and saw them start running around killing things. 🤨 That is really weird. I have had them sitting there stuck in that loop while I was working for the last couple hours... they never once moved an inch.
Click to expand...

By chance have you updated the DROGAB mesh? If not, please do so immediately :)

EDIT: So I thought it might be easier to just attach it here for you @asplinteredcell
 

Attachments

Last edited:
hytiek said:
By chance have you updated the DROGAB mesh? If not, please do so immediately :)

EDIT: So I thought it might be easier to just attach it here for you @asplinteredcell
Click to expand...
Gotcha, thanks. I had updated my meshes pretty recently, but I will do this one next.

Update before I do that. Out of my four PC, my tank (PAL) and slot 2 (BRD) were using DPS mercs. I have used the tank's DPS merc before, and I have used the BRD's healer merc before. I have never used a DPS merc on the BRD. When I loaded up today I decided to through both mercs on so I could move through a little faster. I decided to try removing the BRD's merc prior to them leaving the instance just a moment ago. When they zoned out, they went through the regular task acquire, then zoned back in. All day long they have been getting stuck at that point. However, they zoned in and got right to business, happily killing goblins. I have no idea why the BRD's merc would have mucked things up like that. Or maybe correlation doesn't mean causation. Just wanted to share that update.
 
That seemed to be what was gumming up the system. It has run over an hour without incident. The only thing different that I can think of that I did with the mercs (other than using DPS instead of healer) is that I actually went in to the BRD's .ini and changed the merc setting to =1 instead of just manually popping it. I'm going to try popping mercs on other toons to see if I can recreate the issue. I'll let you know what I come up with.
 
After running it in various configs throughout the afternoon, @hytiek , I have the following results:

-Tank (115 Pal) ran DPS merc consistently with no problems.
-PC 2 (115 BRD) tried both a healer merc and a DPS merc. DPS merc would work on the initial entry to the instance, but would hang up invariably upon reentry. I then dropped the dps (melee) merc to run without a merc at all. That worked fine and would keep running as intended. Third, I tried the BRD's healer merc. That also worked upon reentry.
-PC 3 (115 CLR) tried a tank merc. It worked on initial entry, but fell in to the autoaccept / looking for member loop upon reentry.
-PC 4 (111 CLR) tried a healer merc. It worked fine initially and on reentry.

/echo ${Group.AnyoneMissing} showed FALSE each time it got stuck in the loop.

So, for the short fix, I am just not using melee mercs with anyone other than the tank... but this is a strange phenomenon.
 
Esiah said:
Here is how my yaml file looks. Of course you will want to replace your server name and character name. I attached a copy of the file below because yaml needs formatting.

globals:
{server name here}:
{character name here}:
Resumegrind: enabled
reacts:
Resumegrind:
action: /grind resume
condition: "${Grind.Paused} && !${Group.AnyoneMissing} && !${SpawnCount[pccorpse]}"
sleep_frames: 15
Click to expand...
Thanks! So to clarify, it would look like this?
[CODE lang="yaml" title="Resume Grind React"]globals:
EverQuest: (just an example server)
StupidToon:
Resumegrind: enabled
reacts:
Resumegrind:
action: /grind resume
condition: "${Grind.Paused} && !${Group.AnyoneMissing} && !${SpawnCount[pccorpse]}"
sleep_frames: 15[/CODE]
 
asplinteredcell said:
After running it in various configs throughout the afternoon, @hytiek , I have the following results:

-Tank (115 Pal) ran DPS merc consistently with no problems.
-PC 2 (115 BRD) tried both a healer merc and a DPS merc. DPS merc would work on the initial entry to the instance, but would hang up invariably upon reentry. I then dropped the dps (melee) merc to run without a merc at all. That worked fine and would keep running as intended. Third, I tried the BRD's healer merc. That also worked upon reentry.
-PC 3 (115 CLR) tried a tank merc. It worked on initial entry, but fell in to the autoaccept / looking for member loop upon reentry.
-PC 4 (111 CLR) tried a healer merc. It worked fine initially and on reentry.

/echo ${Group.AnyoneMissing} showed FALSE each time it got stuck in the loop.

So, for the short fix, I am just not using melee mercs with anyone other than the tank... but this is a strange phenomenon.
Click to expand...

I had tried this almost perfectly. I had no issue with Healer Merc - the issue I had once was DPS Merc. What fascinates me is that my experience had PC3 drop from group but the Merc remained in the group. I've talked with Sic and it seems that this is a new EQ issue over the last month or so. I'll keep looking into this, but at this time, I do not have a remedy or solution in mind.
 
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 -