• 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

Another Wending Ways portal

joojoobee

A Member to Remember
Creator
Joined
May 15, 2016
RedCents
4,327¢
V1.2 -- Some fixes to move from Fire and to Water. When it lands at minibosses, auto moves a little closer into the alcove. Also now faster at startup, portal clicking.
V1.1 -- Removed the Quest-giver check for now.


A macro for moving around in the Wending Ways portal pad TBL trial by JJB 2019 (--> I learned a lot from eqmule's Wending Ways script and adapted it from there).
  • The script will determine where you are and navigate from there. You only need to say where you want to go. Assumes you are at one of the Mini-boss pads have MQ2Nav access to the north or south start points.
  • Requires MQ2nav, and will dismount you because mounts or bard speed overshoot the pads.
  • Commands:
    • fire, earth, water, and air will take your toon to the respective rooms from anywhere.
    • 'north' & 'south' are the north & south start positions, respectively.
    • 'chest' will run to the Tricky Chest reward and open it after you have won the Trial.
  • The script:
    • Makes sure group is invis when starting this. Will auto-end if you are not invisible.
    • Will exit if the portal pad induces injuries from a fall, and results in HPs < 60. Will also /endmacro if you are dead.
How to run the code:
Code:
/mac ww ***

where ***  = water | earth | air | fire | south | north | chest |

e.q.
/mac ww air
will run to air...
  • I STRONGLY RECOMMEND you run only one toon at a time. And I STRONGLY RECOMMEND that you run it as the foreground window.
    • For some reason when multiple toons running, or in the background, the jumping pads seem wonky and there's a lot of falling/death.
    • Foreground window seems largely immune to the problem.
    • It's not the script's fault... it's something with the portals and MQ2-- or maybe the speed of the CPU. I am working on solution ideas...
      • Solutions tried: EQWire & MQ2FPS to lower FPS, wireframe, low render rate, turbo 20, turbo 120. None of these worked. Any ideas on this anyone?
JJB
 

Attachments

Last edited:
Yay! May not test it right away, on a short break from active EQ. I kind of overdosed on TBL. But I will when I start up again.
 
I also had the same experience with EQMule's macro (trying to run it /via bcga on all toons didn't work the majority of the time, but one at a time with a foreground window does.
 
It's interesting because it implies that there's feedback between the background process rate and some form of computational air "friction" when a character is tossed. Like the rate at which one moves (the physics) is dependent on CPU cycles. There might be some setting somewhere that can affect it to be better but I could not find it.
 
Understood per the other thread. With EQWire and FPS unlimited, it mostly works for all 4 (per your suggestion). Otherwise, just doing 1 at a time with a script is still better than manual.

Thx!
JJB
 
V1.2 -- Some fixes to move from Fire and to Water. When it lands at minibosses, auto moves a little closer into the alcove. Also now faster at startup, portal clicking.
 
MQ2Nav... PathExists appears to be broken last update... and since this macro relies on that... this macro not working.
 
are you sure the message about the 1.2 version shifting the path over during on of the moves isnt working for me in the build i downloaded ... i see where your mention it in the update notes
 
Thanks for the great work!

Does this require a mesh file for MQ2NAV? will start at any pad or just Mini bosses nearby pads?
 
Pathing keeps failing and macro pauses. How do we resume?
Also Is there a way to just have the macro select box up the correct pads to click instead of actually moving?
 
If the path fails with an MQ2Nav error, that means your mesh has issues. Attached is my navmesh with some of the fixes. Let me know if it works.

I'll look at the script this weekend... but you can do it yourself. Just search the script for /nav door & /nav locxyz. Comment those out with |

That "should" highlight the pads only and you can go to them.

JJB
 

Attachments

Last edited:
I just did this using @kaen01 's navmesh for trialofsmoke. It worked great.
 
Please modify this so that it doesn't /open the chest at the end. I just hosed myself on an entire chest of loot because I was navigating to the chest and had autoloot enabled. My raid-geared tank just sucked up a couple of caster items and some visibles he'll never use.

Actually, I guess I could just modify mine. Nevermind.
 
Copied JooJoos Nav Mesh, and did what everyone mentioned.
1. Group invis
2. Only do 1 screen at a time, it needs to be the Foreground all the way until the end. Used CPU FPS and only had 30 FPS and worked great.
a. Move each toon separately
3. Don't forgot to turn your favorite /mac program back on before you fight.
4. After each named, I turned off all macs going.
5. Group Invis again and go look with one toon which is next Boss.

..if you are overshooting, unclik all your speed boosts. Tala'Tak, SoW, Selos etc.

use the /mac ww .....

rinse and repeat.

Was able to get the achievement for not falling in finally !

Thank you for this !
 
So I've been using this macro, thanks JJ :).

It works pretty much perfectly except it sometimes says that both quest givers are present midway through the trial. I use it the complete opposite way to how i'm supposed to I admit, but /bcaa //mac ww water or whichever works perfectly. They all run, no-one falls, no-one dies. Admittedly I have all my background fps set to 60, and do not use mq2fps or any energy conserving plugins. But it means that after I /bcaa //mac ww whichever, I have to alt tab to each window and start the random ones that are sure that the trial hasn't started yet because both quest givers are present. Sometimes more than once.

If I edit the macro (I don't know code, and have no confidence at all with this stuff) and delete this bit:


/if (${NorthQuestGiver} && ${SouthQuestGiver}) {
/echo Both quest givers are present, you need to start the Trial then you can use this script
/endmacro
}

Is it likely to crash everything? I realise I could just try it myself, but I'm stuck away from eq for a couple of days and I'm suffering from withdrawal.

Alternatively, is | the comment character for macros, and can I just enter that at the start of each line?

Thanks in advance :)
 
It's been a while since I've done this event, but as I recall there are two quest givers. Why it says there are two quest givers I can't imagine unless they changed the event, or you have access to the arena without actually starting the trial.

You can delete that code though if you like. It's there to make sure people actually start the trial so the barrier comes down. If the barrier is already down, you don't need that (but I would have thought the quest givers were not then present).
 
I've had similar experiences... I simply moved my toon a little and tried again... it's rare that the macro would fail to initiate and start working after two tries.
 
Still doing the quest giver check but it would succeed on the second try typically. Had 3 falls but no "bounces", this finally got me my "appointments required" achievement.
 
For me the quest giver check always fails if my target is not clear when i start the macro. I do them individually and in the foreground as I find mq2nav too unpredictable in the background.
 
I know this is a nearly abandoned mac, but I discovered today the path from earth to air is right over another portal. I didn't see quickly enough where this other portal landed me, but I know nav tried to go directly to the expected portal which dropped me in the center (thus eliminating a potential achievement).
 
Was running a set of characters through this and decided to make a Lua version of it. The biggest difference is you can leave the Lua running and just use /ww <destination>. Automatically ends when leaving the zone. Still best practice to activate a path on one character at a time.

Save to your Lua folder and extract to there. Two files go into \lib
 

Attachments

Another Wending Ways portal

Users who are viewing this thread

Back
Top
Cart