Target custom next (Slash Command): Difference between revisions
Jump to navigation
Jump to search
BlackSpectre (talk | contribs) No edit summary |
BlackSpectre (talk | contribs) No edit summary |
||
Line 7: | Line 7: | ||
== Notes == | == Notes == | ||
You '''must''' specify the defined parameters '''before''' entering the text to be used to target the entity. Defining a parameter after a non-parameter will cause the game to look for ''{{red|an entity that matches all words after the non-parameter.}}'' | * You '''must''' specify the defined parameters '''before''' entering the text to be used to target the entity. Defining a parameter after a non-parameter will cause the game to look for ''{{red|an entity that matches all words after the non-parameter.}}'' | ||
This command is a standard tool for any type of hunting. It is particularly useful when hunting specific entities (e.g. Tsoo Sorcerers) for badges, or for checking a mob for a particularly dangerous type, such as Malta Sappers, or Void Hunters and Quantum spawns for Kheldians. | * This command is a standard tool for any type of hunting. It is particularly useful when hunting specific entities (e.g. Tsoo Sorcerers) for badges, or for checking a mob for a particularly dangerous type, such as Malta Sappers, or Void Hunters and Quantum spawns for Kheldians. | ||
The standard form of '''target_custom_next''' is to use it to create a keybind or macro of the type of creature you are looking for. For instance: | * The standard form of '''target_custom_next''' is to use it to create a keybind or macro of the type of creature you are looking for. For instance: | ||
:{{slashcommand|macro}} '''find''' "target_custom_next enemy alive quantum$$target_custom_next enemy alive void$$target_custom_next enemy alive cyst" | :: <code>{{slashcommand|macro}} '''find''' "target_custom_next enemy alive quantum$$target_custom_next enemy alive void$$target_custom_next enemy alive cyst"</code> | ||
: | :::'''Note:''' Substitute ''/macro find'' with ''/bind <key>'' to create a key bind instead | ||
Triggering this macro will examine all entities in the user's field of view for foes whose names contain the strings "quantum", "void", or "cyst". This can be combined with the standard {{slashcommand|target_enemy_next}} command in order to prioritize these items, but select the next available enemy if they don't exist in this manner: | * Triggering this macro will examine all entities in the user's field of view for foes whose names contain the strings "quantum", "void", or "cyst". This can be combined with the standard {{slashcommand|target_enemy_next}} command in order to prioritize these items, but select the next available enemy if they don't exist in this manner: | ||
:: <code>{{slashcommand|bind}} '''TAB''' "target_enemy_next$$target_custom_next enemy alive quantum$$target_custom_next enemy alive void$$target_custom_next enemy alive cyst"</code> | |||
* The {{slashcommand|target_name}} command has fewer characters, and so might be useful to use instead of {{slashcommand|target_custom_next}} in order to fit as many targeting commands in a single bind string as possible (within the 255 character limit). However, unlike {{slashcommand|target_custom_next}}, the {{slashcommand|target_name}} command outputs the following error message for every name not found: " No entity with name matching '<name>' found within targeting range." | |||
== Examples == | == Examples == | ||
Line 34: | Line 37: | ||
;target_custom_next enemy void alive | ;target_custom_next enemy void alive | ||
* The game will look for a hostile entity whose name includes ''void alive'', because "alive" is defined ''after'' the string. | * The game will look for a hostile entity whose name includes ''void alive'', because "alive" is defined ''after'' the string. | ||
{{Navbox Targeting}} | {{Navbox Targeting}} | ||
[[Category:Targeting Commands]] | [[Category:Targeting Commands]] |
Latest revision as of 00:31, 28 November 2024
Slash Command
/target_custom_next parameters
Cycles through entities matching the parameters specified. Any parameters that do not match the list below will be interpreted as entity names. Entities are anything not part of the environment. This includes heroes, villains, critters, doors, boats, citizens, and mission objectives. As with other targeting commands, the entities that will be cycled through must be in your perception radius, as well as visible to the camera (not the player).
Parameters
- enemy - Hostile enemies
- friend - Friendlies (including pets)
- defeated - 0 HP targets
- alive - Living targets
- mypet - Inlcude only your pets
- notmypet - Exclude your pets
- base - Include only passive base items
- notbase - Exlude passive base items
- teammate - Include only teammates
- notteammate - Exclude teammates
- name - Name of the entity (this parameter is actually not needed, but can be used.)
Note: Any text following the slash command other than the previous parameters will be used to match the name of the entity, as will any text following one of the parameters.
Notes
- You must specify the defined parameters before entering the text to be used to target the entity. Defining a parameter after a non-parameter will cause the game to look for an entity that matches all words after the non-parameter.
- This command is a standard tool for any type of hunting. It is particularly useful when hunting specific entities (e.g. Tsoo Sorcerers) for badges, or for checking a mob for a particularly dangerous type, such as Malta Sappers, or Void Hunters and Quantum spawns for Kheldians.
- The standard form of target_custom_next is to use it to create a keybind or macro of the type of creature you are looking for. For instance:
/macro find "target_custom_next enemy alive quantum$$target_custom_next enemy alive void$$target_custom_next enemy alive cyst"
- Note: Substitute /macro find with /bind <key> to create a key bind instead
- Triggering this macro will examine all entities in the user's field of view for foes whose names contain the strings "quantum", "void", or "cyst". This can be combined with the standard /target_enemy_next command in order to prioritize these items, but select the next available enemy if they don't exist in this manner:
/bind TAB "target_enemy_next$$target_custom_next enemy alive quantum$$target_custom_next enemy alive void$$target_custom_next enemy alive cyst"
- The /target_name command has fewer characters, and so might be useful to use instead of /target_custom_next in order to fit as many targeting commands in a single bind string as possible (within the 255 character limit). However, unlike /target_custom_next, the /target_name command outputs the following error message for every name not found: " No entity with name matching '<name>' found within targeting range."
Examples
Valid Examples
- target_custom_next friend notteammate notmypet
- Allows easy targeting of allies that are not on your team, including ally pets.
- target_custom_next notteammate notmypet
- Will target most anything not your pet or on your team, including doors, boats, cars, villains, heroes not on your team, other player's pets, bombs, etc.
- target_custom_next enemy alive void
- Targets any Void Hunter that is still alive.
Invalid Examples
- target_custom_next enemy void alive
- The game will look for a hostile entity whose name includes void alive, because "alive" is defined after the string.