![]() rvice - Killing Floor 2 Dedicated Server.Now you can easily start and stop the server using the systemctl command, as in the following example: # systemctl start rvice Description = Killing Floor 2 Dedicated Server ExecStart = /usr/bin/unbuffer /usr/bin/wine "C:/steamcmd/kf2server/Binaries/Win64/KFServer.exe" kf-burningparis # The user account that will run the server User = kf2server Group = kf2server # The server is stopped by sending it a SIGINT (Ctrl-C) KillSignal = SIGINT # This hides most of the fixme errors in Wine, which are harmless in this case and just clutter up the output Environment = "WINEDEBUG=fixme-all" WantedBy = multi-user.target The following is a sample systemd service unit for the Killing Floor 2 Dedicated Server. One workaround is to fake a controlling TTY using the program unbuffer from expect (see also expect Ubuntu packages. This somewhat obstructs unattended startup of the server, for instance by a init script. If not, it attempts to start an xterm, presumably so that the user can see the console output even if they started the server by double-clicking it in Windows Explorer. On startup the server checks if it is connected to a controlling terminal. I suggest only setting an administrator's password for the Web Admin interface, and doing the rest of the configuration there. wine/drive_c/steamcmd/kf2server/KFGame/Config/). ConfigurationĮdit the configuration files to your liking (located in. Note that it is required to specify a map on the command line, otherwise Web Admin will not be accessible. Now run the server once to let it create its configuration files with default values: $ wine "C:/steamcmd/kf2server/Binaries/Win64/KFServer.exe" kf-burningparis The same command is later used to update the existing installation when Tripwire releases a new version of the dedicated server. Use the following command to install the server into C:/steamcmd/kf2server: $ wine "C:/steamcmd/steamcmd.exe" +login anonymous +force_install_dir kf2server +app_update 232130 +quit ![]() wine/drive_c/steamcmd/ in the kf2server user's home directory. (Without it, the server would crash on startup with the error message "BugSplatRC resource DLL not found".)ĭownload SteamCMD for Windows. Use winetricks to install Microsoft Visual C Runtime 2010 in Wine: $ winetricks vcrun2010 Run winecfg once to create a Wine directory hierarchy: $ winecfg You may also want to use the -base-dir option to specify a different location for the home directory than the default /home. create-home creates an empty home directory for the account. system makes it a system account which, among other things, will make it not show up at the login screen if you are using a full desktop environment. I used the official PPA for Ubuntu to install Wine 1.8.Ĭreate a new local user account on the machine that will run the server, and su to it: # useradd -system -create-home kf2server This is mostly based on the guide Installing KF 2 Server on Linux with WINE at the Tripwire forums. If you intend to run it on your regular PC, as will be covered here, it should at least run under its own user account. Ideally, it should run on its own (containerized/virtualized/bare metal) machine. See its AppDB entry.Īs this is a closed-source program which will run an Internet facing network server, it makes a lot of sense to try to contain it somewhat. However, the Windows version of the program runs perfectly well in a Wine environment. Killing Floor 2 has a dedicated server program, but it is not yet available for Linux. Update : See Containerized Killing Floor 2 Dedicated Server for an updated guide. I'll update this guide when I find the time. killingfloor.Update : This guide is out of date. Vi /home//killingfloor/game/System/Killingfloor.ini cat /home//killingfloor/game/System/Default.ini > /home//killingfloor/game/System/Killingfloor.ini ucc-bin server KF-farm.rom?Difficulty=7.0?game=KFmod.KFGameType?VACSecured=true?MaxPlayers=6 -ini=Killingfloor.ini -nohomedirĮdit Killingfloor.ini with the settings that you would like to use. ![]() ![]() force_install_dir /home//killingfloor/game/Ĭreate a startup script for your server. Set the installation directory and wait for the game files to download. Run SteamCMD and enter your Steam login identity./steamcmd.sh Sudo apt-get install lib32gcc1 screen wgetĬreate a directory for your server. Prerequisitesįirst, install the required packages. The commands were written for Ubuntu, but may be adopted to other Linux distributions (such as CentOS). In this tutorial, you will learn how to setup your own Killing Floor server.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |