I don't think you understand how the settings.scr works

[GoogleCodeExporter]

hl2:dm will not override settings.scr, it is created when a user runs the
mod and there is not one there previously. So it uses the
settings_default.scr to get all the defaults for that specific mod/game,
and throws them into the users custom settings.scr, which is then used as
long as it exists. So only the settings_default.scr should be committed
into the svn, and a custom settings.scr will be created for each user,
resulting in never having a tree conflict in the svn. As long as other
files aren't causing problems as-well of course :D Also,
settings_default.scr can be very useful if you add new binds and such.

Original issue reported on code.google.com by Bako...@gmail.com on 25 May 2010 at 11:57

[GoogleCodeExporter]

I know how settings.scr works, but the unfortunate fact is that if I don't have 
a
blank settings.scr in the distribution, then HL2:DM, as a result of .gcf 
dependency,
will actually override settings_default.scr.

I'm setting this issue to "Fixed", however the reality is that it isn't, but 
Google
doesn't have a suitable status for "Unfixable" or anything of the sort that 
implies
that we actually tried to work on it, or acknowledge this can't be addressed.

Original comment by mcwattersandrew@gmail.com on 26 May 2010 at 8:31

• Changed state: Fixed

[GoogleCodeExporter]

Additionally, to recreate the problem I'm talking about, checkout a fresh batch 
of
HL2:SB, then delete the blank settings.scr.

You'll find that once the game starts, the "Create Server" window will use the
settings_default.scr from HL2:DM. Compare with settings_default.scr in hl2sb.

Original comment by mcwattersandrew@gmail.com on 26 May 2010 at 8:33

[GoogleCodeExporter]

Original comment by mcwattersandrew@gmail.com on 29 Aug 2010 at 5:07

• Changed state: WontFix