Hosting a Crossfire Server

This is a rough draft (and a work in progress) on suggestions and things to consider when hosting a Crossfire server.

Make sure you have the following available to you:

• Hardware that can handle hosting a Crossfire server
  • Any hardware that can run or handle a relatively modern desktop OS should be adequate
• Enough and fast enough bandwidth (it’s mostly upload speed that you are concerned about)
  • One should estimate 10kbps down (in) and 20kbps up (out) per user (kbps = kilo bits per second)
  • More bandwidth is of course better - even if not constantly being used, just so that the bursts of data get delivered faster
• Have an ISP allows for server hosting
• Network security to allow remote connections (aka, tweaked firewall rules) and communication to the metaserver(s)
  • NOTE: Make sure the hostname is a Fully Qualified Domain Name (FQDN), otherwise there will be connections issues within the Crossfire client

After your server and network is setup and configured, there are additional steps to consider.

• Become very, very familiar with the DM commands and how to use them
• Edit and update the MOTD (Message of the Day) information
• Edit and update the Server Rules file
  • As an example, if you want to ban players who exploit bugs, PK other players, disrupt gameplay for others, etc. - say so in the server rules file so if/when something like this happens you can take action and avoid the long “debate” afterwards
• Edit and update the Server News file - players like to know about new maps, bug fixes, special events, etc.
• Consider limiting how many guilds are initially available
  • This will prevent a player or small group of players from buying all the guilds at once
  • This helps to make sure guilds will be available for new players who join your server later on
• Have access to the server firewall rules for the extremely problematic player(s) and/or network(s)
  • Unfortunately, it’s advised that you learn how to block (ban) networks and subnets
  • Much of this can be done in game while in DM mode (command: banish) but sometimes attacks are too widespread or not coming from player(s) from within the game

• - using crossloop script or monit for automatically restarting after crashes
• - core dumps from crashes
• - using munin for monitoring and tacking server resources, more of a server host or administration benefit
• Have an automated and remote backup of player files and unique map files in case of hardware failure, data corruption or accident

If you want to attract players and build a community on your server - your server will need to be reliable, which means:

• Available on a consistent basis
• Available for the long term - at least several months (maybe longer)
• Adequate bandwidth for usage and performance
• Adequate hardware to handle server load
• The catch-22; you need players online to attract and keep new players
• Have a trustworthy DM (or two) to help players and address related issues