![]() ~/Config: Your own config files, you need to edit these.Now generate the initial, default config files, before anything else: kf2.sh init You can query the list of available options by: kf2.sh help If everything went well, switch to the steam user: sudo -iu steamĪll KF2 server commands are wrapped in by kf2.sh, a script I created. The vanilla Killing Floor 2 server is around 17 GB in size so sit back and relax until it finishes, then proceed. Obtain a copy of the installer I created, then execute it with admin privileges: git clone Now, to perform all this, log in to your Vultr server with your normal user (i.e. installs kf2_autokick, which had to be done separately in the past.deploys initial configuration which you can build upon very quickly.deploys a helper command to make management very simple and easy.allows the necessary ports to pass the firewall.sets up access delegation so that you can actually control these things with the steam user.creates a systemd unit to conveniently control the KF2 server via system tools.obtains steamcmd, Valve’s official command-line tool for managing Steam-related content.creates a new dedicated steam user to deal with anything Steam-related, because it’s stupid to run things as administrator.There’s a whole lot of components needing installation and/or configuration for the KF2 server to work properly, but I thought I’d save you some (okay, a lot of) time by creating a script that does all that for ya.įor the curious, let me summarize what it does: The $5 Vultr instance should be more than enough for a server with up to 100 custom maps. To get your Linux server up and running, you need to complete the Vultr CentOS tutorial, then you can move on to the next step. It is a free variant of Red Hat Enterprise Linux, one of the most trusted Linux vendors out there. Also, CentOS is just a flavor (distribution) of Linux. I’ll use the terms VPS (=virtual private server), VM (=virtual machine) and server interchangeably here. So, without further ado, let’s do this! Vultr ![]() Finally, I extended my installer script with lots of great new stuff, so setting up a KF2 server became even easier, and I wanted a write-up to reflect those changes. But I realized that’s way beyond what most KF2 server admins will ever want to do, so I stripped those out, too. I also used to guide you through Nginx, SSL, domain names etc. apply any manually specified, custom map cycles as wellĬustom maps are particularly problematic, and in the previous revision of this guide I ranted about these issues in great length, so I’m not gonna do that again.automatically generate separate map cycles for stock and workshop maps.using these, regenerate the server’s actual config files automatically.configure KF2 options via very small config files instead of the enormous stock ones (almost 2 thousand lines).fire up a CentOS server with firewall, Security-Enhanced Linux and hardened management access.This article will guide you through setting up a proper KF2 server on Linux (CentOS) step-by-step. This one is only here for historical reference. This one is only here for historical reference.īIG FAT WARNING This tutorial is deprecated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |