• 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

Question - Spawn search wonky when there's a mount

AmericanNero

Seasoned veteran member
Joined
Oct 13, 2020
RedCents
4,709¢
/echo ${Spawn[AmericanNero]}

If there is a mount, the first thing I get back is AmericanNero_mount00. Wouldn't the first thing to expect is the exact match?

I see this problem crop up in mq2dpsadv results, too. Note that limiting the result by [pc name] would *not* give me the result I want, I want to provide a name and it return the *exact* match first, if it's there. This is for a general use target function. If spawn returns an array, I don't know how to access it.

I love reinventing the wheel. I learn so much.

AN
 
It will actually alternate between you or your mount inconsistently. You'll need to define pc or npc in the spawn search.

You need to define exactly what you're looking for. You could also loop until you get a match that isn't a mount.
 
That's wacky. Why not fix it. I'm not looking for a pc or mount per se. It just returns whatever it finds first without considering the actual value sought.
 
Depending on how your mount/you are animating, you or the mount will be the first spawn. You'll need to consider the options and limitations.
 
Depending on how your mount/you are animating, you or the mount will be the first spawn. You'll need to consider the options and limitations.
It returns based on the order of the spawn id?
 
I believe that particular search returns based on what is "closest" and as Lemons says, it can be either/or. But you don't really need to spawn search for yourself, you always know who you are. The issue you're seeing is going to crop up with others, and Lemons has the right answer there as well, narrow your search.
 
a search for a spawn ${Spawn[Soandso]}, where SoAndSo is another player, could very well return their pet if the pet is closer to you than the player is.
a search for a spawn ${Spawn[pc Soandso]} would only return a player character named Soandso. Since player names are unique, you can expect the result to reliably be the player you're trying to search for without fear of getting a mount or a pet.

It's not really wonky, it's that you're not being specific enough with the search, and depending on the animation as mentioned by Lemons, it's possible that one time you check the mount is found to be closer, and the next time you check the player is considered closer to you.

It just returns whatever it finds first without considering the actual value sought.

The macro or spawn search has no way to know what value you seek, unless you're specific.

When programming, the code is only as smart or specific as you make it. If you're not specific, you can't reasonably expect specific results.
 
a search for a spawn ${Spawn[Soandso]}, where SoAndSo is another player, could very well return their pet if the pet is closer to you than the player is.
a search for a spawn ${Spawn[pc Soandso]} would only return a player character named Soandso. Since player names are unique, you can expect the result to reliably be the player you're trying to search for without fear of getting a mount or a pet.

It's not really wonky, it's that you're not being specific enough with the search, and depending on the animation as mentioned by Lemons, it's possible that one time you check the mount is found to be closer, and the next time you check the player is considered closer to you.



The macro or spawn search has no way to know what value you seek, unless you're specific.

When programming, the code is only as smart or specific as you make it. If you're not specific, you can't reasonably expect specific results.
Is there a flag to indicate exact match? You guys are beating me up missing the point, it seems.
 
Question - Spawn search wonky when there's a mount

Users who are viewing this thread

Back
Top
Cart