/target

Rusty~ · Post by **Rusty~** » Sat May 15, 2004 1:23 pm

as of latest patch if i /target something thats already on target, it gives "There are no spawns matching: (0-100)"

not a real problem, just kinda annoying

ml2517 · Post by **ml2517** » Sun May 16, 2004 9:59 am

Same behavior here.

ml2517 · Post by **ml2517** » Sun May 16, 2004 11:10 am

Lax,
This used to work before and now it isn't working properly.

/target id ${Group[0].ID}

Or

/target id ${Me.ID}

The reason why I used the top one is that it is part of a loop and worked out nicely before because I didn't have to make an exception for the bot itself.

Jerle69 · Post by **Jerle69** » Sun May 16, 2004 11:17 am

Cross-cut-and-paste from the /who thread that got locked, since my post really belonged in this thread...

This is sort-of related to the spawn-search routines and the /who issue, but is also an artifact of earlier versions of MQ2:

${Me.ID} will return your spawn ID, but neither /target ${Me}, nor /target id ${Me.ID} not even /Target TypeMyNameHere will actually work. I'm aware that you can just use "/target myself" but I've had to put in some special condition checks to see if a TargetString.Equal[${Me}] then change it to "myself."

Not a big deal but when looking at the spawn-search stuff I noticed the MQ2 has issues when doing some self-targeting for some reason.
_________________
--Jerle

Thanks,

ml2517 · Post by **ml2517** » Sun May 16, 2004 11:20 am

The point is, it worked before via ID. I know how to work around it and I'm doing that. But it adds un-necessary work.

Lax · Post by **Lax** » Sun May 16, 2004 1:13 pm

/target issues mentioned are fixed for next zip

/target ${Me}
works fine
as well as..
/target shm
/target shm next
/target shm next
/target shm next
/target shm next

and so on

Rusty~ · Post by **Rusty~** » Sun May 16, 2004 1:20 pm

yay