by RedIce » Wed 2008 Apr 02 15:52 EDT
Stunning
In order to stun you must be able to see the move that you are stunning. Your chat filters must be set so you will see the message. In all situations you will need the following chat filters OFF.
Special actions started on/by You, Your party, your alliance, and your foe.
Specific events you will also need
Special actions started on/by Other people and NPCs.
If you do not have the “Other people” or “NPC” filters off you may miss messages in things such as einherjar and dynamis where you are in multiple alliances.
I am not going to create a list of things you need to stun when. You should know what is dangerous.
Stun orders are important to keep from overlapping stuns and to prevent a period of time when no one would be able to stun. The general rule of thumb when stunning is DO NOT cast if you are up to stun. DO NOT cast if you are next in line to stun. You do not want to be casting when you need to stun.
On mobs that do not build resistance to stun it is ok to “Free stun” a few seconds after your turn as come up in order. This gives tanks an extra second or two on their utsusemi cool down. This also slows down the amount of damage the mob can do over the course of the fight. But do not stun as soon as your turn comes up, wait a little while to make sure the next person’s stun is up or let him finish his cast. But on mobs like this you should not “sit” on your stun for more than 30 seconds. But on mobs that do build resistance DO NOT free stun, stun only what is needed. It sucks but you can be sitting on your stun for a long time.
I know it’s a pain and annoying to have to retype parts of macros every event, but having a simple /p chat is very useful as a refresh to whose stun it is. A SOFT call like #14 is ok too.
Like I said before and will continue to say, BLM is not a static job. You need to adapt and be dynamic depending on your situation. Use your head.
[u]Stunning[/u]
In order to stun you must be able to see the move that you are stunning. Your chat filters must be set so you will see the message. In all situations you will need the following chat filters OFF.
Special actions started on/by You, Your party, your alliance, and your foe.
Specific events you will also need
Special actions started on/by Other people and NPCs.
If you do not have the “Other people” or “NPC” filters off you may miss messages in things such as einherjar and dynamis where you are in multiple alliances.
I am not going to create a list of things you need to stun when. You should know what is dangerous.
Stun orders are important to keep from overlapping stuns and to prevent a period of time when no one would be able to stun. The general rule of thumb when stunning is DO NOT cast if you are up to stun. DO NOT cast if you are next in line to stun. You do not want to be casting when you need to stun.
On mobs that do not build resistance to stun it is ok to “Free stun” a few seconds after your turn as come up in order. This gives tanks an extra second or two on their utsusemi cool down. This also slows down the amount of damage the mob can do over the course of the fight. But do not stun as soon as your turn comes up, wait a little while to make sure the next person’s stun is up or let him finish his cast. But on mobs like this you should not “sit” on your stun for more than 30 seconds. But on mobs that do build resistance DO NOT free stun, stun only what is needed. It sucks but you can be sitting on your stun for a long time.
I know it’s a pain and annoying to have to retype parts of macros every event, but having a simple /p chat is very useful as a refresh to whose stun it is. A SOFT call like #14 is ok too.
Like I said before and will continue to say, BLM is not a static job. You need to adapt and be dynamic depending on your situation. Use your head.