On some bosses, aggro (to start the fight) is based on proximity to the boss. At a certain point in raiding, it's good to know the actual aggro boundary so you don't go past it and prematurely start the fight. It's also good to min/max any precasts you want to do.
How I'm creating the boundaries is via a trail with a very short fade range. Reason being is that it's only used for the aggro boundary and nothing else, and to constantly see it while you fight is annoying.
With all that said, here's a list of bosses where an aggro boundary is applicable:
[x] Vale Guardian
[x] Gorseval
[x] Sabetha
[x] Matthias
[x] Keep Construct
[x] Samarog
[x] Conjured Amalgamate
[x] Cardinal Sabir
Now yes, while other bosses do have aggro ranges, they aren't that important; running into the Deimos arena still gives people time to get their bearings since you're not immediately fighting the boss, for example.
QuitarHero
commented
4 years ago
On some bosses, aggro (to start the fight) is based on proximity to the boss. At a certain point in raiding, it's good to know the actual aggro boundary so you don't go past it and prematurely start the fight. It's also good to min/max any precasts you want to do.
How I'm creating the boundaries is via a trail with a very short fade range. Reason being is that it's only used for the aggro boundary and nothing else, and to constantly see it while you fight is annoying.
With all that said, here's a list of bosses where an aggro boundary is applicable:
Now yes, while other bosses do have aggro ranges, they aren't that important; running into the Deimos arena still gives people time to get their bearings since you're not immediately fighting the boss, for example.