Member
10 posts
Registered:
Feb 2007
hi ezquake admins, i'm not sure if i missed any debate on these commands (cl_sidespeed, cl_forwardspeed, cl_backspeed), but in recent ezquake builds these commands have been locked to the default value, despite being able to seemingly alter it in console. if there was debate about this that i missed could you post a link or otherwise explain why you did this? i haven't upgraded since ezquake 1517 for this reason as it fucks up my movement and i know others that haven't too. thanks!
Member
1011 posts
Registered:
Feb 2006
the values are not locked by the client
Member
231 posts
Registered:
Jan 2006
the values are not locked by the client
New client 1.8 and l8r dosnt save +speed value when using config.cfg (cfg_save only)
Member
1011 posts
Registered:
Feb 2006
DumpPlusCommand(f, &in_speed, "speed"
;
?
EDIT: oh i see you said about config.cfg, ignore this then, but that wouldn't be relevant nless he really is using legacy config - which would seem odd in this day and age! :-)
tbh, these days ezquake should do a OnStart cfg_load config and OnQuit cfg_save config, to emulate the old saving of modified values provided by config.cfg but properly retaining all settings too
Member
364 posts
Registered:
Oct 2006
There's no point in saving +speed. Go to the menus and choose "Always run" if necessary, your cl_forward/back/sidespeed will be set to 400, and that will be saved.