Marshals,
Update 0.13.1 is now available for Crown Marshal.
This update reworks the Lancer's charge movement and corridor damage so the dash now physically plays out at the unit's current movement speed. It also fixes an issue where middle-button camera dragging could remain stuck to mouse movement.
Balance Changes
Lancer Charge
The Lancer's dash is no longer instantaneous.
After a strike connects, the Lancer now physically gallops the full 6 m at its current movement speed.
When not slowed, the full charge takes approximately 1.5 seconds.
During the charge:
- The Lancer cannot turn.
- The Lancer cannot begin another attack.
- Enemies standing in the charge path are pushed aside instead of stopping the Lancer.
If the Lancer dies during the charge, any remaining distance it has not actually traveled deals no damage.
Damage from the charge corridor has also been adjusted.
Enemies swept by the 2.8 m-wide corridor now take:
50% of the Lancer's Attack
instead of one full-Attack hit.
The directly attacked target still takes the full attack hit.
Concussive Lance retains its existing paralysis behavior:
- The directly attacked target is still paralysed.
- Enemies swept by the charge corridor are still paralysed.
The following rules remain unchanged:
- Charge distance remains 6 m.
- Corridor width remains 2.8 m.
- A given enemy can only take one corridor hit during a single charge.
Light Gallop already removes the Lancer's charge entirely and is unaffected by this change.
Fixes and Improvements
Middle-Button Camera Dragging
Fixed the camera continuing to follow the mouse after a middle-button drag.
Previously, if any of the following happened during a drag:
- A match-end or similar window appeared
- The game window lost focus
- The middle mouse button was released outside the battlefield
the game could fail to receive the button-release event.
After that, every mouse movement could continue panning the camera, while mouse interactions such as:
- Hover information
- Placement previews
stopped working correctly.
This issue has now been fixed.
Thank you for your continued support and feedback.
See you on the battlefield, Marshals!