Nuclear Dawn

Nuclear Dawn

Not enough ratings
Dedicated Server Linux
By Viper
A guide on how to setup a Nuclear Dawn Linux dedicated server.
   
Award
Favorite
Favorited
Unfavorite
Requirements
To setup a dedicated Nuclear Dawn server you will need:

SteamCMD.
Install via SteamCMD
Setting up a Nuclear Dawn (SRCDS) server with the SteamCMD client is very simple. First you need to download the installer from Steam[www.interwavestudios.com] or here. Make sure you install this in a separate directory from other Source or HLDS games!

Then create a new folder which will eventually hold the game files. For instance “/home/nucleardawn”

Next open a editor and enter the following:

STEAMEXE=steamcmd ./steam.sh

The program will automatically update and enter you in to a Steam> prompt. Type help for more information.

Next open notepad and enter the following:

steamcmd +login anonymous +force_install_dir /home/nucleardawn +app_update 111710 validate

Be sure to:

Replace the “/home/nucleardawn” with the directory for the game you created earlier.
Setup the server
Now you have your base installation. You just need to configure it. Open Notepad and create a file called server.cfg and put it in the /nucleardawn/cfg folder. (Remember NOT to save it as an "txt" file)

Heres a base server.cfg file:

// Nuclear Dawn Configuration File, To be used with ND only! // Server Name hostname "Nuclear Dawn Server" sv_tags "nucleardawn" // Rcon Cvars rcon_password "" // Set remote control password sv_rcon_banpenalty 15 // Number of minutes to ban users who fail rcon authentication sv_rcon_log 1 // Enable/disable rcon logging sv_rcon_maxfailures 3 // Max number of times a user can fail rcon authentication before being banned sv_rcon_minfailures 5 // Number of times a user can fail rcon authentication in sv_rcon_minfailuretime before being banned sv_rcon_minfailuretime 10 // Number of seconds to track failed rcon authentications sv_password "" // Password protects server mp_roundtime 35 // Minutes in a round mp_maxrounds 2 // Number of rounds mp_timelimit 70 // Minutes for a map to last // Team balance mp_limitteams 1 // Sets how many players can a team have over the opposite team. mp_autoteambalance 2 // 0 = No balancing, 1 = Only balance on end of round (default), 2 = Only balance during the game, 3 = Balance throughout the round and at the end of the round. mp_unbalance_limit 2 mp_autoteambalance_delay 60 // Specify the amount of seconds into a round that balancing will occur // Communications // enable voice communications sv_voiceenable 1 // Players can hear all other players, no team restrictions 0=off 1=on sv_alltalk 0 // toggles whether the server allows spectator mode or not mp_allowspectators 1 // Contact & Region // Contact email for server sysop sv_contact emailaddy@example.com // The region of the world to report this server in. // -1 is the world, 0 is USA east coast, 1 is USA west coast // 2 south america, 3 europe, 4 asia, 5 australia, 6 middle east, 7 africa sv_region 3 // Type of server 0=internet 1=lan sv_lan 0 // Round-end Teamswap mp_roundend_teamswap 1 // Auto swap teams at round-end? (0=no/1=yes)

Optional:

// Commander selection nd_commander_accept_time 15 // The time (seconds) the selected commander has to accept nd_commander_election_time 45 // How long until a commander is selected at the beginning of a round // Team votes nd_commander_mutiny_min_players 3 // Minimum number of players connected to start a mutiny vote nd_commander_mutiny_surpress_time 5 // Time in minutes before a mutiny can start after a previous one, or after a new round nd_commander_mutiny_time 30 // Time (in seconds) a mutiny vote lasts nd_commander_mutiny_vote_threshold 51.0 // The percentage of team votes required for the current commander to be voted off nd_commander_surrender_vote_threshold 51.0 // The percentage of team votes required for the team to surrender the round // Resources nd_starting_resources 3000 // Resources that each team starts the game with // Spawning nd_spawn_min_time 6.0 // Min time in seconds player must be dead for before they can spawn nd_spawn_wave_interval 12.0 // Time in seconds between spawn waves // Bots bot_quota 6 // How many bots should enter the game bot_quota_mode fill // Fill the server with bots, if less than x players bot_join_after_player 0 // Should bots join after players have joined or start playing without players (1) // Additional nd_xmas 0 // disable or enable Christmas hats. 0=disabled, 1=hats only for commanders 2=hats for everyone. Only active during Christmas period. // Teams mp_force_autoassign 0 // force players to join a team when joining the server. 0=disabled 1=enabled
Starting the server
To start the ND dedicated server you can use this command:

First edit (or create) srcds_l/nucleardawn/cfg/server.cfg like you want it to be. Now we are ready to run the srcds.

./srcds_run -console -game nucleardawn +map downtown -maxplayers 32 -autoupdate

Your srcds is now up and running.

This will start the server with the basic commands, for 32 players with the map downtown. Ofcourse you can always add other commands like +ip you.ip.number.xxx to set the server to a specific ip.
Running srcds in background (re-attachable)
Here is an example script that will run srcds in the background in a "screen" you will need to have screen installed for this. make a file called server.sh and put this in:

Command(s):

#!/bin/sh echo "Starting Nuclear Dawn Server" sleep 1 screen -A -m -d -S ndserver ./srcds_run -game nucleardawn +map downtown +maxplayers 32 -autoupdate

Save the file, and chmod it to run

Command(s):

chmod +x server.sh

If you want to start your server, simply run server.sh . It will start your srcd server in the background, to open it type: Command(s):

screen -x ndserver

If you want to close it again press ctrl+a+d, and it will detach the screen and keep it running in the background.
1 Comments
Death Squad 23 May, 2015 @ 1:32pm 
Has this been successful to all who have tried it. I keep getting errors running STEAMEXE=steamcmd ./steam.sh