#5714 Sidestep Mechanic Broken for Wesker in Independent Use of dashes After Recent Fixes

Dead by Daylight

Overview

Bugs (3864)

Releases

Dead by Daylight

Home

Discover Projects

Bug: Sidestep Mechanic Broken for Wesker in Independent Use of dashes After Recent Fixes

191 °C

Bug #5714

Sidestep Mechanic Broken for Wesker in Independent Use of dashes After Recent Fixes

Status:	Open
Priority:	High
Added by:	Anonymous on July 25, '26
Assigned to:	Unassigned
Due date:
Reported for:	10.0.3
Actual Result:	Despite the fix attempted for the "sidestep" mechanic, the character currently travels in a strictly linear forward trajectory on individual bounds. The recent flick adjustments have overwritten the partial fix, resulting in zero lateral movement (sidestepping) when performing bounds independently or with a delay or at all.
Expected Result:	The character model should correctly perform a "sidestep" (shifting slightly in the direction of the held WASD keys) exactly on the starting frame of the power. Crucially, this sidestep must apply to BOTH bounds independently, not just when rapidly double tapping them.
Severity:	Blocker
Reproducibility:	Always
Platform:	Steam
Additional Notes & Comments:	This is one of the most crucial problems for mastermind community. Open talk of it would be apperciated.

Steps to Reproduce

Input a continuous movement command by holding 'A' or 'D' or 'W' or 'S'.
Keep the camera facing directly forward.
Trigger the primary Virulent Bound.
Observe the immediate trajectory—notice the absolute lack of a sidestep; the movement is rigidly locked forward.
Wait briefly in the chain window, continue holding the key, and trigger the secondary Bound.
Notice that the secondary Bound also completely lacks the sidestep mechanic.

Explanation

This is a regression report regarding the "sidestep" mechanic (which was officially referenced in the May 28th patch notes: "Fixed an issue where The Mastermind was not able to make a sidestep...").

While a partial correction was introduced recently, it only functions when rapidly tapping and then holding bounds. Because it was implemented incorrectly, subsequent fixes for "insta-flicks" have broken it once again for independent uses. Currently, both the primary and secondary bounds strictly ignore directional inputs on startup when used on their own. This mechanic functioned flawlessly from release (patch 6.7.2) up to the 9.5.0 PTB and needs to be fully reinstated for each bound individually.