Pugging has brought my attention to the fact that a lot of players really have no idea what the real raid target icon order is, as listed in-game. When raid icons were released, a lot of party leaders defaulted to "skull" as the primary kill target as it symbolizes death, etc. Skull is the last mark in the list. Going BACKWARDS up the list from there is X, which became the common PuG 2nd-target. Strangely, many puggers have no concept that skull and X aren't actually the first two icons in the list, or that other marking systems are out there, and why.
The IconsThis skull -> x assignment is backwards from the actual listing of icons. The icons are listed as follows for left-to-right reading countries:
When listed top-to-bottom, they are read in the same pattern: Star, Circle, Diamond, Triangle, Moon, Square, X, Skull. They are also labeled in the system 1 through 8 in this fashion:
 |  |  |  |  |  |  |  |
| Star | Circle | Diamond | Triangle | Moon | Square | X | Skull |
|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| {Star} {rt1} | {Circle} {Coin} {rt2} | {Diamond} {rt3} | {Triangle} {rt4} | {Moon} {rt5} | {Square} {rt6} | {Cross} {X} {rt7} | {Skull} {rt8} |
Listed in {} are the chat commands for each icon, which will insert the icon into your chat window. The number labels 1-8 are used in the game's code and in macros when referring to raid icons. A very useful icon script the guilds I've been in have used for tanks marking their targets is:
| /script SetRaidTarget("target",1) |
You can change the
1 to be any of the numbers 1-8 of your choosing. The script, when created as a macro, will then quickly assign the chosen raid icon to your target. You can change "target" to be "self" or "mouseover" as well.
My own keybind for this is on mouse button 5 and ties other actions into the button using modifiers, in the following macro:
/cancelform [mod:alt]
/cast [mod:alt,target=mouseover,help] [mod:alt,help] [mod:alt,target=player] Regrowth
/stopmacro [mod:alt]
/script SetRaidTarget("target",1)
/clearfocus [form:1]
/focustarget [form:1]
/cast [form:1] Mangle (Bear)(); [form:3] Shred |
Edit: I added in the /clearfocus and /focustarget lines at Celeritas' suggestion :)Boss ModsThe problem with the Pugger
->
marking system is that boss mods such as DBM and Bigwigs have long used both Skull and X for their own scripted boss warnings, which is reasonable considering Skull and X are the last two in the list. The mods will drop that icon on a player to bring attention to them for things such as life leech and slag pots. If a guild is using either of these marks for kill targets, things get chaotic as they try to remark mobs mid-combat, usually manually. You can easily get around this, however, if you break away from the Pugger skull/X mark mentality and use the other icons.
In all honesty, the Pugger Skull-for-Kill-Target is a "lowest common denominator" tradition, implemented for group members who don't know the actual icon order and for tanks that have to pre-mark all of their targets before combat. It shocks me how many players don't know the order, when it seems to me so basic a thing. If you don't know the order and plan to raid, I highly suggest you learn it, as you can't rely on skull/x in high end raids.
If you're really stuck on the use of skull/X for your kill targets, you can go into your boss mods' LUA files and change the SetIcon line to a different corresponding icon number. Each of your raid assistants will have to make the change as well, and every time your boss mods were updated, you'd all have to make the change again manually.
Tanks with Personal MarksEver since the implementation of target icons in the game, I have run with guilds that assign each tank their own, "permanent" icon for all guild runs. In the days of necessary CC, we assigned semi-permanent icon targets to mages and hunters as well! The MT is often Star, the first icon, but different tanks have had their own favorite marks and can certainly choose a different one!
Personally, mine has been
in raids, though I moved it to
for the purposes of pugging on Kae-bear.
In Vortex:
- our warrior uses
- our feral uses
- our paladin uses
Our only rule in the icon claims has been to leave skull and X alone, as they belong to the bossmods!
The tanks each used the above /script SetRaidTarget("target",
1) and tied it to an easy-access key or mouse button (I use Mousebutton 5 for it), so that they can quickly mark a target while attacking mid-combat. You can even add a /cast AttackName or a /startattack line to the macro to make your click more versatile.
DPS DisciplineBreaking further from the Pugger marking system, most of the raiding guilds I've been in have opted for a variable kill order rather than having a set "moon then triangle" or even "skull then x" order. Obviously, this is something for voice chat communication and thus not really feasible in a pug (unless you use that ingame voice chat, but I won't go there). As far as a guild's internal raids are concerned, however, having a shifting command of which icon to kill first is a great way to discipline and train your DPS: discipline and attentiveness that is helpful, or even necessary, for learning boss fights and difficult strategies. Raiders need to be alert and able to react quickly to the leaders' commands, and variable kill orders are a way to train it.
The guilds I've been in that didn't use this variable kill order had a lot of difficulty with getting DPS to listen to the raid leader when it came to important target switches or interrupts during boss fights.
For raids without that level of discipline (PuGs) or communication, a set kill order among the tank targets is optimal.
PuggersWhen dealing with Puggers, you never know what you're going to get. Some will adapt quickly to the personal tank-mark system, while others act like you've just shoved their head under water off the side of an iceberg while the frenzyfish are swarming up from the depths, gnashing their teeth in hunger.
Generally, it is good at the start of the PuG to announce "My target icon is
(whatever), please kill it first." Those used to the Pugger mark style will just have to change from looking for Skull to looking for your mark. If they argue, just explain that you have it macroed, and they typically will not argue further: if they don't know about the game's raid mark order or are that unwilling to break Pugger tradition, then macros are probably a foreign continent for them as well.
From there,
don't mark all of the adds. Having too many marks up will confuse the puggers and make them ask for the full kill order, and even after explaining it, inevitably some will forget and still dps the wrong target.
Only mark the one that you are focusing on (aside from those rare CC), as a tank: the one you'd like the DPS to kill. Once your current target is dead, mark the next using your script. Think of your tank-mark as a "I'm putting threat into this one, so you're safe to dps it" icon.
| In a way, this is easier than the skull->X strategy since the DPS only has one mark to look for, so they really have little room to complain about the break from pugger tradition. |
- If DPS is on the wrong target, call them out on it and remind them that they need to be on your marked target.
- If there are multiple tanks, establish an order of precedence from the start of the instance: "Our MT is Soandso, their mark is , so kill the Star first. Our OT is Suchandsuch, so kill thesecond. Kill order: -> ."
- Alternatively, if your raid needs further simplicity, have your MT pull mobs off of the OT and/or remark them with her own target mark so that the DPS is absolutely clear on what to kill next. Thus, there will only be one mark for your DPS to pay attention to, and they can ignore all others. Whether this is skull or the MT's own mark doesn't matter as long as the dps is warned ahead of time.
TL:DR,- For one, be aware that Skull->X is actually backwards in the icon list order and that boss mods will automatically reassign them to important boss-specific alerts on players, so they are generally unsafe for use in raids as kill target markers.
- For two, I highly suggest using a targeting script for tanking to apply a mark to your target. This will save time between pulls as the tanks/RL will not have to manually mark each target for kill order, and it will more easily establish which mobs are being actively tanked vs being an offtarget.
- For three, if you go against the typical Pugger style of Skull->X kill order, be ready to let the DPS know what kill target they should be going after at the start of the instance. Many Puggers are easily confused.
Resto
Balance
Feral
As you can see, most of the responses were introverts (I's) and druids :) What do you think this mass of introverts means, particularly in comparison to the large chunk of extroverts (E's) found among the ENFJ's? Something to ponder.
