Question - How do you use the "next" spawn search?

[grundy923]

How exactly am I meant to use "next" in a spawn search?

I'm running this command:

/echo ${Spawn[npc goblin]}

output is "an_ice_goblin44"
mq2nav can't figure out how to get to certain parts of permafrost, this goblin is in such a location, so I want to skip it and find the next goblin

/echo ${Spawn[npc goblin next]}

again is the same "an_ice_goblin44". If I try just

/echo ${Spawn[next]}

it gets myself. I add the npc goblin part back in, i still just keep getting an_ice_goblin44. With or without next I just keep getting the same goblin and with out the "npc goblin" search I just get myself. I can't figure out how to get it to return the next goblin.

 

[bytebite]

https://www.redguides.com/docs/projects/macroquest/reference/top-level-objects/tlo-nearestspawn/

Could you use the

${NearestSpawn[1-N, npc goblin]}

ETA: To answer you question about Next instead of guessing at what you want.

Had to go check the C++. 'next' is used to find the first nearest spawn to your target only it looks like. So if you target something and run

/echo ${Spawn[next]}

you can see its behavior.

 

[grundy923]

Had to go check the C++. 'next' is used to find the first nearest spawn to your target only it looks like. So if you target something and run

/echo ${Spawn[next]}

you can see its behavior.

Interesting... that's not at all what I was expecting based on the wiki explanation: https://www.redguides.com/docs/projects/macroquest/reference/general/spawn-search/

Next spawn matching the search criteria

That looks like it should just give me a different npc that also matches the search criteria

 

[Redbot]

I believe next and prev are for the target command. e.g.
/mqtarget goblin next
will work, but not:
/mqtarget ${Spawn[goblin next]}

 

[bytebite]

I think the confusion is that it is meant to be used with `/target next` and `/target prev` commands. Those are spawn searches but not really meant to be used in a ${Spawn[next]} way. Documentation might need an update.

^ What redbot said.

 

[brainiac]

/mqtarget uses spawn search criteria, same as NearestSpawn, Spawn, etc. It just so happens that next/prev are really just going to be more useful when used with /mqtarget

 

[grundy923]

I saw people recommending not to target mobs that you can't see, so I was hoping to be able to use "next" and store that spawn id in a variable, instead of having to target it. Is there a way to do that?

 

[brainiac]

I saw people recommending not to target mobs that you can't see, so I was hoping to be able to use "next" and store that spawn id in a variable, instead of having to target it. Is there a way to do that?

use NearestSpawn and cycle through them that way. the first parameter is an index. Some posted an example up above.

 

[Knightly]

I saw people recommending not to target mobs that you can't see, so I was hoping to be able to use "next" and store that spawn id in a variable, instead of having to target it. Is there a way to do that?

/eqtarget also follows all the normal rules