https://wiki.tripwireinteractive.com/api.php?action=feedcontributions&user=Dweiss&feedformat=atomTripwire Interactive Wiki - User contributions [en]2024-03-28T18:02:34ZUser contributionsMediaWiki 1.40.0https://wiki.tripwireinteractive.com/index.php?title=Dedicated_Server_(Killing_Floor_2)&diff=11436Dedicated Server (Killing Floor 2)2017-06-17T03:37:09Z<p>Dweiss: /* Ports */</p>
<hr />
<div>Creating Dedicated Server (Killing Floor 2)<br />
<br />
== Downloading and Running the SteamCMD Update Tool ==<br />
<br />
# Download the SteamCMD Update Tool:<br />
#* [http://media.steampowered.com/installer/steamcmd.zip Windows Installer]<br />
# Extract the contents to a directory (Windows example: C:\SteamCmd\). <br />
#: ''Do not extract the contents of the updater tool to the regular Steam Client folder or to a folder that has the older HLDSUpdateTool program.''<br />
# Launch SteamCmd (NOTE: To automate this process for future updates, see [[#Automating SteamCmd]]).<br />
# Open a command prompt in that directory and start SteamCmd. On Windows, type '''steamcmd'''. ''The program will automatically update and enter you in to a '''Steam>''' prompt. Type '''help''' for more information.''<br />
# Log in with the username "anonymous", by typing: "login anonymous". Do ''not'' use your Steam login!<br />
# You should see a message stating that you have successfully logged in anonymously.<br />
<br />
=== Downloading the Killing Floor 2 Server ===<br />
: This describes the process of updating the KF2 dedicated server application. These steps are required every time the game is updated. To automate this process for future updates, see [[#Automating SteamCmd]].<br />
<br />
: 1. If you aren't proceeding from the previous set of instructions, first launch '''SteamCmd'''.<br />
<br />
: 2. At the '''Steam>''' prompt, set your KF2 Dedicated Server install directory. <br />
<br />
: Examples:<br />
: Absolute Path:<br />
force_install_dir c:\KF2Server\<br />
<br />
: Up one folder:<br />
force_install_dir ..\KF2Server\<br />
<br />
: In the Steam Command folder (suggested):<br />
force_install_dir .\KF2Server\<br />
<br />
: 3. Install or Update KF2.<br />
: If this is your first time installing or if you are trying to verify the integrity of the server files:<br />
app_update 232130 validate<br />
<br />
: If this is simply an update to an existing KF2 dedicated server:<br />
app_update 232130<br />
<br />
: If Tripwire is currently running a beta update of the dedicated server files:<br />
app_update 232130 -beta "branch name"<br />
Where "branch name" is the current beta branch. Currently there is not a live dedicated server beta branch.<br />
<br />
: 4. Once finished, type '''quit''' at the '''Steam>''' prompt to properly log off of the Steam servers.<br />
<br />
=== Automating SteamCmd ===<br />
<br />
There are two ways to automate SteamCmd.<br />
<br />
: 1. Add commands to the command line. Example:<br />
<br />
SteamCmd +login anonymous +force_install_dir ./kf2_ds +app_update 232130 +exit<br />
<br />
: 2. Create a script.<br />
<br />
:: a. Put your SteamCmd commands in a text file. Example:<br />
<br />
// update_kf2_ds.txt<br />
//<br />
login anonymous<br />
force_install_dir ./kf2server<br />
app_update 232130 validate<br />
exit<br />
::: ''Note: Using the validate option in your SteamCmd script will overwrite the KF2Server.bat file every time you update your server. If you edited this file for launching your server, either create a separate batch file to launch your server or remove the validate option from your SteamCmd script.''<br />
<br />
:: b. Run SteamCmd with the +runscript option. Example:<br />
SteamCmd +runscript kf2_ds.txt<br />
<br />
== Starting the Server ==<br />
<br />
Use the batch file downloaded with the server or create your own. To launch a server with default settings on Survival Biotics Lab use the following batch script:<br />
start .\Binaries\win64\kfserver kf-bioticslab<br />
<br />
=Pre-Requisites=<br />
Currently the server has several dependencies. As such we have shipped the UE3Redist.exe with the server files and it can be found in the "\Binaries\Redist" sub folder of where you have installed the server from SteamCMD. <br />
<br />
=Ports=<br />
By default the server will use the following ports:<br />
<br />
{| class="wikitable"<br />
!style="width:15%"|Port<br />
!style="width:20%"|Default<br />
!style="width:15%"|Protocol<br />
!style="width:65%"|What this option controls<br />
|-<br />
|Game Port<br />
|7777<br />
|UDP<br />
|This is the main port the game will send connections over<br />
|-<br />
|Query Port<br />
|27015<br />
|UDP<br />
|This port is used to communicate with the Steam Master Server<br />
|-<br />
|Web Admin<br />
|8080<br />
|TCP<br />
|This port is used to connect to your servers web admin page (if turned on)<br />
|-<br />
|Steam Port<br />
|20560<br />
|UDP<br />
|-<br />
|NTP Port<br />
|123<br />
|UDP<br />
|'''Weekly Outbreak Only''' - Internet time lookup to determine correct Outbreak<br />
|<br />
|}<br />
<br />
=Game Modes=<br />
By default the game will launch into the '''Survival''' coop game mode which is a 6 player game mode.<br />
<br />
<br />
===Versus Survival===<br />
Admins can have the server launch into '''Versus Survival''' competitive game mode (an up to 12 player game mode) by using the following launch script:<br />
..\Binaries\Win64\KFGame.exe Server KF-BurningParis'''?Game=KFGameContent.KFGameInfo_VersusSurvival?maxplayers=12'''<br />
<br />
To make this change in webadmin admins just need to select the game mode '''"VersusSurvival"''' from the ''Change Map'' tab.<br />
<br />
Support maps for Versus Survival at this time are:<br />
BurningParis<br />
BioticsLab<br />
Prison<br />
VoltorManor<br />
Farmhouse<br />
<br />
<br />
===Weekly Outbreaks===<br />
Admins can also launch the server into the '''Weekly Outbreaks''' coop game mode (also a 6 player game mode) by using the following launch script:<br />
..\Binaries\Win64\KFGame.exe Server KF-BurningParis'''?Game=KFGameContent.KFGameInfo_WeeklySurvival'''<br />
<br />
To make this change in webadmin admins just need to select the game mode '''"Weekly"''' from the ''Change Map'' tab.<br />
<br />
= Advanced Configuration =<br />
<br />
Configuring your new Killing Floor 2 server will be very similar to those who have set up any Unreal Engine 3 server (such as UT 3). However to those who are from other engines such as IdTech and Source there are many differences, which we'll cover here. Those who are also looking for specific sever config settings will likely find what they are looking for below.<br />
<br />
'''Please note: You will need to launch your server once for it to generate config files (based of the default config files that come with the install. It is strongly recommended you do NOT ever edit one of the default config files).'''<br />
<br />
=== Command Line Launch Options ===<br />
<br />
You can use several command line launch options to help quickly launch a server. These include url arguments attached to the command line itself (example ...bioticslab?optionhere=x?option2here=x) as well as switches which are included after the main line (example ...bioticslab -switchhere -switch2here)<br />
<br />
{| class="wikitable"<br />
!style="width:15%"|Url Arguments<br />
!style="width:20%"|Valid Entries<br />
!style="width:65%"|What this option controls<br />
|-<br />
|AdminName=<br />
|Alpha numeric character combinations. Example: Admin<br />
|This is the admin username for WebAdmin if you're configuring WebAdmin via Commandline<br />
|-<br />
|AdminPassword=<br />
|Alpha numeric character combinations. Example: Abd32Sdn53<br />
|This is the master server administrator password<br />
|-<br />
|MaxPlayers=<br />
|Alpha numeric character combinations. Example: 6<br />
|This is how many maximum players the server is set to support<br />
|-<br />
|Difficulty=<br />
|Numeric characters 0-3<br />
|This sets the server difficulty. 0 = Normal, 1 = Hard, 2 = Suicidal, 3 = Hell on Earth<br />
|}<br />
<br />
{| class="wikitable"<br />
!style="width:15%"|Switches<br />
!style="width:20%"|Valid Entries<br />
!style="width:65%"|What this option controls<br />
|-<br />
|Port=<br />
|Alpha numeric character combinations. Example: 7787<br />
|This is the game port. Changing this without changing the query port will automatically change the query port as well (up/down the same number from the default game port)<br />
|-<br />
|QueryPort=<br />
|Alpha numeric character combinations. Example: 27015<br />
|This is the query port. Changing this will change the port the server uses to communicate with Steam. Default is 27015. Change this in your launch will make it different from the automatic change that happens if you change the default port.<br />
|-<br />
|WebAdminPort=<br />
|Alpha numeric character combinations. Example: 8080<br />
|This is the web admin port. Changing this will change the port used to connect to the servers webadmin panel if that functionality is turned on. This switch is still in Beta, use at your own risk. <br />
|-<br />
|Multihome=<br />
|An IP that can resolve to the server machine. Example: 192.168.0.1<br />
|If a server machine can resolve to multiple IP's, this command can tie a server to a specific IP on that machine.<br />
|-<br />
|PREFERREDPROCESSOR=<br />
|Numeric characters. Example: 2<br />
|This will tie a server process to a single core/thread on the hosting machine.<br />
|-<br />
|ConfigSubDir=<br />
|Alpha numeric character combinations. Example: KF2Server-Normal-Long1<br />
|Creates and reads settings from a sub directory under ./KFGame/Config which allows you to configure .INI settings on a per server basis.<br />
|}<br />
<br />
=== PCServer-KFGame.ini ===<br />
<br />
''The PCServer-KFGame.ini file can be found under \KFGame\Config\''<br />
<br />
This file controls all the various game elements that can be configured by admins in Killing Floor2. From game modes to spectating options and more, everything can be set up to the admins liking from this file.<br />
<br />
First admins will want to configure this file to update the WebAdmin, server password and other settings that you do have access to. Here is an example of a very simple PCServer-KFGame.ini settings admins will want to change first:<br />
<br />
=== Server Passwords ===<br />
<br />
: [Engine.AccessControl] in PCServer-KFGame.ini:<br />
{| class="wikitable"<br />
!style="width:15%"|Option Name<br />
!style="width:20%"|Valid Entries<br />
!style="width:65%"|What this option controls<br />
|-<br />
|AdminPassword<br />
|Alpha numeric character combinations. Example: Abd32Sdn53<br />
|This is the master server administrator password<br />
|-<br />
|GamePassword<br />
|Alpha numeric character combinations. Example: cl4ng4m3<br />
|This sets a password players will need to enter to join the server<br />
|}<br />
<br />
=== Server Name and Admin Contact ===<br />
: [Engine.GameReplicationInfo] in PCServer-KFGame.ini:<br />
{| class="wikitable"<br />
!style="width:15%"|Option Name<br />
!style="width:20%"|Valid Entries<br />
!style="width:65%"|What this option controls<br />
|-<br />
|ServerName<br />
|Alpha numeric character combinations. Example: Yoshi's House of 32 Compressed Pancakes<br />
|This is the displayed server name to all players in the server and the server browser<br />
|-<br />
|AdminContact<br />
|Alpha numeric character combinations. Example: testemail@testemail.com<br />
|This is the displayed admin contact in the server browser<br />
|}<br />
<br />
<br />
<br />
==== Maps ====<br />
<br />
bUseMapList=True - This sets the server to use a custom map list you specify instead of the entire default map list.<br />
GameLength=1 - This sets the number of rounds per game. 0 -> {short, 4 rounds} 1 -> {normal, 7 rounds} 2 -> {long, 10 rounds}<br />
<br />
Maps can be set to run by gametype and amount of rounds played. The following is an example map list that can be put in your PCServer-KFGame.ini:<br />
<br />
{| class="wikitable"<br />
!style="width:100%"|Game Map Cycle<br />
|-<br />
|GameMapCycles=(Maps=("KF-BurningParis","KF-Bioticslab","KF-Outpost","KF-VolterManor","KF-Catacombs","KF-EvacuationPoint"))<br />
|}<br />
<br />
The first part specifies the exact maps and their game types.<br />
<br />
=== PCServer-KFEngine.ini ===<br />
<br />
The Engine.ini is where most port related changes can be made to a server, including the game port and query port.<br />
<br />
NetServerMaxTickRate - This setting changes the server tickrate. The default is 30.<br />
<br />
= Setting Up Web Admin =<br />
<br />
To enable webadmin:<br />
Open KFWeb.ini. In the [IpDrv.WebServer] section set<br />
bEnabled=true<br />
<br />
By default webadmin will listen on port 8080 on the IP of the game server using, but you'll want to customize this port for multiple servers on the same IP. To change this, open KFweb.ini and modify the following line:<br />
ListenPort=8080<br />
<br />
Admins will now be able to log into their servers web admin panel. They can do by either connecting via a local address (if the server is local) or web address (the servers IP) followed by the port. They can use any of their favorite modern internet browsers such as Chrome, Firefox, and IE. An example of what to put in the address bar of the browser is:<br />
192.168.0.100:8080<br />
<br />
They will be presented with a login screen. The default user is: Admin. The password will be whatever was set as the admin pass in PCServer-KFGame.ini. If no admin pass was set, the admin will not be able to log in.<br />
<br />
<br />
<br />
== Setting up multiple web admins ==<br />
<br />
Open KFWebAdmin.ini and add the following under [WebAdmin.WebAdmin]:<br />
AuthenticationClass=WebAdmin.MultiWebAdminAuth<br />
<br />
Start the server once to generate a new MultiAdmin.ini. Now you can either add new admin names and passwords from within the Web Admin itself, or you can add them manually in the file. To do so add the following information for each admin under [Admin MultiAdminData] in MultiAdmin.ini<br />
DisplayName= "AdminNameHere" // Punctuation does matter for these names<br />
Password= "123" // Any alpha numeric set of characters will work here<br />
Order= "DenyAllow"<br />
bEnabled= "True" // This enables this admin<br />
<br />
== How To Use Web Admin ==<br />
Go to [[Web_Admin|web admin]] to find out more details on how to use the system.<br />
<br />
== Setting Up Steam Workshop For Servers ==<br />
<br />
'''Configuring the server to download files from Workshop:'''<br />
<br />
# Make sure that the server is not running. If it is running, the Workshop setup will be overridden the next time you restart the server.<br />
# Add a new section to the PCServer-KFEngine.ini config file: [OnlineSubsystemSteamworks.KFWorkshopSteamworks]<br />
# For each Workshop item you want the server to download, add a ServerSubscribedWorkshopItems=<number> line in that section. You can find the number by looking for the id= part of the the URL of the Workshop item in Steam. For example, the URL of the Workshop Test map is http://steamcommunity.com/sharedfiles/filedetails/?id=535769647, so the line will be "ServerSubscribedWorkshopItems=535769647". There might be other text=number parts of the URL, so be sure to use only the number after "id=".<br />
<br />
Example [OnlineSubsystemSteamworks.KFWorkshopSteamworks] section (These ID's are for Grindhouse Contest Maps):<br />
<br />
[OnlineSubsystemSteamworks.KFWorkshopSteamworks]<br />
ServerSubscribedWorkshopItems=605633924<br />
ServerSubscribedWorkshopItems=605551918<br />
ServerSubscribedWorkshopItems=605549089<br />
ServerSubscribedWorkshopItems=605532351<br />
<br />
<br />
'''Make clients download the Workshop item from Steam when connecting to the server:'''<br />
<br />
This will only work for Workshop items that the server downloads itself, that are listed in the [OnlineSubsystemSteamworks.KFWorkshopSteamworks] section as described above.<br />
<br />
# Make sure that the server is not running. If it is running, the Workshop setup will be overridden the next time you restart the server.<br />
# Find the section [IpDrv.TcpNetDriver] in the PCServer-KFEngine.ini config file.<br />
# Add the line "DownloadManagers=OnlineSubsystemSteamworks.SteamWorkshopDownload" to that section. If there are other "DownloadManagers=" lines, make sure this one is the first.<br />
# Do not delete anything from this section, except (optionally) other DownloadManagers= lines.<br />
<br />
<br />
'''Steam Workshop map location in server and map names'''<br />
<br />
Start the server and wait it to download Steam Workshop maps you added earlier. <br />
This can take several minutes. <br />
After server has downloaded all the maps stop the server and make sure that it is not running.<br />
<br />
Navigate into server install location and go into folder KFGame\Cache\XXX\0\BrewedPC where XXX is one of the ServerSubscribedWorkshopItems you added earlier. For example (KF-BikiniAtoll):<br />
KFGame\Cache\643383080\0\BrewedPC<br />
Copy paste the map file name (excluding the .kfm extension).<br />
<br />
See [[#Maps]] and [[#Get Custom Maps To Show In Web Admin]] where you can paste it.<br />
<br />
<br />
== Setting Up Redirect - Depreciated by SteamWorkshop ==<br />
<br />
To enable redirect for third party custom maps to be able to run on their server, admins needs to install the "cooked server" files in their "\KFGame\BrewedPC" directory on the dedicated server.<br />
<br />
Now unless users already have the cooked client map files installed manually or previously downloaded in their clients cache, the server will need to be set up to redirect clients without the map to download it from a redirect server. To enable this, the admin must open the PCServer-KFEngine.ini file and add a new section near the bottom of the file. The section is called [IpDrv.HTTPDownload] and should look like this:<br />
<br />
[IpDrv.HTTPDownload]<br />
RedirectToURL=http://kf2.tripwirecdn.com/<br />
<br />
Where the RedirectToURL is a web location that is a repository of the client map files. The example above is the location of Tripwire's public redirect server which will host several near complete and complete custom maps. The client map file must be named as a .kfm file.<br />
<br />
<br />
For Windows Server users if you use IIS for the redirect please make sure to go to Server Manager and check that you have Anonymous Authentication or Basic Authentication enabled. Next be sure that the File Extension .kfm is added to the list in MIME Types. You will see two fields when you add a new MIME Type, File name extension and MIME type. Here is an example on how it should look<br />
<br />
http://i.imgur.com/hGsJuId.png (Can't find out how to embed the image so here is the link)<br />
<br />
=== Get Custom Maps To Show In Web Admin ===<br />
To get custom maps to show up in the change level section of web admin, admins will need to add a data store for the game in PCServer-KFGame.ini. A data store looks like the following example:<br />
<br />
<pre><br />
[KF-Default KFMapSummary]<br />
MapName=KF-Default<br />
ScreenshotPathName=UI_MapPreview_TEX.UI_MapPreview_Placeholder<br />
</pre><br />
<br />
Please note the use of lowercase in the map name and read the Known Issues to Avoid section for more information on the topic. This holds true for the mapcycle as well.<br />
<br />
=== Known Issues to Avoid ===<br />
<br />
* Linux Redirect<br />
As a redirect server can be a Linux machine, it is very important admins have the closing forward slash in the URL as well as spell all map names in lowercase. Failure to do so will result in a broken redirect and clients will only obtain a 1kb file of the proper name but not the actual files. Also take care when adding the map data store to the PCServer-KFGame.ini to use lowercase as well as the server will use those file names over any typed in as an admin.<br />
<br />
* Traveling from a custom map to a custom map<br />
When a server goes from a custom map to a custom map, clients will download the second custom map, however there is a bug where the client will just see the "connecting" screen without any updated information about downloading the custom map until it is downloaded and begins to load.<br />
<br />
A redirect server needs fast speeds and as much bandwidth as possible, but little else.<br />
<br />
= Setting Up Server Welcome Screen =<br />
<br />
# Make sure the game server isn't running<br />
# Edit PCServer-KFGame.ini:<br />
<br />
Find this part and edit it, here is the default one<br />
<br />
Code:<br />
BannerLink=http://art.tripwirecdn.com/TestItemIcons/MOTDServer.png<br />
ServerMOTD=Welcome to our server. \n \n Have fun and good luck!<br />
WebsiteLink=http://killingfloor2.com/<br />
<br />
# BannerLink should be a PNG (save it > 8bit) image<br />
# ServerMOTD is the message display under the BannerLink image. You can usesome "\n" to create a new line like in the default message, I personally add two lines before my MOTD message to add space between image and text<br />
# WebsiteLink is the url of your website (if you edit this from the webadmin, it resets to a blank value after saving)<br />
# Save, start the server, enjoy you welcome screen.<br />
<br />
<br />
= Server Takeover =<br />
== What it is ==<br />
Server Takeover is a feature that allows players who are matchmaking and choosing to start their own private game to "grab" a server that has not opted out for them to use during their play time. This will change the settings on the server to those that the players want and make it private. However it will not expose any of the private information about that server (such as admin passwords) to them. At the end of their stay in the server, the server will open back up again and await new players or another takeover request.<br />
<br />
== How to opt out ==<br />
To remove your server from the take over list you can use this line in the KFEngine.ini:<br />
<br />
[Engine.GameEngine]<br />
bUsedForTakeover=FALSE</div>Dweisshttps://wiki.tripwireinteractive.com/index.php?title=Dedicated_Server_(KillingFloor)&diff=11435Dedicated Server (KillingFloor)2017-06-17T03:35:56Z<p>Dweiss: Wrong page, my searching skills are bad.</p>
<hr />
<div>== About ==<br />
<br />
[http://developer.valvesoftware.com/wiki/SteamCMD ''SteamCMD Update Tool''] is a new method of updating game servers under Steam. All games are gradually switching to this method.<br />
<br />
{{quote|style="margin:10px; border: 1px dashed grey"||text=There is some misunderstanding of the new steamcmd update tool happening here, let me just clear things up:<br/><br />
<br/><br />
* steamcmd is used for updating of dedicated servers using the new Steam Pipe content system, newly released games on Steam use this system and older games are being switched over.<br/><br />
* Currently steamcmd requires a steam login to perform an update, we plan on adding a no-login mode in the future for free to download titles.<br/><br />
* The login you use for steamcmd just needs rights to the game you are updating, so for the majority of dedicated server applications you CAN use a free account. So you could currently make an account per machine you wish to run the tool on. You do NOT need to buy the full game client to update if the dedicated server is free.<br/><br />
* CS:GO is a special case because it is in closed beta, access to its dedicated server is limited to blessed accounts which is why you need a special login. If you are having problems running CS:GO servers and are in the beta email the team and ask for access to another account for your dedicated servers.<br/><br />
<br/><br />
With Steam Pipe you should see an improvement in download speeds and more robust response during high demand. It uses HTTP as the content delivery method, so you could set up a local HTTP proxy to cache all steamcmd requests, making updates from multiple machines stay on your local network.|source=Alfred, Valve}}<br />
<br />
==Windows==<br />
<br />
===Installing SteamCmd ===<br />
<br />
# Go to https://store.steampowered.com/join/ and make new Steam account - no need for any games on it, this account will be needed later. <br />
# Download the SteamCMD Update Tool - [http://blog.counter-strike.net/wp-content/uploads//2012/04/steamcmd.zip Windows Installer] ''(MD5: 1aa2b3206b9626f20dface42b9bcf7f0)'' to the destination directory, for example c:\SteamCmd.<p><br />
# Unpack it.{{note|Do not extract the contents of the updater tool to the regular Steam Client folder or to a folder that has the older HLDSUpdateTool program.}}</p><br />
# Run command prompt (start->run->[http://en.wikipedia.org/wiki/Command_Prompt cmd]).<br />
# Change to the install directory:<br/><blockquote><code>cd /d c:\SteamCmd</code></blockquote><br />
# Run steamcmd to update itself:<br/><blockquote><code>steamcmd</code></blockquote><p>{{note|If you have a Steam running on the same machine you want to install server, then first of all close and exit Steam - you will avoid errors with SteamCmd thinking that another copy of Steam is already running.}}</p><p>{{note|Make sure you have "automatically detect settings" selected in the network options tab of Internet Explorer, else you may receive an error stating that you can't connect.}}</p><p>You can see extra info by using the ''help'' command:<br/><blockquote><code>help</code></blockquote>Notice that you are in Steam prompt, since there is ''Steam>'' in front of the line.<br/><br/><br />
# Log in with your Steam account created at the beginning:<br/><blockquote><code>login <username> <password></code></blockquote>You should see something like this on successful login<br/><blockquote>''Logging in user <username> to Steam Public...Success.''</blockquote><br />
# If you receive a Steam Guard error, check your e-mail for your access code and execute the following commands (you'll only need to do this once):<br/><blockquote><code>set_steam_guard_code yourcodehere<br/>login <username> <password></code></blockquote><br />
<br />
{{troubleshoot begin}}<br />
* I am getting the following error when I run <code>steamcmd</code>:<br/><blockquote><code>SteamUpdater: Error: Steam needs to be online to update. Please confirm your network connection and try again.<br/>[ 0%] !!! Fatal Error: Steam needs to be online to update. Please confirm your network connection and try again.</code></blockquote>'''Solution''': Make sure you have "automatically detect settings" selected in the network options tab of Internet Explorer.<br />
{{troubleshoot end}}<br />
<br />
===Installing KillingFloor server===<br />
<br />
# For now it is assumed that your game server will be in c:\KFServer\ (more about it in [[#Installation paths]]). You must tell SteamCmd to force install the game in that directory:<br/><blockquote><code>force_install_dir c:\KFServer\</code></blockquote><br />
# Install game server. If you selected the directory that already contains the game, it will be updated:<br/><blockquote><code>app_update 215350 validate</code></blockquote>{{note|You must turn off the server before trying to update, otherwise it will fail.}}You should see progress of game server installation or update.<br/><br/><br />
# Once finished, type '''quit''' at the '''Steam>''' prompt to properly log off of the Steam servers.<br/><br />
<br/><br />
Now you may turn on the server.<br />
<br />
{{troubleshoot begin}}<br />
* I am getting the following error when I run <code>app_update</code><br/><blockquote><code>ERROR! Failed to request AppInfo update, not online or not logged into Steam</code></blockquote>'''Solution''': Remove the Steam folder from root directory (rd /s c:\Steam).<br />
{{troubleshoot end}}<br />
<br />
===Automation===<br />
<br />
There are two ways to automate SteamCmd:<br />
<br />
* Via direct use of command prompt<br />
* Via use of a script<br />
<br />
====Command prompt====<br />
<br />
Simply enter the commands directly into command prompt, for example:<br />
<br />
<blockquote><code>SteamCmd +login user password +force_install_dir c:\KFServer\ +app_update 215350 validate</code></blockquote><br />
<br />
This will first login to Steam and try to update game server.<br />
<br />
====Using a script====<br />
<br />
Alternately, you can create a script that will perform a series of actions:<br />
<br />
<blockquote><code><br />
// update_kf_ds.txt<br/><br />
//<br/><br />
login user password<br/><br />
force_install_dir c:\KFServer\<br/><br />
app_update 215350 validate<br/><br />
exit</code></blockquote><br />
<br />
Now you can issue SteamCmd to execute the script:<br />
<br />
<blockquote><code>SteamCmd +runscript C:\SteamCmd\update_kf_ds.txt</code></blockquote><br />
<br />
Place the script anywhere you want, just make sure to update the paths when invoking ''SteamCmd +runscript''.<br />
<br />
==Linux==<br />
<br />
===Installing SteamCmd ===<br />
<br />
# Go to https://store.steampowered.com/join/ and make new Steam account - no need for any games on it, this account will be needed later.<br />
# Create installation directory for SteamCmd, example ''home/unreal/steamcmd'':<br/><blockquote><code>mkdir -p /home/unreal/steamcmd<br/>cd /home/unreal/steamcmd</code/></blockquote><br />
# Download the SteamCMD Update Tool - [http://blog.counter-strike.net/wp-content/uploads//2012/04/steamcmd.tar.gz Linux Installer] ''(MD5: b803e6adc6dd051039cbbfdd846d804d)''.<br />
# Unpack it.<br/><blockquote><code>tar zxf steamcmd.tar.gz</code></blockquote><br />
# Run the shell script:<blockquote><code>./steam.sh</code></blockquote>This should make the ~/Steam directory and update the Steam framework.<br/>You can see extra info by using the ''help'' command:<br/><blockquote><code>help</code></blockquote>Notice that you are in Steam prompt, since there is ''Steam>'' in front of the line.<br/><br/><br />
# Log in with your Steam account created at the beginning:<br/><blockquote><code>login <username> <password></code></blockquote>You should see something like this on successful login<br/><blockquote>''Logging in user <username> to Steam Public...Success.''</blockquote><br />
# If you receive a Steam Guard error, check your e-mail for your access code and execute the following commands (you'll only need to do this once):<br/><blockquote><code>set_steam_guard_code yourcodehere<br/>login <username> <password></code></blockquote><br />
<br />
{{troubleshoot begin}}<br />
* On certain Linux distributions you will see error message that something cannot be found etc.<br/><br/>'''Solution''': Try this instead:<br/><blockquote><code>STEAMEXE=steamcmd ./steam.sh</code></blockquote>If this still fails try:<br/><blockquote><code>export LD_LIBRARY_PATH=/home/unreal/steamcmd/linux32/<br/>STEAMEXE=steamcmd ./steam.sh</code></blockquote><br />
* On 64-bit systems you may get the following error:<br/><blockquote><code>steamcmd: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory</code></blockquote>'''Solution''': Install lib32stdc++6:<br />
**Debian-based systems:<blockquote><code>apt-get install lib32stdc++6</code></blockquote><br />
**Red Hat-based systems:<blockquote><code>yum install libstdc++ libstdc++-4.4.6-4.el6.i686</code></blockquote><br />
<br />
{{troubleshoot end}}<br />
<br />
===Installing KillingFloor server===<br />
<br />
# For now it is assumed that your game server will be in /home/unreal/killingfloor (more about it in [[#Installation paths]]). You must tell SteamCmd to force install the game in that directory:<br/><blockquote><code>force_install_dir /home/unreal/killingfloor</code></blockquote><br />
# Install game server. If you selected the directory that already contains the game, it will be updated:<br/><blockquote><code>app_update 215360 validate</code></blockquote>{{note|You must turn off the server before trying to update, otherwise it will fail.}}You should see progress of game server installation or update.<br/><br/><br />
# Once finished, type '''quit''' at the '''Steam>''' prompt to properly log off of the Steam servers.<br/><br />
<br/><br />
Now you may turn on the server.<br />
<br />
{{troubleshoot begin}}<br />
* I am getting the following error when I run <code>app_update</code><br/><blockquote><code>ERROR! Failed to request AppInfo update, not online or not logged into Steam</code></blockquote>'''Solution''': Remove the Steam folder from root directory (rm -rf ~/Steam).<br />
{{troubleshoot end}}<br />
<br />
===Automation===<br />
<br />
There are two ways to automate SteamCmd:<br />
<br />
* Via direct use of command prompt<br />
* Via use of a script<br />
<br />
====Command prompt====<br />
<br />
Simply enter the commands directly into command prompt, for example:<br />
<br />
<blockquote><code>SteamCmd +login user password +force_install_dir /home/unreal/killingfloor +app_update 215360 validate</code></blockquote><br />
<br />
This will first login to Steam and try to update game server.<br />
<br />
====Using a script====<br />
<br />
Alternately, you can create a script that will perform a series of actions:<br />
<br />
<blockquote><code><br />
// update_kf_ds.txt<br/><br />
//<br/><br />
login user password<br/><br />
force_install_dir /home/unreal/killingfloor<br/><br />
app_update 215360 validate<br/><br />
exit</code></blockquote><br />
<br />
Now you can issue SteamCmd to execute the script:<br />
<br />
<blockquote><code>SteamCmd +runscript /home/unreal/killingfloor/update_kf_ds.txt</code></blockquote><br />
<br />
Place the script anywhere you want, just make sure to update the paths when invoking ''SteamCmd +runscript''.<br />
<br />
{{troubleshoot begin}}<br />
* I am getting errors.<br/><br/>'''Solution''': On some Linux distribution you may recieve errors with not loading some .so files, so try this (alter paths):<blockquote><code>#!/bin/bash<br/>DIR=/home/unreal/steamcmd<br/>export LD_LIBRARY_PATH="${DIR}/linux32:$LD_LIBRARY_PATH"<br/>cd ${DIR}/linux32<br/>./steamcmd +runscript ${DIR}/update_kf_ds.txt</code></blockquote><br />
{{troubleshoot end}}<br />
<br />
==Installation paths==<br />
<br />
You can specify installation directory in various ways:<br />
<br />
===Windows===<br />
<br />
* Absolute Path:<br />
<blockquote><code>force_install_dir c:\KFServer\</code></blockquote><br />
<br />
* Up one folder:<br />
<blockquote><code>force_install_dir ..\KFServer\</code></blockquote><br />
<br />
* In the Steam Command folder:<br />
<blockquote><code>force_install_dir .\KFServer\</code></blockquote><br />
<br />
===Linux===<br />
<br />
* Absolute Path:<br />
<blockquote><code>force_install_dir /home/unreal/killingfloor/</code></blockquote><br />
<br />
* Up one folder:<br />
<blockquote><code>force_install_dir ../killingfloor/</code></blockquote><br />
<br />
* In the Steam Command folder:<br />
<blockquote><code>force_install_dir ./killingfloor/</code></blockquote><br />
<br />
==Beta versions==<br />
<br />
If Tripwire is currently running a beta update of the dedicated server files:<br />
<blockquote><code>app_update 215350 -beta "branch name"</code></blockquote><br />
Where "branch name" is the current beta branch. Currently there is not a live dedicated server beta branch.<br />
<br />
== Starting the server ==<br />
<br />
Use the batch file downloaded with the server or create your own. To launch a server with default settings on BioticsLab use the following batch script:<br />
<br />
Windows<br />
<blockquote><code>ucc server KF-bioticslab.rom?game=KFmod.KFGameType?VACSecured=true?MaxPlayers=6</code></blockquote><br />
<br />
Linux<br />
<blockquote><code>./ucc-bin server KF-bioticslab.rom?game=KFmod.KFGameType?VACSecured=true?MaxPlayers=6 -nohomedir</code></blockquote><br />
<br />
==Server ports==<br />
<br />
The following list of ports need to be open for a server to run successfully:<br />
* 7707 UDP/IP (Game Port)<br />
* 7708 UDP/IP (Query Port)<br />
* 7717 UDP/IP (GameSpy Query Port)<br />
* 28852 TCP/IP and UDP (Allows your Server to Connect to the Master Server Browser)<br />
* 8075 TCP/IP (Port set via ListenPort that your WebAdmin will run on)<br />
* 20560 UDP/IP (Steam Port)<br />
<br />
Since the game is running with the Steam backend, if you are running more than 1 server per IP, you will need to make sure that you have some additional ports open beyond the default KF ports. If you change the default Game Port from 7707, this change will be reflected in the Master Server Port (28852) and the Steam Port (20560) as well.<br />
<br />
You must also change OldQueryPortNumber=7717 under [IpDrv.UdpGamespyQuery] in the KillingFloor.ini to match the increase of the 7707 port. So if you change 7707 to 7807, then 7717 would change to 7817. If this is not done, the server will crash when starting.<br />
<br />
==Advanced admin settings==<br />
<br />
Admins looking to made changes from the default settings will find most options available in the Killingfloor.ini (or in WebAdmin once enabled in the Killingfloor.ini).<br />
<br />
===Server name and passwords===<br />
<br />
<blockquote><code>ServerName=Killing Floor Server<br/><br />
GamePassword=<br/><br />
Adminpassword=</code></blockquote><br />
<br />
===Difficulty and Length===<br />
<br />
<blockquote><code>GameDifficulty=</code></blockquote><br />
<br />
Valid inputs:<br />
* 1.0 = Beginner - Your grandma can play the game<br />
* 2.0 = Normal - Quite challenging with lower level perks<br />
* 4.0 = Hard - Very challenging even with mid level perks<br />
* 5.0 = Suicidal - Incredibly difficult, even with high level perks<br />
* 7.0 = Hell on Earth - You'll be wishing you were one of them<br />
<br />
<blockquote><code>KFGameLength=</code></blockquote><br />
<br />
Valid inputs:<br />
* 0 = Short - A 4 wave game<br />
* 1 = Normal - The standard 7 wave game<br />
* 2 = Long - The longer 10 wave game<br />
* 3 = Custom - uses the custom sandbox settings for waves, monster counts, etc (which i won't go into here, but we'll talk about in another post). <br />
<br />
===Map voting===<br />
In the [xVoting.XvotingHandler] section of the killingfloor.ini admins need to set ''bMapVote'' to ''true'' in order to enable map voting.<br />
<br />
Admins can can also configure how soon a map can be re-voted for with ''RepeatLimit''. The numerical value determined the number of previously played maps that should not be selectable. 0 - Map can be voted for right away. 4(Default) - Four maps must be played before the map becomes available again.<br />
<br />
===WebAdmin===<br />
To enable WebAdmin, admins need to locate the [UWeb.WebServer] section of the Killingfloor.ini and set ''bEnable'' to ''true''.<br />
<br />
The default webadmin port is 8075 and once enabled Admins can log into it by navigating to <br />
<br />
<blockquote><code>YOUR_SERVER_IP:8075</code></blockquote><br />
<br />
in their favorite web browser and logging in with the admin name (default: admin if not set) and password.<br />
<br />
===In-game admin===<br />
When you're in game press your ~ key to open the command console and type:<br />
<br />
<blockquote><code>adminlogin <yourpassword></code></blockquote><br />
<br />
This will log you in as admin and will give you access to admin commands such as ''map'', ''kick'', and ''ban''.<br />
<br />
[[Category:Killing Floor]]</div>Dweisshttps://wiki.tripwireinteractive.com/index.php?title=Dedicated_Server_(KillingFloor)&diff=11434Dedicated Server (KillingFloor)2017-06-17T03:33:25Z<p>Dweiss: /* Server ports */</p>
<hr />
<div>== About ==<br />
<br />
[http://developer.valvesoftware.com/wiki/SteamCMD ''SteamCMD Update Tool''] is a new method of updating game servers under Steam. All games are gradually switching to this method.<br />
<br />
{{quote|style="margin:10px; border: 1px dashed grey"||text=There is some misunderstanding of the new steamcmd update tool happening here, let me just clear things up:<br/><br />
<br/><br />
* steamcmd is used for updating of dedicated servers using the new Steam Pipe content system, newly released games on Steam use this system and older games are being switched over.<br/><br />
* Currently steamcmd requires a steam login to perform an update, we plan on adding a no-login mode in the future for free to download titles.<br/><br />
* The login you use for steamcmd just needs rights to the game you are updating, so for the majority of dedicated server applications you CAN use a free account. So you could currently make an account per machine you wish to run the tool on. You do NOT need to buy the full game client to update if the dedicated server is free.<br/><br />
* CS:GO is a special case because it is in closed beta, access to its dedicated server is limited to blessed accounts which is why you need a special login. If you are having problems running CS:GO servers and are in the beta email the team and ask for access to another account for your dedicated servers.<br/><br />
<br/><br />
With Steam Pipe you should see an improvement in download speeds and more robust response during high demand. It uses HTTP as the content delivery method, so you could set up a local HTTP proxy to cache all steamcmd requests, making updates from multiple machines stay on your local network.|source=Alfred, Valve}}<br />
<br />
==Windows==<br />
<br />
===Installing SteamCmd ===<br />
<br />
# Go to https://store.steampowered.com/join/ and make new Steam account - no need for any games on it, this account will be needed later. <br />
# Download the SteamCMD Update Tool - [http://blog.counter-strike.net/wp-content/uploads//2012/04/steamcmd.zip Windows Installer] ''(MD5: 1aa2b3206b9626f20dface42b9bcf7f0)'' to the destination directory, for example c:\SteamCmd.<p><br />
# Unpack it.{{note|Do not extract the contents of the updater tool to the regular Steam Client folder or to a folder that has the older HLDSUpdateTool program.}}</p><br />
# Run command prompt (start->run->[http://en.wikipedia.org/wiki/Command_Prompt cmd]).<br />
# Change to the install directory:<br/><blockquote><code>cd /d c:\SteamCmd</code></blockquote><br />
# Run steamcmd to update itself:<br/><blockquote><code>steamcmd</code></blockquote><p>{{note|If you have a Steam running on the same machine you want to install server, then first of all close and exit Steam - you will avoid errors with SteamCmd thinking that another copy of Steam is already running.}}</p><p>{{note|Make sure you have "automatically detect settings" selected in the network options tab of Internet Explorer, else you may receive an error stating that you can't connect.}}</p><p>You can see extra info by using the ''help'' command:<br/><blockquote><code>help</code></blockquote>Notice that you are in Steam prompt, since there is ''Steam>'' in front of the line.<br/><br/><br />
# Log in with your Steam account created at the beginning:<br/><blockquote><code>login <username> <password></code></blockquote>You should see something like this on successful login<br/><blockquote>''Logging in user <username> to Steam Public...Success.''</blockquote><br />
# If you receive a Steam Guard error, check your e-mail for your access code and execute the following commands (you'll only need to do this once):<br/><blockquote><code>set_steam_guard_code yourcodehere<br/>login <username> <password></code></blockquote><br />
<br />
{{troubleshoot begin}}<br />
* I am getting the following error when I run <code>steamcmd</code>:<br/><blockquote><code>SteamUpdater: Error: Steam needs to be online to update. Please confirm your network connection and try again.<br/>[ 0%] !!! Fatal Error: Steam needs to be online to update. Please confirm your network connection and try again.</code></blockquote>'''Solution''': Make sure you have "automatically detect settings" selected in the network options tab of Internet Explorer.<br />
{{troubleshoot end}}<br />
<br />
===Installing KillingFloor server===<br />
<br />
# For now it is assumed that your game server will be in c:\KFServer\ (more about it in [[#Installation paths]]). You must tell SteamCmd to force install the game in that directory:<br/><blockquote><code>force_install_dir c:\KFServer\</code></blockquote><br />
# Install game server. If you selected the directory that already contains the game, it will be updated:<br/><blockquote><code>app_update 215350 validate</code></blockquote>{{note|You must turn off the server before trying to update, otherwise it will fail.}}You should see progress of game server installation or update.<br/><br/><br />
# Once finished, type '''quit''' at the '''Steam>''' prompt to properly log off of the Steam servers.<br/><br />
<br/><br />
Now you may turn on the server.<br />
<br />
{{troubleshoot begin}}<br />
* I am getting the following error when I run <code>app_update</code><br/><blockquote><code>ERROR! Failed to request AppInfo update, not online or not logged into Steam</code></blockquote>'''Solution''': Remove the Steam folder from root directory (rd /s c:\Steam).<br />
{{troubleshoot end}}<br />
<br />
===Automation===<br />
<br />
There are two ways to automate SteamCmd:<br />
<br />
* Via direct use of command prompt<br />
* Via use of a script<br />
<br />
====Command prompt====<br />
<br />
Simply enter the commands directly into command prompt, for example:<br />
<br />
<blockquote><code>SteamCmd +login user password +force_install_dir c:\KFServer\ +app_update 215350 validate</code></blockquote><br />
<br />
This will first login to Steam and try to update game server.<br />
<br />
====Using a script====<br />
<br />
Alternately, you can create a script that will perform a series of actions:<br />
<br />
<blockquote><code><br />
// update_kf_ds.txt<br/><br />
//<br/><br />
login user password<br/><br />
force_install_dir c:\KFServer\<br/><br />
app_update 215350 validate<br/><br />
exit</code></blockquote><br />
<br />
Now you can issue SteamCmd to execute the script:<br />
<br />
<blockquote><code>SteamCmd +runscript C:\SteamCmd\update_kf_ds.txt</code></blockquote><br />
<br />
Place the script anywhere you want, just make sure to update the paths when invoking ''SteamCmd +runscript''.<br />
<br />
==Linux==<br />
<br />
===Installing SteamCmd ===<br />
<br />
# Go to https://store.steampowered.com/join/ and make new Steam account - no need for any games on it, this account will be needed later.<br />
# Create installation directory for SteamCmd, example ''home/unreal/steamcmd'':<br/><blockquote><code>mkdir -p /home/unreal/steamcmd<br/>cd /home/unreal/steamcmd</code/></blockquote><br />
# Download the SteamCMD Update Tool - [http://blog.counter-strike.net/wp-content/uploads//2012/04/steamcmd.tar.gz Linux Installer] ''(MD5: b803e6adc6dd051039cbbfdd846d804d)''.<br />
# Unpack it.<br/><blockquote><code>tar zxf steamcmd.tar.gz</code></blockquote><br />
# Run the shell script:<blockquote><code>./steam.sh</code></blockquote>This should make the ~/Steam directory and update the Steam framework.<br/>You can see extra info by using the ''help'' command:<br/><blockquote><code>help</code></blockquote>Notice that you are in Steam prompt, since there is ''Steam>'' in front of the line.<br/><br/><br />
# Log in with your Steam account created at the beginning:<br/><blockquote><code>login <username> <password></code></blockquote>You should see something like this on successful login<br/><blockquote>''Logging in user <username> to Steam Public...Success.''</blockquote><br />
# If you receive a Steam Guard error, check your e-mail for your access code and execute the following commands (you'll only need to do this once):<br/><blockquote><code>set_steam_guard_code yourcodehere<br/>login <username> <password></code></blockquote><br />
<br />
{{troubleshoot begin}}<br />
* On certain Linux distributions you will see error message that something cannot be found etc.<br/><br/>'''Solution''': Try this instead:<br/><blockquote><code>STEAMEXE=steamcmd ./steam.sh</code></blockquote>If this still fails try:<br/><blockquote><code>export LD_LIBRARY_PATH=/home/unreal/steamcmd/linux32/<br/>STEAMEXE=steamcmd ./steam.sh</code></blockquote><br />
* On 64-bit systems you may get the following error:<br/><blockquote><code>steamcmd: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory</code></blockquote>'''Solution''': Install lib32stdc++6:<br />
**Debian-based systems:<blockquote><code>apt-get install lib32stdc++6</code></blockquote><br />
**Red Hat-based systems:<blockquote><code>yum install libstdc++ libstdc++-4.4.6-4.el6.i686</code></blockquote><br />
<br />
{{troubleshoot end}}<br />
<br />
===Installing KillingFloor server===<br />
<br />
# For now it is assumed that your game server will be in /home/unreal/killingfloor (more about it in [[#Installation paths]]). You must tell SteamCmd to force install the game in that directory:<br/><blockquote><code>force_install_dir /home/unreal/killingfloor</code></blockquote><br />
# Install game server. If you selected the directory that already contains the game, it will be updated:<br/><blockquote><code>app_update 215360 validate</code></blockquote>{{note|You must turn off the server before trying to update, otherwise it will fail.}}You should see progress of game server installation or update.<br/><br/><br />
# Once finished, type '''quit''' at the '''Steam>''' prompt to properly log off of the Steam servers.<br/><br />
<br/><br />
Now you may turn on the server.<br />
<br />
{{troubleshoot begin}}<br />
* I am getting the following error when I run <code>app_update</code><br/><blockquote><code>ERROR! Failed to request AppInfo update, not online or not logged into Steam</code></blockquote>'''Solution''': Remove the Steam folder from root directory (rm -rf ~/Steam).<br />
{{troubleshoot end}}<br />
<br />
===Automation===<br />
<br />
There are two ways to automate SteamCmd:<br />
<br />
* Via direct use of command prompt<br />
* Via use of a script<br />
<br />
====Command prompt====<br />
<br />
Simply enter the commands directly into command prompt, for example:<br />
<br />
<blockquote><code>SteamCmd +login user password +force_install_dir /home/unreal/killingfloor +app_update 215360 validate</code></blockquote><br />
<br />
This will first login to Steam and try to update game server.<br />
<br />
====Using a script====<br />
<br />
Alternately, you can create a script that will perform a series of actions:<br />
<br />
<blockquote><code><br />
// update_kf_ds.txt<br/><br />
//<br/><br />
login user password<br/><br />
force_install_dir /home/unreal/killingfloor<br/><br />
app_update 215360 validate<br/><br />
exit</code></blockquote><br />
<br />
Now you can issue SteamCmd to execute the script:<br />
<br />
<blockquote><code>SteamCmd +runscript /home/unreal/killingfloor/update_kf_ds.txt</code></blockquote><br />
<br />
Place the script anywhere you want, just make sure to update the paths when invoking ''SteamCmd +runscript''.<br />
<br />
{{troubleshoot begin}}<br />
* I am getting errors.<br/><br/>'''Solution''': On some Linux distribution you may recieve errors with not loading some .so files, so try this (alter paths):<blockquote><code>#!/bin/bash<br/>DIR=/home/unreal/steamcmd<br/>export LD_LIBRARY_PATH="${DIR}/linux32:$LD_LIBRARY_PATH"<br/>cd ${DIR}/linux32<br/>./steamcmd +runscript ${DIR}/update_kf_ds.txt</code></blockquote><br />
{{troubleshoot end}}<br />
<br />
==Installation paths==<br />
<br />
You can specify installation directory in various ways:<br />
<br />
===Windows===<br />
<br />
* Absolute Path:<br />
<blockquote><code>force_install_dir c:\KFServer\</code></blockquote><br />
<br />
* Up one folder:<br />
<blockquote><code>force_install_dir ..\KFServer\</code></blockquote><br />
<br />
* In the Steam Command folder:<br />
<blockquote><code>force_install_dir .\KFServer\</code></blockquote><br />
<br />
===Linux===<br />
<br />
* Absolute Path:<br />
<blockquote><code>force_install_dir /home/unreal/killingfloor/</code></blockquote><br />
<br />
* Up one folder:<br />
<blockquote><code>force_install_dir ../killingfloor/</code></blockquote><br />
<br />
* In the Steam Command folder:<br />
<blockquote><code>force_install_dir ./killingfloor/</code></blockquote><br />
<br />
==Beta versions==<br />
<br />
If Tripwire is currently running a beta update of the dedicated server files:<br />
<blockquote><code>app_update 215350 -beta "branch name"</code></blockquote><br />
Where "branch name" is the current beta branch. Currently there is not a live dedicated server beta branch.<br />
<br />
== Starting the server ==<br />
<br />
Use the batch file downloaded with the server or create your own. To launch a server with default settings on BioticsLab use the following batch script:<br />
<br />
Windows<br />
<blockquote><code>ucc server KF-bioticslab.rom?game=KFmod.KFGameType?VACSecured=true?MaxPlayers=6</code></blockquote><br />
<br />
Linux<br />
<blockquote><code>./ucc-bin server KF-bioticslab.rom?game=KFmod.KFGameType?VACSecured=true?MaxPlayers=6 -nohomedir</code></blockquote><br />
<br />
==Server ports==<br />
<br />
The following list of ports need to be open for a server to run successfully:<br />
* 7707 UDP/IP (Game Port)<br />
* 7708 UDP/IP (Query Port)<br />
* 7717 UDP/IP (GameSpy Query Port)<br />
* 28852 TCP/IP and UDP (Allows your Server to Connect to the Master Server Browser)<br />
* 8075 TCP/IP (Port set via ListenPort that your WebAdmin will run on)<br />
* 20560 UDP/IP (Steam Port)<br />
* 123 UDP ('''Weekly Survival Only''' - Internet time lookup to determine appropriate weekly)<br />
<br />
Since the game is running with the Steam backend, if you are running more than 1 server per IP, you will need to make sure that you have some additional ports open beyond the default KF ports. If you change the default Game Port from 7707, this change will be reflected in the Master Server Port (28852) and the Steam Port (20560) as well.<br />
<br />
You must also change OldQueryPortNumber=7717 under [IpDrv.UdpGamespyQuery] in the KillingFloor.ini to match the increase of the 7707 port. So if you change 7707 to 7807, then 7717 would change to 7817. If this is not done, the server will crash when starting.<br />
<br />
==Advanced admin settings==<br />
<br />
Admins looking to made changes from the default settings will find most options available in the Killingfloor.ini (or in WebAdmin once enabled in the Killingfloor.ini).<br />
<br />
===Server name and passwords===<br />
<br />
<blockquote><code>ServerName=Killing Floor Server<br/><br />
GamePassword=<br/><br />
Adminpassword=</code></blockquote><br />
<br />
===Difficulty and Length===<br />
<br />
<blockquote><code>GameDifficulty=</code></blockquote><br />
<br />
Valid inputs:<br />
* 1.0 = Beginner - Your grandma can play the game<br />
* 2.0 = Normal - Quite challenging with lower level perks<br />
* 4.0 = Hard - Very challenging even with mid level perks<br />
* 5.0 = Suicidal - Incredibly difficult, even with high level perks<br />
* 7.0 = Hell on Earth - You'll be wishing you were one of them<br />
<br />
<blockquote><code>KFGameLength=</code></blockquote><br />
<br />
Valid inputs:<br />
* 0 = Short - A 4 wave game<br />
* 1 = Normal - The standard 7 wave game<br />
* 2 = Long - The longer 10 wave game<br />
* 3 = Custom - uses the custom sandbox settings for waves, monster counts, etc (which i won't go into here, but we'll talk about in another post). <br />
<br />
===Map voting===<br />
In the [xVoting.XvotingHandler] section of the killingfloor.ini admins need to set ''bMapVote'' to ''true'' in order to enable map voting.<br />
<br />
Admins can can also configure how soon a map can be re-voted for with ''RepeatLimit''. The numerical value determined the number of previously played maps that should not be selectable. 0 - Map can be voted for right away. 4(Default) - Four maps must be played before the map becomes available again.<br />
<br />
===WebAdmin===<br />
To enable WebAdmin, admins need to locate the [UWeb.WebServer] section of the Killingfloor.ini and set ''bEnable'' to ''true''.<br />
<br />
The default webadmin port is 8075 and once enabled Admins can log into it by navigating to <br />
<br />
<blockquote><code>YOUR_SERVER_IP:8075</code></blockquote><br />
<br />
in their favorite web browser and logging in with the admin name (default: admin if not set) and password.<br />
<br />
===In-game admin===<br />
When you're in game press your ~ key to open the command console and type:<br />
<br />
<blockquote><code>adminlogin <yourpassword></code></blockquote><br />
<br />
This will log you in as admin and will give you access to admin commands such as ''map'', ''kick'', and ''ban''.<br />
<br />
[[Category:Killing Floor]]</div>Dweiss