• 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 (1 Viewer) 3.1.52471.11

hytiek

✨Broken TA Owner✨
Moderator
Joined
May 21, 2019
RedCents
16,692¢
hytiek submitted a new resource:

MQ2Grind - Group management for instance flipping

INTRO / INFO:
  • This automates the group farming of XP within an instance for privacy while you are monitoring and not sleeping or afk
  • This does not automate the completion of a group mission
  • Currently supports Restless Assault (ToV) instance, more to come
  • The route covers the wurm cave only, not the Tizmaks caves
  • The 'driver' of the plugin, must be a tank type (PAL, SHD, WAR)
View attachment 26325

Mentions:
Redbot: Thank you for this...

Read more about this resource...
 
So... you run this in say GD, it runs to the mission giver, gets the mission, everyone (?) says ready to get in, it runs everyone (?) to the wurms, clears them out (with basic combat abilities, or kissassist, or what?) drops mission and re-gets? Rinse-repeat?

What are my characters running? Are they all on CTWN / ChaseAssist or Kiss Assist chase modes, and the driver is running the macro? Issuing commands over EQBCS? What is my driver (tank) doing for combat?

I'm happy to play with this once servers come up between now and tomorrow.
 
So... you run this in say GD, it runs to the mission giver, gets the mission, everyone (?) says ready to get in, it runs everyone (?) to the wurms, clears them out (with basic combat abilities, or kissassist, or what?) drops mission and re-gets? Rinse-repeat?

What are my characters running? Are they all on CTWN / ChaseAssist or Kiss Assist chase modes, and the driver is running the macro? Issuing commands over EQBCS? What is my driver (tank) doing for combat?

I'm happy to play with this once servers come up between now and tomorrow.
Idk about the rest, but it says dannet is required
 
Yes it has been tested with characters running cwtn plugins, kissasssist, rgmercs....it creates an ini for you to set up your classes and what macro/plugins they run. Then the plugin handles the rest, navigating through the caves, pulling mobs....it does it all. Then exits task, gets again and on and on.
 
So... you run this in say GD, it runs to the mission giver, gets the mission, everyone (?) says ready to get in, it runs everyone (?) to the wurms, clears them out (with basic combat abilities, or kissassist, or what?) drops mission and re-gets? Rinse-repeat?

What are my characters running? Are they all on CTWN / ChaseAssist or Kiss Assist chase modes, and the driver is running the macro? Issuing commands over EQBCS? What is my driver (tank) doing for combat?

I'm happy to play with this once servers come up between now and tomorrow.

Essentially, you've got it. Few things which might help understand what this will assist with. So you'll need to be within /say distance of Zrelik in GD. If you aren't, the plugin will error and explain what you must do. I tried to make the user experience really friendly and provide as much protection for you as possible. So it checks if you are a tank, it checks if a MT/MA has been assigned. Once all the silly checks are done, it will create a campfire for you if yours is in the zone, close by, and expiring within a few hours.

Next, it will talk with Zrelik, get the quest, and then send instruction (based on your INI configuration, it's in your mq2 folder called MQ2Grind.ini) to each group member, and tell them to start up. Before entering the task, it will pause everyone, get inside, and make sure everyone is in before it starts running around killing stuff.

There's a hard coded route through the tunnels, i've tried everything possible to pull as few as possible at a time.

Loading dannet, is easy and won't interfere with your EQBC, I need it for a few things that are planned but not yet in the plugin. =) Ping me in discord if the INI doesn't make sense. I'm really looking forward to your feedback on this!
 
I've been working with hytiek on this. Remember to not only set the mq2grind.ini file to the classes below for your group, but also change the TANK section at the top. If you don't run a warrior (with mq2war) as your main driver, you will need to change the section. Ideally you want to use the commands you would use to get your group into automated chase mode.
 
YEAH NO good here lotta couldnt parse do command lines not sure what to edit on the grind ini could be me
 
YEAH NO good here lotta couldnt parse do command lines not sure what to edit on the grind ini could be me

if I recall some of the sample lines in the INI did not have a space between the ”/multiline” and the “;”.
that space (lack there of) gave me docommand errors
 
if I recall some of the sample lines in the INI did not have a space between the ”/multiline” and the “;”.
that space (lack there of) gave me docommand errors

You are right; there's two instances, in a comment:

;SK|PAL: GTDistPullCmd=/multiline; /cast Protest for Power; /face; /timed 20 /nav target log=off; /timed 25 /attack on
;WAR|SK|PAL: LTDistPullCmd=/docommand ${If[${Target.Distance} > 50,/ranged,/multiline; /nav target log=off; /timed 5 /attack on]}

Thanks for alerting me to it! :)

Should be:

;SK|PAL: GTDistPullCmd=/multiline ; /cast Protest for Power; /face; /timed 20 /nav target log=off; /timed 25 /attack on
;WAR|SK|PAL: LTDistPullCmd=/docommand ${If[${Target.Distance} > 50,/ranged,/multiline ; /nav target log=off; /timed 5 /attack on]}
 
I've flipped the instance probably about 20 times since last week and have only noticed 2 problems. The first was the spacing in the ini (which was an easy enough fix) and the other is toons trying to enter the instance before its ready. If my main toon tries to enter before its ready, he waits certain amount of time and attempts to enter again. However, if one of the other toons in group tries to enter too early and the main gets in, the toon left out is stuck until I manually /say ready. A few extra seconds before issuing the command to enter the instance would easily fix this. A "buffer" against the ever so common server lag.

That being said, I think this is a great plugin and look forward to seeing the finished product.
 
I've flipped the instance probably about 20 times since last week and have only noticed 2 problems. The first was the spacing in the ini (which was an easy enough fix) and the other is toons trying to enter the instance before its ready. If my main toon tries to enter before its ready, he waits certain amount of time and attempts to enter again. However, if one of the other toons in group tries to enter too early and the main gets in, the toon left out is stuck until I manually /say ready. A few extra seconds before issuing the command to enter the instance would easily fix this. A "buffer" against the ever so common server lag.

That being said, I think this is a great plugin and look forward to seeing the finished product.

I've seen and confirmed both of those and have full intention to fix it. =)

My daughter was born yesterday ... so this might take a bit, but I've got her next to me in a bassinette now for the first time so Mom can sleep. This might work for some late night coding ! :)

What I've found is that the Expedition window will populate, then about 15 seconds later, its flawless. I don't like delaying more than needed. So this is an option with a buffer. The other idea I had was setting up Dannet query to the group members, find out where they are, then zone them in first. When driver is the last, then zone in. This should help the smooth ride through the Grinds.
 
I've seen and confirmed both of those and have full intention to fix it. =)

My daughter was born yesterday ... so this might take a bit, but I've got her next to me in a bassinette now for the first time so Mom can sleep. This might work for some late night coding ! :)

What I've found is that the Expedition window will populate, then about 15 seconds later, its flawless. I don't like delaying more than needed. So this is an option with a buffer. The other idea I had was setting up Dannet query to the group members, find out where they are, then zone them in first. When driver is the last, then zone in. This should help the smooth ride through the Grinds.


I've had my own macro flipping instances for a while, and I do it like that. The driver zones everyone else in and then themselves.

My logic is group member x, checks their distance to the instance npc for say range and if not close enough will make sure they can nav to them and if not end the instance flipping and camp out. If they are close enough/can nav to the npc to be in range for say. Gets them to say the entry phrase and waits for them to have left the zone before moving to next group x

I also use a hard coded time for waiting for the instance to be ready, at 40 seconds seems to be the good spot where I don't ever see any issues, there's no way to know when it's ready other than spamming and doing an event check which really... If it saves you 20 seconds and hour that's nothing.

Also, in terms of kill paths I use a instance name with a number appended for a mq2nav waypoint that I manually have setup. Then for the instance profile it just needs to know how high that number goes. I have the GD instance run through the entire tizmak caves and then the wurns and if I want a short run just for a lesson burn/Max out AA bank for glyph burns for missions/raids I will only run half the waypoints before it quits after 1 run.




The trouble public macro/plugin are going to cause is like the old school PL sellers using monster missions automated over and over for exp/AA. There is a reason I didn't share this work of mine publicly or william12 didn't share his widely.

I urge everyone to use this responsibly, and accept the risk for bans/suspensions using it.
 
I've had my own macro flipping instances for a while, and I do it like that. The driver zones everyone else in and then themselves.

The trouble public macro/plugin are going to cause is like the old school PL sellers using monster missions automated over and over for exp/AA. There is a reason I didn't share this work of mine publicly or william12 didn't share his widely.

I urge everyone to use this responsibly, and accept the risk for bans/suspensions using it.
100% *please* mq2 - be cool :)
 
I LOVE MQ2GRIND!

However, one issue I am having is after the grind is over with, my chase mode will not work unless I click follow me.
 
I LOVE MQ2GRIND!

However, one issue I am having is after the grind is over with, my chase mode will not work unless I click follow me.

Thanks man I appreciate the kind words!

At the end of the mission, before the zone out, the plugin will instruct everyone to "pause" which looks to the INI file and executes what ever the "Pause" instruction is. So when you get to GD and then /grind end or something else; your toons are still "paused" essentially.
 
The trouble public macro/plugin are going to cause is like the old school PL sellers using monster missions automated over and over for exp/AA. There is a reason I didn't share this work of mine publicly or william12 didn't share his widely.

I urge everyone to use this responsibly, and accept the risk for bans/suspensions using it.

You know they wont be responsible with it and its why I stopped sharing them publicly after COTF simply put we all got dead hills nerfed to crap because of it.
 
I've seen and confirmed both of those and have full intention to fix it. =)

My daughter was born yesterday ... so this might take a bit, but I've got her next to me in a bassinette now for the first time so Mom can sleep. This might work for some late night coding ! :)

What I've found is that the Expedition window will populate, then about 15 seconds later, its flawless. I don't like delaying more than needed. So this is an option with a buffer. The other idea I had was setting up Dannet query to the group members, find out where they are, then zone them in first. When driver is the last, then zone in. This should help the smooth ride through the Grinds.

${DynamicZone.LeaderFlagged} and a 10s delay after that is true works perfect unless the server is lagging. You used to always be able to just delay 15s from getting the task and the instance would be up but thats rarely the case anymore.
 
Been testing plugin out, still having issues with it targeting pet on tank and just hanging there.

Message me on Discord (hytiek#2341) I'll send you an update which has the pet fix in it. Redbot will include the fix in the next build I'm certain.
 
${DynamicZone.LeaderFlagged} and a 10s delay after that is true works perfect unless the server is lagging. You used to always be able to just delay 15s from getting the task and the instance would be up but thats rarely the case anymore.

Hey William, definitely one of a few ways to resolve this.
 
Release MQ2Grind

Users who are viewing this thread

Back
Top
Cart