#415 /pak0.pak/default.cfg overrides ezquake default variables

[AAS]

See sshot.

Plain example:
Our mouse sensitivity variable is 12 (default in ezQuake) and /cfg_save_unchanged var is 0. As "/describe cfg_save_unchanged" said, sensitivity variable has not been written into config when /cfg_save executed, but when I load this config (through /cfg_load) "sensitivity" variable sets to 3, not 12.

i.e. somehow standard /id1/pak0.pak/default.cfg overrides ezquake built-in default values. May be it's time to not use default.cfg anymore or just write own default config?

ezquake 1.9.2/win32

[AAS]

bug reproduction screenshot

[biomass]

Confirmed. Possible solutions.

1. Remove default.cfg execution support which might break mods.
2. Create an ezquake default.cfg, even an empty file will prohibit the one in id1 to be executed which also might break mods.
3. Always save the variables that are in default.cfg even if they are set to default value in ezquake
4. Suggestions ?

[AAS]

First solution is to add variable to control wheter to exec default.cfg from id1 dir or not.
Second is to modify /cfg_legacy_exec variable.

Need to be very careful with all calls for default.cfg in cfg_load/cfg_reset/etc.

[JohnNy_cz]

im not able to reproduce this

[AAS]

It's still occurs on 2.1/linux

[AAS]

default.cfg moved out of the game since r4177.