I've seen and been asked various questions that pertain to targeting various things in the game. Here are some MQ2 commands that might come in handy. Although I have tested most of these commands using both warder pets and similarly-named pc's, there are some (mostly the corpse-type commands) that I have not.
For targeting stuff that is either not in sight, or in a pile (like in raid wipes, heh):
/tar pc Jaton - this will target Jaton, rather than Jaton's warder pet or Jaton's corpse.
/tar pet - targets nearest pet
/tar corpse - targets the nearest corpse, whether pc or mob.
/tar pc corpse - targets the nearest pc corpse.
/tar npc - targets the nearest living mob. Just like F8.
/tar an ukun deathhound - targets the nearest living or dead ukun deathhound. Sometimes, you can drop the article (the an).
/tar npc an ukun deathhound - targets the nearest living ukun deathhound.
/tar corpse an ukun deathhound's corpse - targets the nearest ukun deathhound corpse. Note that the ' is a single quote, not an apostrophe. I am not sure if thats always the case with all mobs...maybe sometimes it does have to be an apostrophe. Also, the name could have been shortened to an ukun death, or even shorter depending upon what other corpses are in the area.
These commands can, of course be placed into Socials for hotkeying, or used with MQ2 for remote control.
This one is one of my favs. Makes looting large mob corpse piles abit faster:
Tar&Loot (this is my Social Name)
--------
/keypress num_9
/loot
Note: num_9 = 9 on the Number Pad. This is the default keypress for targeting the nearest corpse.
JatPetAtk (this is one of my sk's remote pet controls)
---------
/bct Jaton //target ID ${Target.ID}
/bct Jaton //pet attack
Note: /bct means "Broadcast Target", as in sending the command to a specific toon or MQ2-defined group. The first ID means "an identification string, rather than a direct pc/npc name, is about to come". The $ stuff means "my target" as in my sk's target.
/bct maingrp //target ID ${Target.ID} - this is what I use to send all my MQ2-defined group's pets to attack my sk's target.
Note: to make an MQ2-defined group, place the appropriate entries in your MQ2Eqbc.ini file. Here are my sk and mage entries:
[Jaton]
Channels=maingrp
[Shadome]
Channels=maingrp
/bca //target ID ${Target.ID} - if typed (or Socialed) from my sk, it would tell all my connected toons to target his target.
Note: there is a similar /bc command.../bcaa. You would not use it with targeting but you might use for other things, like /say. Example: "/bca //say blah" would tell all toons EXCEPT the broadcasting toon to say blah. Using /bcaa would INCLUDE the broadcasting toon.
AllStick
--------
/bct maingrp //target ID ${Me.ID}
/bct maingrp //stick hold !front uw
Note: This is an example of the broadcasting toon telling the other toons to target him.
/tar =Jaton - adding the equal sign works like /tar pc Jaton. Did not work on a warder pet when I tried it (i.e. /tar =Jaton's pet did not work). I have not tried it on npcs or corpses.
/target ID ${Spawn[=Jaton].Pet.ID - this targets Jaton's pet regardless of pet name. Note that the equal sign would focus the command on Jaton, not on similar names like JatonA or JatonB, etc. This would also do the same thing /target ID ${Spawn[pc =Jaton].Pet.ID}.
I think we have all encountered that annoying corpse bug, where toon A will kill a mob but toon B cannot loot the corpse because toon B was not within a certain range at the time of the kill. Either the corpse is shown to be in the ground, or the graphics have one location but the server coordinates have another. Or, it just does not show up at all. In some cases, this can be solved by toon A targeting the corpse and then toon B using command /assist B. Otherwise, simply log toon B to the character screen then log back in. Neither of these tricks need MQ2.
Be aware that some of the commands here require the appropriate MQ2 plugins to be load. For example, the /stick command requires MQ2MoveUtils.dll. Also, many commands can be abbreviated, for example, /tar for /target. But also be aware that stuff for MQ2 within braces {} cannot be abbreviated and in fact are case sensitive.