Question - MQ2Nav or MQ2MoveUtils - I am confused

[Soandso2]

Been using MQ2Nav quite a bit now and I love it. Whenever my main toon tells the group to "attack" the other melee toons get the target via /assist and then /nav target dist=10, which works just fine. Every now and then, but rarely, the toons "dont understand" and just stand where they are. But this happens so seldom that I dont worry about it.
But after a while, the toons get a bit spread out and I wish they would "return to camp" so I started to look on how to code that. Just out of the blue I decided to watch the video on MQ2Nav and at the end of the video, I saw a command on the screen /moveto
This is not something I recognize from MQ2Nav (although it looks similar to /travelto, which I presume is from MQ2Nav as well). So I decided to lookup that command and found out about MQ2MoveUtils. Looking at THAT plugin I see many similarities, like moving to a target with ID whatever (also it has the "make camp" and "return to camp" features, so ... yay, no need to code nuffin!).

However... MQ2Nav... MQ2MoveUtils... and then there is MQ2EasyFind, which uses MQ2Nav somehow... it gets confusing. Would anyone feel like untangling this mess?

Should I use /moveto loc or /nav locyx for example?

 

[Szazor]

There is no best method, you just need to choose the one which suits the situation and hopefully master them all.

Its really great to be able to pick and choose. ie - If you need to run away from an emote then doing a /nav wp X is a fairly standard. But If you need to run away for a set time or if you are being chased....then ive found /circle to be tremendously useful.

Likewise you can use something like /rootme on/off to stop a toon doing their normal behaviour. (ie dont run around behind the mob and try and backstab it..just stand and melee.

I'm not sure what circumstance you do /assist and /nav target dist=10, but it sounds like you aren't using the automation to its best ability.

In the best situation - you are driving with your Main Assist and everyone else is chasing you around and their behavior is programmed by the automation.

 

[Sic]

Been using MQ2Nav quite a bit now and I love it. Whenever my main toon tells the group to "attack" the other melee toons get the target via /assist and then /nav target dist=10, which works just fine. Every now and then, but rarely, the toons "dont understand" and just stand where they are. But this happens so seldom that I dont worry about it.
But after a while, the toons get a bit spread out and I wish they would "return to camp" so I started to look on how to code that. Just out of the blue I decided to watch the video on MQ2Nav and at the end of the video, I saw a command on the screen /moveto
This is not something I recognize from MQ2Nav (although it looks similar to /travelto, which I presume is from MQ2Nav as well). So I decided to lookup that command and found out about MQ2MoveUtils. Looking at THAT plugin I see many similarities, like moving to a target with ID whatever (also it has the "make camp" and "return to camp" features, so ... yay, no need to code nuffin!).

However... MQ2Nav... MQ2MoveUtils... and then there is MQ2EasyFind, which uses MQ2Nav somehow... it gets confusing. Would anyone feel like untangling this mess?

Should I use /moveto loc or /nav locyx for example?

use mq2nav anywhere you can. use moveto for places you cant (hopefully few)

 

[Soandso2]

I'm not sure what circumstance you do /assist and /nav target dist=10, but it sounds like you aren't using the automation to its best ability.

I am running my own luas for all of my toons and I always use the same player as puller, so I set the puller to puller (!) and main assist, so the mercs know what to do. Then my real toons get their target from mq.cmd("/assist Puller'sName"). Then when they have their targets, they move into position with the /nav command.

Using other plugins there are probably much better ways of doing this, but until today I only knew about MQ2Nav so that is what have been doing and it works just fine.

 

[Soandso2]

use mq2nav anywhere you can. use moveto for places you cant (hopefully few)

So, MQ2Nav before MQ2MoveUtils because of reasons? Fair enough, reasons are good enough for me. My code works and does what I want, so I wont change.

 

[Sic]

So, MQ2Nav before MQ2MoveUtils because of reasons? Fair enough, reasons are good enough for me. My code works and does what I want, so I wont change.

mq2nav uses a navigation mesh, which can have weights added for pathing and all sorts of "smarts"
mq2moveutils isn't smart, it doesn't know anything, basically blind

 

[Soandso2]

mq2nav uses a navigation mesh, which can have weights added for pathing and all sorts of "smarts"
mq2moveutils isn't smart, it doesn't know anything, basically blind

Ah. Cool. Then I know. Thanks.

 

[aquietone]

Moveutils came first (I think?) with it's stick command and move to that allow you to move in straight lines or keep you sticking to a target. Stick is used quite a bit just in staying on a mob you're engaged with.

Then you have advpath that came along for following. You could stick to a person with moveutils to follow them but that would get caught on things and not know hot to go around them. Advpath was a bit smarter recording and replaying movements from the driver. Advpath is basically only for following.

Then there is nav which is smart, moving through a zone based on a mesh file, navigating obstacles. You issue a nav command to go from a to b. You might use it to move to a mob that isn't close to you, but generally not for a mob that is close and within a straight line from you probably.

Easyfind is built on nav and all about travelling around. You wouldn't use it in a combat routine at all. Use it to run from zone a to zone b, or to nav to a npc on your find window with Ctrl click. Travelto is also easyfind.

Groupinfo follow me button uses advpath. Groupinfo come to me button uses nav.

Most automation allows you to configure a stick command for combat, but also allows to turn off using stick. Most automation uses nav to chase your driver or pull or return to camp, except in edge cases like going off mesh.