Sprint should automatically resume after being interrupted (Hold & Toggle Sprint)
I've noticed that both Hold Sprint and Toggle Sprint currently require an additional sprint input every time sprint is interrupted by certain actions, such as shooting, looting, stopping movement, strafing or other gameplay actions.
To be clear, I'm not asking to be able to sprint while shooting, and this has nothing to do with the stamina system. I fully understand that those actions should interrupt sprint.
The issue is what happens after the interruption.
For Hold Sprint, if I'm still physically holding the sprint key, I would expect my character to automatically resume sprinting as soon as sprint is allowed again and I'm moving forward. This is how Hold Sprint behaves in many modern FPS games and feels much more natural.
For Toggle Sprint, I would also expect sprint to resume automatically after a temporary interruption, since sprint was already toggled on. Instead, the game currently requires another press of the sprint key.
I also tested this on a different keyboard and by rebinding sprint to multiple mouse buttons, and the behavior is exactly the same, so this doesn't appear to be a keyboard or hardware issue.
Right now, both options require an extra sprint input after every interruption, which makes movement feel less fluid and adds unnecessary key presses during normal gameplay.
I think sprint should behave as a persistent state. If Hold Sprint is active because the sprint key is still being held, or Toggle Sprint is active because it has been toggled on, sprint should automatically resume whenever sprinting becomes possible again.
Please let me know if you're experiencing the same behavior as well or if this is an intended game design?
Comentários
Hello there,
Thanks for the detailed write-up.
From the current behavior setup, this sounds more like intended sprint behavior than a broken keybind. Sprint is treated as something that can be interrupted by actions like firing, reloading, and certain other gameplay actions, rather than a persistent state that always resumes automatically afterward.
There is some queued sprint behavior in certain cases, but it appears to be limited. For example, toggle sprint can queue back in after actions like jump, slide, clamber, or vault complete, but that is not how all interruptions are handled.
So if Hold Sprint and Toggle Sprint both require a fresh sprint input after things like shooting or other interrupting actions, that looks consistent with the current design rather than a keyboard issue.
That said, the QoL suggestion makes sense. Automatic sprint resuming after temporary interruptions would be a reasonable accessibility and input-flow improvement, especially for Hold Sprint.
The best place to share it is on the official Marathon Discord rather than our Help Forums. To that point, we suggest posting your thoughts there, if you haven't already done so. You can find the specific feedback channels below:
- Targeted Feedback: https://discord.com/channels/1303855380845301861/1478943000792006768
- Freeform Feedback - https://discord.com/channels/1303855380845301861/1478943087957905550
Thank you for the quick response. I will post this on Discord. Have a nice day. :)
Por favor, entrar para comentar.