questions regarding server.cfg

[gorman]

I was a bit overwhelmed about the server.cfg default settings. So much stuff in there

To those who also have an nfo l4d2 rental gameserver, I would like to ask you people, if these settings below are needed at all?

---- // originally in newmapsettings.cfg
mat_motion_blur_enabled 0
mat_grain_enable 1
mat_grain_scale_override 1.5
mat_local_contrast_enable 1
ai_no_steer 1


crosshair 1
r_flashlight_topdown 1
r_flashlightscissor 0
fx_glass_velocity_cap 600
cam_idealyaw 0
cam_idealpitch 90
cam_idealdist 412
fov_desired 75
c_maxpitch 360
c_maxdistance 1000
cl_retire_low_priority_lights 1
cl_interp_ratio 2

[kraze]

Those appear to be all client side variables and should be safe to remove.

[gorman]

Cheers.

By the way, inside my autoexec.cfg I have this here

log on
z_difficulty normal
map c5m1_waterfront


Should I delete the z_difficulty thing? And why is it there anyways in the autoexec??

[Edge100x]

The difficulty there determines the difficulty of that starting map, which is why it needs to be defined first. You can leave it in, change it, or remove it -- up to you.

We also include z_difficulty in the server.cfg, which makes it override anything that might be externally chosen. I should possibly change that.

[gorman]

Sometimes, my server launches the stuff that are inside the autoexec without my command.

Example:
Yesterday my steam friends and I were in the lobby, preparing to play. We set expert difficult and sacrifice campaign. So I launched the game, forcing connect to my server.

Once server had loaded, we ended up with normal difficult and the parish campaign. And vote to return to lobby were greyd out.

Not sure what causes this bug?

[gorman]

New update:
I deleted the entire autoexec.cfg folder and then I removed the z_difficult_normal inside the server.cfg
Hopefully this will prevent the server from starting up with a fixed difficult and fixed map.

All should still be okay, with these new changes?

I'm also getting these here in the consolelog:
Unknown command "cl_engine_reload_rosetta"
Unknown command "hud_reloadscheme"
Unknown command "cl_engine_reload_rosetta"
Unknown command "hud_reloadscheme"

[gorman]

It seems like if I delete the autoexec.cfg It just kills the server

And if I reupload the autoexec.cfg and remove the map inside it, it also kills the server.

But the map inside the autoexec.cfg is the one that causes the bug, where the server loads that map up, even tho another one have been picked in the lobby.

[Edge100x]

The autoexec.cfg is only used at server start, to load the very first map. It is necessary to load a map when starting the server. When you connect to the server with a lobby, the server automatically changes to the one that you specified in your lobby settings, overriding whatever it was already running.

[Patriot]

gorman,

Feel free to contact me if you need help configuring your L4D2 server.

Egde100x,

The difficulty there determines the difficulty of that starting map, which is why it needs to be defined first. You can leave it in, change it, or remove it -- up to you.

We also include z_difficulty in the server.cfg, which makes it override anything that might be externally chosen. I should possibly change that.

Definitely should remove z_difficulty from your default server.cfg as it will override the difficulty setting chosen in the lobby, forcing the players to call a "change difficulty" vote at the beginning of every map.

Hope all is well at NFO,

Patriot