Strike Order - Revision history

Choongmyoung: /* {{t|Curse Bearer}} and {{t|Cursed}} */

2018-07-28T04:43:21Z

‎{{t|Curse Bearer}} and {{t|Cursed}}

Choongmyoung: /* Normal strike order */

2018-07-28T04:36:14Z

‎Normal strike order

Choongmyoung at 18:38, 27 July 2018

2018-07-27T18:38:02Z

Show changes

Choongmyoung: /* Special cases */

2017-11-15T18:12:54Z

‎Special cases

Choongmyoung: /* Life steal */

2017-11-15T18:06:03Z

‎Life steal

Choongmyoung: /* Detailed order */

2017-11-15T18:02:55Z

‎Detailed order

Luigifan: /* Detailed order */ Grammar check

2017-02-06T22:45:18Z

‎Detailed order: Grammar check

Luigifan: /* Normal strike order */ Grammar check

2017-02-06T22:43:37Z

‎Normal strike order: Grammar check

Luigifan: /* Normal strike order */ You forgot something...

2017-02-06T22:43:10Z

‎Normal strike order: You forgot something...

Zayyeh: /* Retaliation */

2016-08-05T08:18:09Z

‎Retaliation

@@ Line 49: / Line 49: @@
 ==={{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. This matters only in such a sharp edge cases, and generally it's not important at all.
+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===

@@ Line 7: / Line 7: @@
 * 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
+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 ==

@@ Line 41: / Line 41: @@
 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}}).
 === Reflex potion ===

@@ Line 57: / Line 57: @@
 === Life steal ===
-The health you gain from {{t|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.
+The health you gain from {{t|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.
 [[Category:Strategy]]
 {{MainNav}}

@@ Line 22: / Line 22: @@
 '''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 a slow attack speed.
+*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.

@@ Line 9: / Line 9: @@
 == Detailed order ==
-Many parameters do impact the strike order is. Here is the sequence from the highest priority to the lowest :
+Many parameters affect the strike order. Here is the sequence from the highest priority to the lowest:
 #[[Classes#Gorgon|Gorgon]] (player class) death gaze ability, [[Assassin]] swift hands, and first strike of {{i|Reflex Potion}}
 #Monster with {{t|First Strike}}
@@ Line 21: / Line 21: @@
 '''Important:''' A player can counter {{t|Slow Strike}} with {{t|First Strike}}, counting as neither slowed nor first striking.
-'''As a result :'''
+'''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 a slow attack speed.
 *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.
-===Buff, debuffs and strike order===
+===Buff, debuffs, and strike order===
 Any 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 strentgh'''.
+*So if you strike a weakening monster '''after''' he strikes you, your blow will be at '''normal 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'''.

@@ Line 2: / Line 2: @@
 == Normal strike order ==
-The basic rules are :
+The basic rules are:
 * Higher or same level monsters strike the player first, unless the player has first strike
 * Lower level monsters strike after the player (so they won't be allowed to hit the player after the final blow), unless the monster has first strike

← Older revision		Revision as of 08:18, 5 August 2016
Line 46:		Line 46:

	=== Retaliation ===		=== Retaliation ===
−	Effects that depend on the player being hit take effect after the monster hits. For instance, if a {{c\|Sorcerer}} has the first attack against a monster, then the sequence is as follows: the Sorcerer hits the monster normally, then the monster hits, then the monster takes damage from {{a\|~~Mana Shield~~}}. So, if you are relying on the {{a\|~~Mana Shield~~}} damage to finish off the monster, remember that he will hit you...	+	Effects that depend on the player being hit take effect after the monster hits. For instance, if a {{c\|Sorcerer}} has the first attack against a monster, then the sequence is as follows: the Sorcerer hits the monster normally, then the monster hits, then the monster takes damage from {{a\|MANA SHIELD}}. So, if you are relying on the {{a\|MANA SHIELD}} damage to finish off the monster, remember that he will hit you...