[DP] "Always Run" weird behaviour

[Nash]

In most FPSes I've played, if there's an "Always Run" option and you turn it on, it'll reverse the behaviour of the +speed (or whatever) button - player will run without it, but will walk when you hold it down.

In DarkPlaces, if you turn on Always Run, you will... well, literally always run, regardless of the +speed button (so it's not possible to walk anymore).

Does anyone know if it's possible to fix this so that it behaves like most other games?

[redrum]

When would you want to walk anyway?

[Nash]

For puzzle-like elements that require you to not move fast (like a narrow platform on top of some lava, or carefully navigating through a bunch of sleeping monsters so that you don't touch them and wake them up).

Obviously this is for modding purposes, not standard Quake stuff.

So any other takers?

[Sajt]

Set cl_movespeedkey to 0.5

[Seven]

Hi Nash,

I dont know if this helps in your case, but I want to post a note from LordHavoc himself to this topic.
Maybe you can get some help out of it.
The text comes from another forum:


Originally Posted by xxx View Post:
In recent releases of darkplaces, I noticed that the option for "always run" has disappeared. So I have been using +speed in the console or in autoexec.cfg. Will this have any undesirable effect?

LordHavocs answer:
+speed doubles your keyboard turn rate (not that you use it) as well as forward/backward movement speed (which is what Always Run does), and your strafe speed (which Always Run does not do), so it has somewhat different physics.

DP defaults the forward/back speed to 400 (like Always Run does), so in effect there is no reason to use +speed or even mess with the option, it's already on if you don't use other engines - and therein lies the problem - if the config.cfg was made by another engine without Always Run on, DP will adopt that, figuring you intentionally had Always Run off.

I have added it back in the local copy, so the next release will have it again, but you will see that it is already on by default as mentioned above.

Here are all the relevant settings for best play:
cl_forwardspeed 400
cl_backspeed 400
cl_sidespeed 350
cl_upspeed 400
(Note that sv_maxspeed is 320, so these are all beyond limits)

You might also want to add these aliases to your autoexec.cfg:
alias +swimuporjump "+moveup;+jump"
alias -swimuporjump "-moveup;-jump"

And bind your jump key to use +swimuporjump instead of the normal +jump command, this allows you to swim up faster (may not be desirable in some mods if for example they might make +jump do something different than you intended).

[Nash]

Thanks, Sajt and Seven. Those definitely clears things up for me.