Killing Floor Config

[JasonF]

I am starting a new thread so people don't need to sift through a million threads to get a working config. I have added a command line parameter so the user can specify their starting map.

 

I have attached my config and a SS of the working query.

 

Killing Floor.txt

[JasonF]

The game is not very resource intensive. A full 4 man server uses 0-1% of a quad core Kentsfield and 138 MB of RAM. Each game server takes up 101 MB of HDD.

[iLight]

what did you set up for the querry ? UT ?

[KingJ]

It has been set to "Unreal Tournament 2004". The reason why the other config in the other topic does not work is due to the query port being wrong - the query port should be the GameSpy port (7717) as specified correctly in JasonF's config.

[tangogc]

Sorry Jason but for me setting:

ut2004 query

server port 7707

quey port 7717

 

don't work

[KingJ]

Works for me, see the attachments as proof.

[Dan M]

Jason you're a legend! Thanks bud

[JasonF]

Sorry Jason but for me setting:

ut2004 query

server port 7707

quey port 7717

 

don't work

 

Did you update to the latest version of the game? Firewall blocking the ports?

[tangogc]

you right the port and query setting are right.

I discovered the problem, the game have mem of the port used so you can't simply change the game port you have to reinstall the game.

now all working

thanks

[iLight]

I changed the game port, it isn't have it mem

 

And now it works well, thank you =)

[R|S GoNz0]

i notice the latest update add's a query port to the ini file after 1st run, no point adding it to the config as it auto generates, even on the none default port

 

nice work on sussing it out.

[dimitrifrom31]

I am starting a new thread so people don't need to sift through a million threads to get a working config. I have added a command line parameter so the user can specify their starting map.

 

I have attached my config and a SS of the working query.

 

 

Theres a typo in your default command lines :

?VACSecure=false

 

in fact it is ?VACSecured=false and its not necessary to add that parameter in command line as it can be set in the server config file

To enable logging you can also add -log=logname.log

[R|S GoNz0]

is there any prefix to adding it to the config, or is it as above

 

VACSecured=true

 

it seems to be a bit hit and miss on my 3 servers i have running. sometimes it says enabled, sometimes it doesnt.

[dimitrifrom31]

is there any prefix to adding it to the config, or is it as above

 

VACSecured=true

 

it seems to be a bit hit and miss on my 3 servers i have running. sometimes it says enabled, sometimes it doesnt.

 

 

its by default present in the ini :

bVACSecured=False

 

about the enabled status if you monitor with HLSW it takes some time to get updated. But it definitely works fine setting it only in the config with

bVACSecured=True