Checking movement with MQ2Navigation

[Randyleo]

I found a little snippet in a macro to check for movement while using MQ2Navigation. I modified it to be able to be plugged into just about any macro with very little modification.

I came up with this because I noticed using /nav target, the macro would immediately go to the next line of code. This was causing the code I was writing to turn on attack and start spamming to move closer. This will also hold it this loop until you finish a long run. I was having a problem with beginning hunting mode before the toon reached the proper area. This seems to work well for both. Enjoy.

Snippet:

	/nav target or LocX LocY LocZ
		:waitForMove
		/delay 2s
		/if (${Navigation.MeshLoaded} && ${Navigation.Active})  {
				/goto :waitForMove
		}

 

[hoosierbilly]

A more general method would be

:moving
/if (${Me.Moving}) /goto :moving

 

[PeteSampras]

Avoid goto loops if possible because sometimes you forget about them when you modify code and it makes tracking the flow more difficult than it needs to be. I'd suggest a /while statement for code cleanup purposes.

/while ${Navigation.Active} {
/delay 2
}

 

[Randyleo]

I'll give that a try, thanks Pete.

That made it twitch and not move.

 

[playbetter]

Randyleo, I find the Advpath easier to work with. A sub that handles the "wait till I am finished moving" for me is

Sub waiting
/while (${AdvPath.State}==2)
/delay 1
/endwhile
/return

another tool for your tool box..........