• 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

Problem - MQ2Nav/EasyFind connection issues

Rooster

Well-known member
Joined
Jan 2, 2014
RedCents
1,611¢
so my mesh for lesser faydark won't let me easyfind to greater fay zone, either from the Find button in there, or if i used the /travelto butcherblock for example, it says cant nav to loc 2149.68 -1193.88 -32000 or something. I have tried to remake a mesh that didn't result in this but raising/lowering the 'floor' of the zone and various pathing type area options like unpahtable/avoid/prefered etc near the zone area with no luck.

So i next tried to add to the MQ2EasyFind.ini

[The Lesser Faydark]
The Greater Faydark=2149.68 -1193.88 0


and it still fails, am i using the wrong ${Zone.Name} ? they are both which appear in the Zone guide window. I tried reloading plugins etc/meshes/reloading all of mq2/eq

Does someone happen to have settings for a mesh they used which work for lesser fay mind sharing, or point me in the direction to try solve this?

i have tried the mesh from kaen0 also
 
Should post this to the resource for MQ2EasyFind instead of creating another thread. But to answer your question. When the connection is found in the find window, but it's not able to navigate to the location, you need to generate a location to replace the one the server has stored. Can do this by approaching the zone line and typing /loc, then move closer to the zone line and type /loc again, this gives you an idea if the X Y and Z are going up or down. Then you can modify the MQ2EasyFind.ini found in the release folder with a location to use instead of the one the game has stored. making minor adjustments until your character zones using the provided location.

A list of current modifications can be found in the MQ2EasyFind overview at the bottom. Those will serve as both a guide on how it should look, as well as a list of zonelines and their corrected locations.
 
Thanks, I was looking at these shared connections and thought the ones I looked at were just the. .Name, probably didn't help I jumped on after a 13 hour day at work with a tried brain I'm normally better at problem solving :-(
 
Problem - MQ2Nav/EasyFind connection issues

Users who are viewing this thread

Back
Top
Cart