Woby sprinting should have a small buffer when standing still for less than a second.

[lowercase skye]

When Woby's sprinting, if you stop moving for even a fraction of a second she IMMEDIATELY snaps back to normal walking speed. This can be intrusive in a lot of situations:

- If using WASD to move, there will sometimes be moments where for example you're pressing W, then entirely let it go for just a fraction of a second before pressing A or D. This fraction of a second will cause Woby to stop sprinting and have to build up speed again.
- If holding Left Click to move, if you let go of the button and click somewhere else, you'll very briefly go to a complete stand still, causing Woby to stop sprinting and have to build up speed again.
- If walking with WASD and you want to switch to clicking to move, like if you want to open the map for example, you'll have to stand still for a very brief moment in order for the click to be registered, causing Woby to stop sprinting and have to build up speed again.

Basically, there are many many moments in this game where you "stop moving" for a tiny fraction of a second and then start moving again, but these will always count as standing entirely still by Woby's standards. This sort of thing could also be observed when playing Wilbur in Shipwrecked, and was just as intrusive there. I think adding a small buffer where you can stand still for juuuust a moment without Woby stopping sprinting would improve the general use of the skill and overall player experience as Walter.

[V2C]

This buffer is currently tuned at 0.1 seconds.  I want to keep it low, but perhaps it's too low right now?  I'd love to hear more feedback on this after people have tried it out a bit more.

[Y0sH]

12 minutes ago, lowercase skye said:

When Woby's sprinting, if you stop moving for even a fraction of a second she IMMEDIATELY snaps back to normal walking speed. This can be intrusive in a lot of situations:

- If using WASD to move, there will sometimes be moments where for example you're pressing W, then entirely let it go for just a fraction of a second before pressing A or D. This fraction of a second will cause Woby to stop sprinting and have to build up speed again.
- If holding Left Click to move, if you let go of the button and click somewhere else, you'll very briefly go to a complete stand still, causing Woby to stop sprinting and have to build up speed again.
- If walking with WASD and you want to switch to clicking to move, like if you want to open the map for example, you'll have to stand still for a very brief moment in order for the click to be registered, causing Woby to stop sprinting and have to build up speed again.

Basically, there are many many moments in this game where you "stop moving" for a tiny fraction of a second and then start moving again, but these will always count as standing entirely still by Woby's standards. This sort of thing could also be observed when playing Wilbur in Shipwrecked, and was just as intrusive there. I think adding a small buffer where you can stand still for juuuust a moment without Woby stopping sprinting would improve the general use of the skill and overall player experience as Walter.

Maybe .3-.5 would make it a little better. I've noticed this too and makes the sprint feel a little clunky.

[Guille6785]

agreed

[-Variant]

1 hour ago, V2C said:

This buffer is currently tuned at 0.1 seconds.  I want to keep it low, but perhaps it's too low right now?  I'd love to hear more feedback on this after people have tried it out a bit more.

Please, please, share it with Wonkey, too. Even Wonkey's buffer seems too small.
A bit more leeway would do both of them wonders.

[Maxil20]

1 hour ago, V2C said:

This buffer is currently tuned at 0.1 seconds.  I want to keep it low, but perhaps it's too low right now?  I'd love to hear more feedback on this after people have tried it out a bit more.

Given that the tickrate of DST by itself is 15 updates per second without modifying it in forest+cave worlds, it’s pretty realistic to try moving another direction but having said input get stuck in processing and therefore go longer than .1 second, especially when you factor in the client’s latency as well. I think a delay of ~.33-.5 would be able to work better for this?