Difference between revisions of "Strike Order"
m (→Detailed order: added new slow strike trait links) |
Choongmyoung (Talk | contribs) (→{{t|Curse Bearer}} and {{t|Cursed}}) |
||
(19 intermediate revisions by 6 users not shown) | |||
Line 2: | Line 2: | ||
== Normal strike order == | == Normal strike order == | ||
− | The basic rules are : | + | The basic rules are: |
− | * | + | * Anyone with first strike will hit first. If both have first strike, the monster hits first. |
− | * | + | * Anyone with slow strike will hit last. If both have slow strike, the monster hits first. |
− | * | + | * If neither have first or slow strike, the higher level strikes first. If both are at equal level, the monster hits first. |
+ | |||
+ | Knockback, burning stack pop, or {{c|Sorcerer}}'s {{a|MANA SHIELD}} effect all happen after the combat. (Though it's not actually true, it's convenient to think so. Keep reading for the detailed explanation. ) | ||
== Detailed order == | == Detailed order == | ||
− | Many parameters | + | Many parameters affect the strike order. Here is the sequence from the highest priority to the lowest: |
− | # | + | #The special first strike of {{i|Reflex Potion}} and {{c|Assassin}}'s {{a|SWIFT HAND}} class trait |
#Monster with {{t|First Strike}} | #Monster with {{t|First Strike}} | ||
#Player with {{t|First Strike}} | #Player with {{t|First Strike}} | ||
Line 19: | Line 21: | ||
#Player with {{t|Slow Strike}} | #Player with {{t|Slow Strike}} | ||
− | |||
− | As a result : | + | '''Important:''' A player can counter {{t|Slow Strike}} with {{t|First Strike}}, counting as neither slowed nor first striking. |
− | *If one combatant has a higher attack speed than the other, that combatant strikes first. A player with both a bonus and a penalty to attack speed has a normal attack speed; a monster with both has | + | |
+ | '''As a result:''' | ||
+ | *If one combatant has a higher attack speed than the other, that combatant strikes first. A player with both a bonus and a penalty to attack speed has a normal attack speed; a monster with both has the newer attack speed. (Unless you are punished by Tikki Tooki, the monster would have slowed later on, thus having slow strike) | ||
*If both combatants have a fast attack speed or both have a slow attack speed, the monster attacks first. | *If both combatants have a fast attack speed or both have a slow attack speed, the monster attacks first. | ||
*If both combatants have a normal strike speed, then the combatant with the higher level attacks first, or in the case of a tie, the monster attacks first. | *If both combatants have a normal strike speed, then the combatant with the higher level attacks first, or in the case of a tie, the monster attacks first. | ||
− | == Special cases == | + | == Event orders and Special cases == |
+ | Because the game handles the events (damage and such) with event handlers and event queue, the actual order of the events and the results are quite complicated. Long story short, the descriptions below will show only the result. | ||
− | === | + | === Reflex potion === |
− | The | + | The Reflexes trait (obtained as a temporary buff from a Reflexes potion) guarantees a first strike no matter what. If the monster survives the player's initial blow it will attack the player, afterwards the player takes a second swing. |
− | + | ||
− | + | ||
− | === | + | ===Buff, debuffs, and strike order=== |
If you strike the monster first and kill it, it won't be able to give you the {{t|Mana Burned}}, {{t|Poisoned}}, {{t|Weakened}}, {{t|Corrosion}} debuffs. | If you strike the monster first and kill it, it won't be able to give you the {{t|Mana Burned}}, {{t|Poisoned}}, {{t|Weakened}}, {{t|Corrosion}} debuffs. | ||
However, you will still get {{t|Cursed}}, but only once and not twice (as it triggers when you kill or get damaged by a {{t|Curse Bearer}}). | However, you will still get {{t|Cursed}}, but only once and not twice (as it triggers when you kill or get damaged by a {{t|Curse Bearer}}). | ||
− | === | + | Almost all new buffs and debuffs are applied after both combatants strike. |
− | The | + | *So if you strike a weakening monster '''after''' he strikes you, your blow will be at '''normal strength''', not a weakened strength. |
+ | *If you strike '''first''' and remove a death protection from an {{m|Animated Armour}}, when the animated armor strikes you, its blow will be at '''normal strength''', not a weakened strength. | ||
+ | |||
+ | However, {{t|Life steal}} and {{t|Curse Bearer}} apply directly after the strike, meaning the strike order matters here. Also {{c|Warlord}}'s {{a|Determined}} trait also applies right at the moment of attack, so strike order matters. Burning stack pop also happens right after the strike, which is described below. | ||
+ | |||
+ | ==={{t|Life steal}}=== | ||
+ | The health you gain from life steal occurs directly after your hit, this means strike order matters. In rare cases first strike may allow you to strike a monster for which your current health would not suffice, as due to first strike and life steal, you may heal enough to survive the hit. In contrast, if you have almost 150% health, since you can't heal above 150% health, striking slower is actually more benefical. | ||
+ | |||
+ | ==={{t|Curse Bearer}} and {{t|Cursed}}=== | ||
+ | A monster with {{t|Curse Bearer}} applies one stack of curse '''directly after''' it damages the player. Similarly, one curse stack is removed '''directly after''' a monster without curse bearer trait is killed. Though the effect of curse doesn't matter at attack damages, in some rare edge cases this matters to curse stacks left. | ||
+ | |||
+ | ===Burning stack pop=== | ||
+ | Attacking a burning monster directly adds a magical damage with player's attack, so no confusion here. The problem is when you have burning on the other monster. In that case, burning stack will pop '''right after''' player's attack. While this may not affect the fight, when the target monster has {{t|Curse Bearer}} trait, it becomes a problem as the curse applies directly after it is killed. So here's the result: | ||
+ | |||
+ | If the player strikes first, | ||
+ | * Player's attack | ||
+ | * Burning pop, which kills the 'other' monster | ||
+ | * Monster's attack with {{t|Curse Bearer}} | ||
+ | 1 curse stack left. | ||
+ | |||
+ | If the monster strikes first, | ||
+ | * Monster's attack with {{t|Curse Bearer}} | ||
+ | * Player's attack | ||
+ | * Burning pop, which kills the 'other' monster → 1 curse stack removed | ||
+ | 0 curse stack left. | ||
+ | |||
+ | ===Knockback and Burning=== | ||
+ | Actually, when the player strikes first, the monster's attack is '''fated to be applied''' after the player attacks him. However, the knockback event could apply after the player's attack, and it makes a confusion. | ||
+ | |||
+ | If the player strikes first, | ||
+ | * Player's attack | ||
+ | * Knockback | ||
+ | * Burning stack pop | ||
+ | * Monster's attack when he survived the player's attack (even if it is dead from knockback damage!) | ||
+ | Whilst it may seems like the knockback occurs after the two attack events (because in intuition dead monster can't attack back), knockback is actually happening before the monster's attack. | ||
+ | |||
+ | If the monster strikes first, | ||
+ | * Monster's attack | ||
+ | * Player's attack | ||
+ | * Knockback | ||
+ | * Burning stack pop | ||
+ | |||
+ | Also it is notable that the knockback occurs before the burning stack pop; this is why the "doublekill" is pratically doable with knockback + burning. Knockback damage can't kill the second target, but it can reduce its health to 1 so that the burning pop could kill it. | ||
+ | |||
+ | ==={{c|Warlord}}'s {{a|DETERMINED}}=== | ||
+ | From the class trait, Warlord gets 30% attack bonus whenever below 50% health. Unlike any other buff or debuff effects which is calculated based on the stats before the combat, Warlord only gets 30% attack bonus if you are below 50% health at that precise moment, making the strike order matters. If your health is above 50% health and you are going to finish off your opponent with first strike or having monster be slowed, you should calculate your damage output carefully if you can win the battle without the attack bonus. | ||
+ | |||
+ | ==={{c|Gorgon}}'s {{t|Death-gaze}}=== | ||
+ | Gorgon's deathgaze ability deals unresistable 100% of your base damage to the monster before the combat if the monster's health is below deathgaze%. This special attack has interaction with some effects, but not with others. Precisely, the deathgaze event does not trigger knockback or burning stack pop, but it's otherwise same with the normal attack. For example, it will trigger {{t|Cowardly}} or {{t|Blinks}}. For example, let's say the Gorgon with knockback is striking the blinking monster, and the monster strikes first. | ||
+ | |||
+ | * Deathgaze | ||
+ | * Blink: blink away | ||
+ | * Monster's attack (even if it is far from the player character) | ||
+ | * Player's attack (even if it is far from the player character) | ||
+ | * Blink (however, it only blinks when it is right next to the player. So, it wouldn't blink) | ||
+ | * Knockback (again, even if it is far from the player character!) | ||
+ | * Blink, if it gets damage from the knockback (but again, it would probably be far from the player character, so no blink) | ||
+ | |||
+ | There is a known bug that deathgaze + {{t|Life steal}} can absorb health from the monster over the monster's remaining health limit. | ||
+ | |||
+ | ==={{c|Sorcerer}}'s {{a|MANA SHIELD}}=== | ||
+ | Mana shield occur right after monster's attack. That's why in the normal circumstances (monster attacking first) mana shield is dealing the damage before the normal attack. Like Gorgon's deathgaze, mana shield also has no interaction with knockback or burning. | ||
+ | |||
+ | ==={{c|Assassin}}'s {{a|SWIFT HAND}}=== | ||
+ | As described in the class trait, this effect overwhelms all other effects in the game. Assassin will insta-kill any lower level monster with no harm at all at any circumstances. {{t|Curse Bearer}} still applies, though. | ||
+ | |||
+ | ===Attack Speed Cancellation=== | ||
+ | The slow strike and first strike effects can be combined, altering the strike order. The platemail, which slows the player is good example: a player wearing it should in theory always strike last. However : | ||
+ | * First strike ability (either from the {{s|GETINDARE}} glyph or {{c|Rogue}} class feature [NOT the assassin's exploration first strike]) cancels out player's slow, resulting in normal striking speed. As such a slowed player with first strike can get a first hit against slowed enemies regardless of their level. | ||
+ | |||
+ | But for monster, the effect does not cancel out. {{t|slowed}} debuff will temporarily overwhelm the {{t|first strike}}. However, with punishment of {{g|Tikki Tokki}} a monster could have both at the same time. In this case the first strike overwhelms slowed debuff. | ||
− | === | + | ==={{t|Retaliate: Fireball}}=== |
− | + | Using {{s|BURNDAYRAZ}} on the retaliating monster is similar to striking first, but the order of the events is slightly different. It might be a bug. | |
+ | * BURNDAYRAZ attack | ||
+ | * Retaliate | ||
+ | * Burning stack pop | ||
− | + | Compare this to the melee case with the player's first strike. | |
− | + | * Player's attack | |
− | + | * Burning stack pop | |
+ | * Monster's attack | ||
− | |||
− | + | [[Category:Strategy]] | |
− | + | {{MainNav}} |
Latest revision as of 04:43, 28 July 2018
The strike order defines the sequence in which the player and its opponent will hit each other. That order is mainly important for the final blow (the blow that will kill the monster), to determine whether he will have the chance to hit the player before dying. It might also be of some importance with life steal.
Contents
- 1 Normal strike order
- 2 Detailed order
- 3 Event orders and Special cases
- 3.1 Reflex potion
- 3.2 Buff, debuffs, and strike order
- 3.3 Life steal
- 3.4 Curse Bearer and Cursed
- 3.5 Burning stack pop
- 3.6 Knockback and Burning
- 3.7 Warlord's DETERMINED
- 3.8 Gorgon's Death-gaze
- 3.9 Sorcerer's MANA SHIELD
- 3.10 Assassin's SWIFT HAND
- 3.11 Attack Speed Cancellation
- 3.12 Retaliate: Fireball
Normal strike order
The basic rules are:
- Anyone with first strike will hit first. If both have first strike, the monster hits first.
- Anyone with slow strike will hit last. If both have slow strike, the monster hits first.
- If neither have first or slow strike, the higher level strikes first. If both are at equal level, the monster hits first.
Knockback, burning stack pop, or Sorcerer's
MANA SHIELD effect all happen after the combat. (Though it's not actually true, it's convenient to think so. Keep reading for the detailed explanation. )
Detailed order
Many parameters affect the strike order. Here is the sequence from the highest priority to the lowest:
- The special first strike of
Reflex Potion and
Assassin's
SWIFT HAND class trait
- Monster with
First Strike
- Player with
First Strike
- Monster (higher or equal level as player)
- Player
- Monster (lower level as player)
- Monster
Slowed
- Player with
Slow Strike
Important: A player can counter Slow Strike with
First Strike, counting as neither slowed nor first striking.
As a result:
- If one combatant has a higher attack speed than the other, that combatant strikes first. A player with both a bonus and a penalty to attack speed has a normal attack speed; a monster with both has the newer attack speed. (Unless you are punished by Tikki Tooki, the monster would have slowed later on, thus having slow strike)
- If both combatants have a fast attack speed or both have a slow attack speed, the monster attacks first.
- If both combatants have a normal strike speed, then the combatant with the higher level attacks first, or in the case of a tie, the monster attacks first.
Event orders and Special cases
Because the game handles the events (damage and such) with event handlers and event queue, the actual order of the events and the results are quite complicated. Long story short, the descriptions below will show only the result.
Reflex potion
The Reflexes trait (obtained as a temporary buff from a Reflexes potion) guarantees a first strike no matter what. If the monster survives the player's initial blow it will attack the player, afterwards the player takes a second swing.
Buff, debuffs, and strike order
If you strike the monster first and kill it, it won't be able to give you the Mana Burned,
Poisoned,
Weakened,
Corrosion debuffs.
However, you will still get
Cursed, but only once and not twice (as it triggers when you kill or get damaged by a
Curse Bearer).
Almost all new buffs and debuffs are applied after both combatants strike.
- So if you strike a weakening monster after he strikes you, your blow will be at normal strength, not a weakened strength.
- If you strike first and remove a death protection from an
Animated Armour, when the animated armor strikes you, its blow will be at normal strength, not a weakened strength.
However, Life steal and
Curse Bearer apply directly after the strike, meaning the strike order matters here. Also
Warlord's
Determined trait also applies right at the moment of attack, so strike order matters. Burning stack pop also happens right after the strike, which is described below.
Life steal
The health you gain from life steal occurs directly after your hit, this means strike order matters. In rare cases first strike may allow you to strike a monster for which your current health would not suffice, as due to first strike and life steal, you may heal enough to survive the hit. In contrast, if you have almost 150% health, since you can't heal above 150% health, striking slower is actually more benefical.
Curse Bearer and
Cursed
A monster with Curse Bearer applies one stack of curse directly after it damages the player. Similarly, one curse stack is removed directly after a monster without curse bearer trait is killed. Though the effect of curse doesn't matter at attack damages, in some rare edge cases this matters to curse stacks left.
Burning stack pop
Attacking a burning monster directly adds a magical damage with player's attack, so no confusion here. The problem is when you have burning on the other monster. In that case, burning stack will pop right after player's attack. While this may not affect the fight, when the target monster has Curse Bearer trait, it becomes a problem as the curse applies directly after it is killed. So here's the result:
If the player strikes first,
- Player's attack
- Burning pop, which kills the 'other' monster
- Monster's attack with
Curse Bearer
1 curse stack left.
If the monster strikes first,
- Monster's attack with
Curse Bearer
- Player's attack
- Burning pop, which kills the 'other' monster → 1 curse stack removed
0 curse stack left.
Knockback and Burning
Actually, when the player strikes first, the monster's attack is fated to be applied after the player attacks him. However, the knockback event could apply after the player's attack, and it makes a confusion.
If the player strikes first,
- Player's attack
- Knockback
- Burning stack pop
- Monster's attack when he survived the player's attack (even if it is dead from knockback damage!)
Whilst it may seems like the knockback occurs after the two attack events (because in intuition dead monster can't attack back), knockback is actually happening before the monster's attack.
If the monster strikes first,
- Monster's attack
- Player's attack
- Knockback
- Burning stack pop
Also it is notable that the knockback occurs before the burning stack pop; this is why the "doublekill" is pratically doable with knockback + burning. Knockback damage can't kill the second target, but it can reduce its health to 1 so that the burning pop could kill it.
Warlord's
DETERMINED
From the class trait, Warlord gets 30% attack bonus whenever below 50% health. Unlike any other buff or debuff effects which is calculated based on the stats before the combat, Warlord only gets 30% attack bonus if you are below 50% health at that precise moment, making the strike order matters. If your health is above 50% health and you are going to finish off your opponent with first strike or having monster be slowed, you should calculate your damage output carefully if you can win the battle without the attack bonus.
Gorgon's
Death-gaze
Gorgon's deathgaze ability deals unresistable 100% of your base damage to the monster before the combat if the monster's health is below deathgaze%. This special attack has interaction with some effects, but not with others. Precisely, the deathgaze event does not trigger knockback or burning stack pop, but it's otherwise same with the normal attack. For example, it will trigger Cowardly or
Blinks. For example, let's say the Gorgon with knockback is striking the blinking monster, and the monster strikes first.
- Deathgaze
- Blink: blink away
- Monster's attack (even if it is far from the player character)
- Player's attack (even if it is far from the player character)
- Blink (however, it only blinks when it is right next to the player. So, it wouldn't blink)
- Knockback (again, even if it is far from the player character!)
- Blink, if it gets damage from the knockback (but again, it would probably be far from the player character, so no blink)
There is a known bug that deathgaze + Life steal can absorb health from the monster over the monster's remaining health limit.
Sorcerer's
MANA SHIELD
Mana shield occur right after monster's attack. That's why in the normal circumstances (monster attacking first) mana shield is dealing the damage before the normal attack. Like Gorgon's deathgaze, mana shield also has no interaction with knockback or burning.
Assassin's
SWIFT HAND
As described in the class trait, this effect overwhelms all other effects in the game. Assassin will insta-kill any lower level monster with no harm at all at any circumstances. Curse Bearer still applies, though.
Attack Speed Cancellation
The slow strike and first strike effects can be combined, altering the strike order. The platemail, which slows the player is good example: a player wearing it should in theory always strike last. However :
- First strike ability (either from the
GETINDARE glyph or
Rogue class feature [NOT the assassin's exploration first strike]) cancels out player's slow, resulting in normal striking speed. As such a slowed player with first strike can get a first hit against slowed enemies regardless of their level.
But for monster, the effect does not cancel out. slowed debuff will temporarily overwhelm the
first strike. However, with punishment of God: Tikki Tokki Tikki Tokki a monster could have both at the same time. In this case the first strike overwhelms slowed debuff.
Retaliate: Fireball
Using BURNDAYRAZ on the retaliating monster is similar to striking first, but the order of the events is slightly different. It might be a bug.
- BURNDAYRAZ attack
- Retaliate
- Burning stack pop
Compare this to the melee case with the player's first strike.
- Player's attack
- Burning stack pop
- Monster's attack