Release Old Man McKenzie - Group Macro Beta 1.15

[TempusX]

Old Man McKenzie Group Macro, by TempusX and Levox

Be gentle, this is my first macro I've written that is actually useful and (for me) relatively involved. This is a public "Beta" in that it will complete all tasks without fail, but there are some known issues we're aware of and looking at fixes for. Those issues DO NOT result in failures of the tasks. We'll be streamlining the code also as we go. Further, there will be a hands-on raid macro coming shortly after we optimize it.

Installation:
the 'omm_grp.mac' file in your Macros folder
the 'gukbottom.navmesh' file goes into your MQ2Nav folder - you'll need to overwrite the RG launcher version of the guk mesh for now.

*NOTE* - Back up your current guk mesh if you want. Ours is not in the RG repository yet, but Levox fixed a LOT of pathing problems (including in the water tunnels) to make this work smoothly.

All testing was completed with a 6 man group. The minimum required is 3 (Default classes will be SHM MAG ENC) and groups of 3 are currently untested (ie you might die in some places).

Expectations:
This macro will expect you to have MQ2Dannet, MQ2Moveutils, and MQ2Nav loaded (plus the included gukbottom navmesh).
It expects you to provide one parameter to determine your chosen instance. Options are: naggy, lguk, dguk to correspond to
the solb, lower guk, and cursed guk instances respectively.
You are expected to be in POK to run this, and all characters must run the macro.
You will need to open and assign loot from the chest at the end. The rest you should "monitor" and be present for.

Known Issues:
There currently is a known issue with the mage shroud not "updating" itself at the designated checkpoints. This causes the mage to very late, run back through the instance to get the locational "updates". We're working on a solution. It will not fail your task, but it's annoying.

There is no "run back" feature if you die. However in testing of some 50-70+ runs, there have been no deaths or anything close to a death.

Also there is no "restart" feature for the macro if you need to restart mid mission (yet!) because you crashed, decided to end, etc.


Notes: I'd like to thank CWTN, MaxD, Kaen, and Hytiek (and if I missed someone, im sorry!) for helping me wiggle through a few items I ddnt understand how to code, and suffering my very incessant line of questions while I was developing this. You guys are awesome!

If you have any issues, problems or otherwise, please post back what you were doing when you had the issue, the error message, etc so we can fix things. thanks!

 

[apop]

Interesting! Shall give this a go, Thanks

 

[Hylander]

Tempus,

massive props. worked flawlessly for my group...

 

[hellfyre]

I will be doing my best to break this over the next few days hehe. Thank you for this.

 

[levox]

I will be doing my best to break this over the next few days hehe. Thank you for this.

Good luck. We pretty much Tempus-proofed it and if he can't break it I'm not sure if anyone can Let us know what you find though.

As a side note, it works best to start all at once with a /dggae /mac omm_group naggy/lguk/dguk

 

[Anteroz1994]

Good luck. We pretty much Tempus-proofed it and if he can't break it I'm not sure if anyone can Let us know what you find though.

As a side note, it works best to start all at once with a /dggae /mac omm_group naggy/lguk/dguk

im having issues getting my 6 to manually get the task and enter, i seem to have jsut my main guy entering and ill manually enter task only 3-4 of them are really doing anything, is this normal?

 

[TempusX]

im having issues getting my 6 to manually get the task and enter, i seem to have jsut my main guy entering and ill manually enter task only 3-4 of them are really doing anything, is this normal?

Are you running the macro on every character? Like @levox said, every character MUST run the macro. so you should be using /dgae /mac omm_grp naggy for example with all toons in POK.

 

[Anteroz1994]

Are you running the macro on every character? Like @levox said, every character MUST run the macro. so you should be using /dgae /mac omm_grp naggy for example with all toons in POK.

yes tried that, still got 1 toon not running so far (shaman)

 

[levox]

yes tried that, still got 1 toon not running so far (shaman)

Are there any echo's in the MQ2 window for the people that aren't zoning in? Are you starting them individually or all at once like the /dgae example above? Do you already have the group task? One issue is IF you have a group task, it checks at startup for a shared task and if you have one it ends the mac. That would be an issue if you tried to start them individually and the main char had already picked up the OMM mission.

Kick everyone from the task, then try again with /dggae /mac omm_grp naggy

This is likely where you are held up

    /if (${Select[${Task[1].Type},shared]}) {
        /echo You have a shared task already buddy. Quit that and try again.
        /endmac
    }

 

[Sic]

Sic submitted a new resource:

Old Man Mckenzie - Group Macro Beta - Old Man McKenzie Group Macro, by TempusX and Levox

Old Man McKenzie Group Macro, by TempusX and Levox

Be gentle, this is my first macro I've written that is actually useful and (for me) relatively involved. This is a public "Beta" in that it will complete all tasks without fail, but there are some known issues we're aware of and looking at fixes for. Those issues DO NOT result in failures of the tasks. We'll be streamlining the code also as we go. Further, there will be a hands-on raid macro coming shortly after we optimize it...

Read more about this resource...

 

[Yabbadabba]

While doing naggy run
Shaman didn't sit to med causing mana and macro timing issues. Had to manually sit the shaman to ensure macro completed sucessfully.
Before I noticed this the macro got me to the bottom of the lava. I sat the shaman down and when he had regened the macro continued but by then buffs had run out (no DMF) and we all fell in the lava.
Back to PoK and re ran macro making sure the shaman sat to regen and all worked fine then

 

[TempusX]

That's new. They should sit and med as they plow / each checkpoint until they meet a minimum threshold (usually it's 50-70m). Stopping to med to 100 after every fight/event is a waste of time. The only reason they wouldn't is if they were locked up in a combat routine, which can happen if they are paused or otherwise. Did the macro end at all? Also there is an explicit call for bufing at the lava walk in solb before going across. I'm even surprised the others kept going with one character being under threshold. Was this a problem for the shaman from the beginning each time?

 

[levox]

Were you running a full group or less than a full group @Yabbadabba? If less, we haven't tested that at all so thanks for the feedback. If you were doing it with 6 there is something else going on. I generally have the macro completed in 30 minutes for SolB with 6 and DMF lasts 60-70 minutes so there would clearly be some issue at hand if it is wearing off.

 

[Yabbadabba]

It was a full group and I thought the macro was taking a long time to run. every checkpoint was an age until they carried on, so much so that by the time they got to the lava they where running back to kill respawns.
Like i said when i ran it a second time i made sure the i manually sat the shaman and it went through fine.
When timer for the quest expires i will run it again with the same group and let you know

 

[levox]

Interesting. We'll take a look and let us know if the problem repeats itself. Sounds like something happened with a buff loop and maybe the shaman never fully exited. When it finally did (and you were at lava) he started running through the waypoints starting with the ones near zone in. One project we have for ourselves is to read task completion steps and skip the relevant waypoints if those steps are completed (nox spider sometimes spawns at zone in in sol b for example). TBD on an ETA

 

[TempusX]

If they are running back to a previously cleared point, that's them not getting the task validation update for those points so they go back for them. That's a known issue. Generally its been the mage that does that and inconsistently.

The next major update will redo some of the task validation to eliminate the backwards running.

They are setup to move as a rough group so if someone isn't meeting the mana requirement they won't move on without them. That's the first time it's caused that kind of delay. If you paused anybody at any point, that's probably going to screw up their routines also. They aren't meant to individually pause.

Again if they are running back - how many is "they"? - is because they were forced out of their routine by something. Generally its buff, med. Combat if a roamer comes through, med to full. Plow/med to an objective. Clear it. Get the UD, med. Rinse repeat.

We'll check on it though and see if we can reproduce.

 

[Yabbadabba]

Lguk version ran no probs with same group
4 out of the 6 were doing the running back to pull mobs, the MA (necro) and the shaman remained at the lava.
Guess it will be tomorrow for the naggy rerun 17 hour task timer boo

 

[TempusX]

Lguk version ran no probs with same group
4 out of the 6 were doing the running back to pull mobs, the MA (necro) and the shaman remained at the lava.
Guess it will be tomorrow for the naggy rerun 17 hour task timer boo

Your necro should have never been the MA. the MA is hardcoded for wizard, or in event of no wizard, the mage.

 

[timmy]

haven't tried this macro but excited to see the raid macro. who would have thought vox would still be my nemesis in 2020? =p

 

[AnotherJohn]

Ok, not sure why but only the first toon will zone in but none of the others will. The other 5 toons have the macro end with the message "[MQ2] DEBUG: We're setting your Xtarget to default" followed by "The current macro has ended." It did this for both of the Guk missions and the Naggy mission. I thought it was because there were a bunch of toons standing around OMM but I moved them to right on top of OMM for a couple of attempts but I still got the same results. I was able to zone them in manually but I see no way to restart the macro once it ends. I get the message "You have a shared task already buddy. Quit that and try again." Any ideas?

On a different note I was wondering if TempusX had a work around for the enchanter trying to cast the spell version of Dazzle instead of the AA version if I wanted to run the missions manually using a KA ini. Thanks for your work and I hope to figure out whats wrong. I will keep plugging away at it.

 

[levox]

Do you have any xtargets pre assigned? If so, try to clear all of them and set to auto-hater. There isn't a way to start the macro in the instance currently. That will come with the next update.

As for dazzle aa and KA there is not that we were able to find though Tempus can chime in if he ever found it. That is one of the reasons we started down this road to build a custom mac.

 

[AnotherJohn]

Ok, will check and see if any of the xtargets are assigned before the next run (I may have done that for KA healing). The other thing I should have mentioned is I am on a TLP server and we only get 5 slots of Xtarget until we zone in to the instance. Mention just in case that would make a difference. In fact I came back to edit with that info but you responded so quickly, thanks for that.

Am out of the instance and checked all my toons Xtargets, they are all set to Auto-hater so that does not seem to be the problem. I will be off line for a bit but if there is something else you want me to check or some debug you want me to run let me know and I will do it when I get back.

 

[levox]

Tempus and I are both on probably the same TLP server so that is where it was built and tested. I have an idea of what is happening if it relates to that and will do some more testing this evening. Try again after resetting xtarget slots then let us know if that helped.

 

[Dolphin]

been messing around with this. very cool.
I have a problem though that the wizard and enchanter just zone in and dont go anywhere. if i move the wizard manually the rest will follow him
what should i check to fix it?
The rest of the group goes to the spawn noble etc, and then run back to where the wizard is.

 

[levox]

Do the ench and wiz have a macro running or did it end for some reason? The startup routine takes quite a bit of time. Generally 5ish mins.

 

[TempusX]

Ok, will check and see if any of the xtargets are assigned before the next run (I may have done that for KA healing). The other thing I should have mentioned is I am on a TLP server and we only get 5 slots of Xtarget until we zone in to the instance. Mention just in case that would make a difference. In fact I came back to edit with that info but you responded so quickly, thanks for that.

Am out of the instance and checked all my toons Xtargets, they are all set to Auto-hater so that does not seem to be the problem. I will be off line for a bit but if there is something else you want me to check or some debug you want me to run let me know and I will do it when I get back.

RE: AE MEz/Dazzle - When I was fiddling with mez routines for this in particular, I scrapped the need for single target mez because, for the most part a full group of casters can easily handle 3-5 in camp with no fuss. a full xtar, an ae mez is going to be more beneficial anyway than cycling single mez. by the time im done cycling single mez, they're gonna be all dead anyway. so I just scrapped it. I can't speak for how KISS would handle casting - except that I know it really doesn't. I've been using /alt act ${Me.AltAbility[AA SPell Name Here].ID} within the macro to fire spells. because they have some wonkiness with respect to thewir actual spell name/id as they share info with real spells that give, essentially false positives.

RE: Xtarget, I'm on TLP and this was developed on said TLP with ~300-400ms latency and havent had many hitches. the routine operates in that everybody starts the macro at once. To be honest I never thought folks would try it one toon at a time (but that wont end well). The routine is to run to mckenzie, snag the task, assign shroud roles via dannet, the classes click in, if they fail, they recycle that every 10 seconds. then, they should have a lengthy pause (30s) to zone, buff routine and med to 100%. the zone in / startup is lengthy but i found shortening the 30sec delay caused toons to wander off and really get out of sync. once they are in the zone, you have all 13 xtar slots and the macro sets them all to auto hater so we dont run into weird issues. It shouldnt be jumping that far ahead.

My question for you are two fold.
1) Do you regularly use dannet, or was it loaded for this macro? Some folks have experienced misconfigurations witht he plugin setup that could be an issue
2) did your other characters actually pick a shroud, or were they sitting on Warrior still? IF they did not pick a shroud, then they are not receiving the commands from the group leader via dannet
3) Bonus round: how did you start the macro? One by one, via /dgae, or?

 

[TempusX]

been messing around with this. very cool.
I have a problem though that the wizard and enchanter just zone in and dont go anywhere. if i move the wizard manually the rest will follow him
what should i check to fix it?
The rest of the group goes to the spawn noble etc, and then run back to where the wizard is.

The wizard is the MA, if he moves/gets aggro, everybody leashes to him. By design. So that's expected.

When you say they don't move/etc. Is your party done buffing and 100 mana on every toon? If not, you're rushing the buff routine and throwing things out of whack.

it's possible a character is getting stuck in a routine early. that seems to suddenly be infinitely more common based on what i'm hearing on these posts so far today. Of the several dozen runs levox and I did, this was a very uncommon issue. We'll look into it but i really need to know exactly every step folks are taking/doing to recreate the issue. Also any other amplifying data that might have an affect: ie. running cwtn plugins, not running dannet (this should cancel the macro tbh), moving toons before they are ready, high latency (this was designed under 300-400ms), etc.

 

[Dolphin]

Do the ench and wiz have a macro running or did it end for some reason? The startup routine takes quite a bit of time. Generally 5ish mins.

They enchanter buffed everyone and would shoot and mez. wizard would shoot just fine but i would have to run him around the zone manually.
going to do some more runs and see.

If it matters im starting everything with /dgaex

 

[levox]

They enchanter buffed everyone and would shoot and mez. wizard would shoot just fine but i would have to run him around the zone manually.
going to do some more runs and see.

If it matters im starting everything with /dgaex

So it seems like the macro is running. How long did you wait at startup? Did the necro buff DMF? Did the shaman buff Talisman? Did the druid buff Skin? Did the mage make a pet? Once the buff routine is finished (generally the shm/druid are about 30% mana) everyone meds to full before they move. The macro is designed to be fully automated and messes up with human interaction generally.

In PoK I just type /dgae /mac omm_grp naggy and come back 30-35 minutes later to a chest of loot.

 

[Dolphin]

doing another run this time in Live guk.
/dggae /mac omm_grp lguk
first time didnt select lguk, tried for naggy, said had lockout timer.

/dggae /mac omm_grp lguk
got task perfectly, all but necro zoned in and started buffing making pets.
the roamer showed up about halfway through the buffs, everyone but necro switched over and killed it.
maybe a minute later all but wizard and necrostarted running like they were going towards the patriarch, got agro on the first mobs and ran back to wizard at the zone in where all but necro attacked and killed.

so far 8 minutes everyone just hanging out at the zone.
just been waiting to see what happens.

no ctwn plugins running on these guys, dannet is on and working (everyone is selecting a character). new mesh is loaded.

 

[levox]

Sent you a PM. Try that and let me know.

 

[AnotherJohn]

My question for you are two fold.
1) Do you regularly use dannet, or was it loaded for this macro? Some folks have experienced misconfigurations witht he plugin setup that could be an issue
2) did your other characters actually pick a shroud, or were they sitting on Warrior still? IF they did not pick a shroud, then they are not receiving the commands from the group leader via dannet
3) Bonus round: how did you start the macro? One by one, via /dgae, or?

1) I exclusively use Dannet, I switched quite a while back when ihc385 was reworking his macro to use Dannet.
2) They all picked their shroud but it seems like after they picked they did not retarget OMM and zone in. This is where the macro gives the "[MQ2] DEBUG: We're setting your Xtarget to default" message and macro ends.
3) I used the /dgae command to start all the toons at once (/dggae /mac omm_grp naggy)

Also if you didnt see my previous response. I did check all the Xtarget slots on all the toons and they are all set to Auto-hater. I am going to log on and play with it some more and see what happens. As I have said before I am Sooo much better at breaking other peoples macros than writing my own. I cannot tell you how many times I have heard "Well I have never seen it do that before...." so if it can go wrong it will go wrong for me. That said if you want me to send you specific info let me know. Just understand I am not very tech savvy so please use small words and explain exactly what you want me to do and I would be happy to provide you with anything you need. Thanks for the response

Followup: tried with a second set of characters just to see if anything changed. It didnt, got the same exact results. Also, tried spamming /tar old man while macro was running to see if that would force the toons into zone. Still left 5 toons outside of zone and macro ended.

 

[levox]

I sent you a PM. I can provide an earlier version that has a lot of debug spam. May help us figure out where the macro is ending exactly.

 

[Dolphin]

Sent you a PM. Try that and let me know.

that worked.
druid didnt buff or sit to med though.

Also running the original with other group when i did /kickp task and clicked yes, all of a sudden i got a lot of movement IE running to patriarch

 

[Anteroz1994]

Are there any echo's in the MQ2 window for the people that aren't zoning in? Are you starting them individually or all at once like the /dgae example above? Do you already have the group task? One issue is IF you have a group task, it checks at startup for a shared task and if you have one it ends the mac. That would be an issue if you tried to start them individually and the main char had already picked up the OMM mission.

Kick everyone from the task, then try again with /dggae /mac omm_grp naggy

This is likely where you are held up

    /if (${Select[${Task[1].Type},shared]}) {
        /echo You have a shared task already buddy. Quit that and try again.
        /endmac
    }

yeah i have them all running the macro at the same time, i done the startup like you suggested and also tried /bcga still didnt zone anyone in but toon that grabbed the task and then when i manually zoned them en via /dggae /say story or /bcga //say story. i will keep playing with it and see if i can get it working thank you for the help

 

[levox]

For those having issues with chars zoning in early (or not at all cause they try to soon then fail and the mac ends) try the attached. I found something where it could skip the check and tried to zone in early, like right when they got to Mckenzie. A few other things are slowed down as well to adjust for some latency issues.

It will give you an /echo countdown on each char in seconds. No one should zone in before 21540 seconds are remaining. This is slightly different than it was previously. Additionally, there is an echo that tell you they are medding to full once they are done with buffs on each char. Let me know if this helps/hurts any.

 

[AnotherJohn]

Gave this a try on both Naggy and dguk. Both gave me the same results. Toon one zones in and is waiting for the others to join. Toons 2 through 6 all pick their shrouds and then the macro ends without them zoning in "[MQ2] DEBUG: We're setting your Xtarget to default" "[MQ2] Buffing done, waiting for FM" "The current macro has ended."

However, I think this is new (or I totally missed it before) I get the message "Slot_number must be between 1 and 5 (your current maximum number of slots" repeated 8 times in a chat window for toons 2 through 6. I am guessing it is referring to Xtarget slots. I have double checked and all Xtarget slots for all toons is set to Auto-hater. Hope this info helps.

 

[levox]

Thank you to all of the beta testers and the feedback you provided today. I think we solved a few issues and identified a few more. Appreciate the help while we work through them and hopefully get it to where it works for everyone. It's an odd thing cause I use the same mac here every day and can go days without an issue. The same for TempusX. We'll get it sorted though.

 

[TempusX]

Gave this a try on both Naggy and dguk. Both gave me the same results. Toon one zones in and is waiting for the others to join. Toons 2 through 6 all pick their shrouds and then the macro ends without them zoning in "[MQ2] DEBUG: We're setting your Xtarget to default" "[MQ2] Buffing done, waiting for FM" "The current macro has ended."

However, I think this is new (or I totally missed it before) I get the message "Slot_number must be between 1 and 5 (your current maximum number of slots" repeated 8 times in a chat window for toons 2 through 6. I am guessing it is referring to Xtarget slots. I have double checked and all Xtarget slots for all toons is set to Auto-hater. Hope this info helps.

I have limited help right now, sitting in an air terminal on travel but...

The xtar is automatically set by the macro. It sets them all to auto hater. All 13. On.tlp we have 5 for now so it's trying to do it out of sequence and giving that error. But there is a check it's failing and still doing the thing which makes all of zero sense.

What's more frustrating is I ran all 3 instances tonight on ~370ms and they all zoned properly and buffed and started plowing. Which makes it difficult to.reproduce and pinpoint. Looks like levox is working hard at it while I'm on travel

 

[Sic]

Sic updated Old Man Mckenzie - Group Macro Beta with a new update entry:

V1.12

* V1.12
-Slowed things down a bit to deal with latency issues (possibly)
-Fixed a /while loop so while in PoK it will try to /say story every 10 seconds
to zone in instead of saying it twice and calling it quits
-Startup routine including buffs takes approx 6 mins. Please be patient
-Added /echo timer that counts down to instance start. It will not zone in when
seconds are above 25540. This is excessive and a full minute but may help us with debugs
-Added /echo after buffs were done to be...

Read the rest of this update entry...