Other - Problems getting Meshed Travel to work (//travelto)

[allandallis235]

Hello fellow Emus!

I'm new to Emu (Laz) and I'm having some challenges getting /travelto xxx to function correctly. I have mq2nav and mq2easyfind loaded. I get the following error (zone guide does open up).




My group Follow Me and Come to Me work great. However its hit or miss if I'll be able to nav to one of the selections in the find window:




Any advice on what I may try? I'm using the EMU build from April 28, 2021. I recall reading that was the one to use because some other things were not working correctly in a later build. If this is one of those things that isn't working correctly until the Emu MQ soon(tm) is release, I'm cool with that too.

Cheers

 

[Sic]

The path is likely a mesh issue, turn of show navigation mesh in your nav options and look for a break.

The other one is a larger issue that you won't be able to fix, and there is no valid zone path (so this will likely be a wait for MQ as you mentioned)

 

[L8erGator]

Easy find has some wonky behavior on emu and I suspect some of it is actually server side. Some functions work fine on some servers and completely borked on others. Doesn't help some of them use custom zone changes like Laz (old Baz for example). Think it's just part of the emu experience. The E3 version of MQ2 that most other folks use on Laz has Nav but no Easyfind. So I dunno if Maudigan just said whatever, due to lack of standardization, or if the server setups have something conflicting with that plugin.

Edit - I also, admittedly, do not understand the inner workings of MQ2Nav/EF, and this is just a theory based on playing different emus and noticing different behaviors on each.

 

[ChatWithThisName]

Easy find has some wonky behavior on emu and I suspect some of it is actually server side. Some functions work fine on some servers and completely borked on others. Doesn't help some of them use custom zone changes like Laz (old Baz for example). Think it's just part of the emu experience. The E3 version of MQ2 that most other folks use on Laz has Nav but no Easyfind. So I dunno if Maudigan just said whatever, due to lack of standardization, or if the server setups have something conflicting with that plugin.

Edit - I also, admittedly, do not understand the inner workings of MQ2Nav/EF, and this is just a theory based on playing different emus and noticing different behaviors on each.

Specifically the output that says it was unable to find a path from plane of knowledge to nexus likely means there is an issue with nav getting to a point on the mesh so that it can click on the stone to go to the nexus.
Again the output shows the inability to find a path to the banker, means it's unable to find a path on the existing mesh that leads to the banker in question.

While I don't disagree that standarization makes it more complicated. Nav uses what it believes is the location of the zoneline by default. Without either specifying a location to travel as an xyz location, and then going there, it's unable to find said path. It's possible as well that nexus isn't in the find window (Easy Find needs the location to show up in the find window, so without it being listed, it's unable to find it in the first place).

Hopefully once MQ is upgraded to support EMU these could be issues of the past with all the customization options available. But until then that not being in the find window is just going to break things for EasyFind.

With all that said, Sic's advice to check your mesh to see if there are breaks in it between the player and the destination will be the issue for the banker 100%, and the zoneline is up in the air on what the actual issue is.

 

[L8erGator]

Specifically the output that says it was unable to find a path from plane of knowledge to nexus likely means there is an issue with nav getting to a point on the mesh so that it can click on the stone to go to the nexus.
Again the output shows the inability to find a path to the banker, means it's unable to find a path on the existing mesh that leads to the banker in question.

While I don't disagree that standarization makes it more complicated. Nav uses what it believes is the location of the zoneline by default. Without either specifying a location to travel as an xyz location, and then going there, it's unable to find said path. It's possible as well that nexus isn't in the find window (Easy Find needs the location to show up in the find window, so without it being listed, it's unable to find it in the first place).

Hopefully once MQ is upgraded to support EMU these could be issues of the past with all the customization options available. But until then that not being in the find window is just going to break things for EasyFind.

With all that said, Sic's advice to check your mesh to see if there are breaks in it between the player and the destination will be the issue for the banker 100%, and the zoneline is up in the air on what the actual issue is.

Thanks, Chat! Appreciate the insights.

The zones at least don't show up on the find window. So that's good to know on that one.

 

[allandallis235]

Thanks for the quick replies folks! Exactly what I needed to know
While it may not be what I wanted to hear, I sort of figured that might be the case.