Mir3Reg.ComReturn to homepage

[Client 1.0.86 Update]

Software Updates

Thank you for reporting how Steadfast (稳如泰山) behaved in player combat. Previously, the attacker could see the opponent’s full flinch, while the player who was hit saw only a flicker. This update fixes that discrepancy.

Player versus player
When another player hits you directly with a melee attack or a spell, you’ll see your character’s full flinch under the original hit-reaction rules, whether Steadfast is on or off. This applies both on foot and on horseback. Even if a monster has just hit you, a player attack that lands immediately afterward will still trigger the normal flinch.

Fighting monsters
With Steadfast on, you can keep walking, running, or riding when a monster hits you. You still lose health normally. Knockback, stun, and the restriction on running at low health still follow the original rules.


A player reported on the official website: “The biggest problem with removing flinch is that characters move too fast. Spells aimed at a moving character can’t seem to hit them. Another way to put it is that the visuals seem out of sync. When someone keeps running, at most 1 of a mage’s 10 attacks on the moving target lands.”

Our assessment before the release of 1.0.86: The report identifies a real effect of Steadfast on player combat. It does not establish that the visuals are out of sync or that mage accuracy has fallen to 10%.

Version 1.0.82 kept the original 600 ms movement interval. What changed was what happened after a hit had already landed. Previously, a character paused when hit. In that version, a normal hit still cost health, but the character could finish the current step and keep moving. A target could therefore cover a few extra tiles in the same few seconds. There was a basis for saying characters felt faster, especially for mages who used to follow up on the pause caused by their first hit. Giving everyone the option made access equal, but also changed how well different classes could chase or escape. Code references: movement interval (line 5) · hit handling during movement (line 10967).

The first hit is the one to check. If the first hit took health off the target, the target kept running, and the mage struggled to land follow-up attacks, that fits the removal of the pause on hit. But if every spell missed before the target had taken even one hit, removing a pause that only happens after a hit cannot directly explain those misses. A cast request includes both the target ID and the target tile. We need to check which skill was used, whether it locked onto the player, and whether the server actually deducted health. Where the spell effect appears is not enough to diagnose a sync problem. Code reference: cast request (line 1215).

Who benefits after the release of 1.0.86?

In the reported case of a mage attacking a warrior who keeps running, the mage may benefit directly. Compared with 1.0.82, restoring the pause on hit in player combat gives a mage who lands the first hit before a warrior closes in time to open up distance or prepare another attack. What improves is the opportunity to follow up after the first hit. The first hit itself does not become easier to land.

Conversely, once the warrior gets into melee range, the warrior benefits. A mage trying to run away will also pause briefly if a melee attack lands, giving the warrior a better chance to follow up with another strike or a combo.

So if the question is which class gains more in overall win rate, we don’t yet have measurements to answer it. The most informative comparison would measure two things separately: how many more hits a mage lands before a warrior closes in, and how many more strikes or combos a warrior lands once in melee range.