Server Setup Guide for [Starbound] Gamers

Game Server Requirements

To embark on your interstellar adventures with friends in Starbound, understanding the foundational requirements for a dedicated server is paramount. The specifications needed are largely contingent on the number of players you intend to host and the complexity of your desired gameplay, particularly if you plan to incorporate numerous modifications (mods).

At a minimum, for a small group of players (around 2), a server would ideally require a processor equivalent to a Core 2 Duo or Athlon 64 x2, with a Core i3 or higher being recommended for smoother performance. The CPU's core count is a significant factor, as it directly influences the number of players the server can comfortably support.

Regarding memory, a basic Starbound server for two players can function with 1GB of RAM dedicated solely to the server, suggesting a total system RAM of approximately 2GB. However, for a more robust experience, especially with a larger player base (e.g., 12 players), 2GB of RAM dedicated to the server is often recommended, with periodic restarts to maintain optimal performance. For general gameplay, 4GB of RAM is often cited as a recommended specification.

Storage-wise, Starbound itself requires about 3GB of available space. However, this figure will increase significantly with the addition of mods and saved game data. Therefore, ample storage, preferably Solid State Drive (SSD) for faster loading times, is highly advisable. Some hosting providers offer a minimum of 64 GB RAM and multiple SSDs for their Starbound servers.

Network connectivity is another critical component. A broadband internet connection is essential. Bandwidth requirements are estimated at around 100kbps per player. For external connections, the default port for Starbound servers is TCP 21025, which will need to be forwarded through your router and firewall to allow outside players to connect.

The operating system can be Windows (XP or later), macOS (10.7.0 or later with a 64-bit Intel CPU), or Linux (Debian Stable or Ubuntu 12.04 LTS or later). For Linux, a 64-bit operating system is required to run the server. While a discrete GPU is listed in general system requirements for the game, it is less critical for a dedicated server running without a graphical interface.

In summary, while Starbound can be relatively light on resources for a small, private server, scaling up for more players or extensive modding necessitates a more powerful CPU, increased RAM, and robust storage solutions.

Beginner's Guide

Setting up a Starbound server, whether on your own machine or through a hosting provider, involves several key steps to ensure a smooth multiplayer experience. This guide will walk you through the fundamental process.

1. Choosing Your Server Type: Self-Hosted vs. Rented

Before diving into the technicalities, decide whether you will host the server on your own computer or rent a dedicated server from a third-party provider. Hosting on your own machine offers complete control and can be free, but it demands a powerful PC and a reliable internet connection, and the server will only be online when your computer is running. Renting a dedicated server, on the other hand, provides high-performance hardware, 24/7 uptime, and professional support, often at a subscription cost.

2. Installing the Starbound Server Software

If self-hosting, the Starbound dedicated server software can typically be found through Steam. Navigate to your Steam library, search for "Starbound Dedicated Server" under the "Tools" section, and install it. For Windows, the executable is usually located in C:\Program Files (x86)\Steam\steamapps\common\Starbound\win32\starbound_server.exe (or win64 for 64-bit systems). On macOS, it's in ~/Library/Application Support/Steam/SteamApps/common/Starbound, and on Linux, ~/.local/share/Steam/SteamApps/common/Starbound/linux/starbound_server.

Some hosting providers offer instant setup, where the server software is pre-installed and ready to go shortly after purchase.

3. Initial Server Configuration

After installing, run the starbound_server.exe (or its equivalent for other operating systems) once. This will generate the necessary configuration files. The primary configuration file is starbound_server.config, typically found in the giraffe_storage or storage directory within your Starbound installation. This file is in JSON format and allows you to adjust various server settings, including passwords, ports, and default game settings.

To set up user accounts and passwords, locate the "serverUsers" section in starbound_server.config. You can add entries for each user, specifying a username, password, and whether they have admin privileges. For example:

"serverUsers" : {

"YourUsername" : {

"admin" : true,

"password" : "YourPassword"

}

}

Remember to save the file after making changes.

4. Port Forwarding (for Self-Hosted Servers)

For players outside your local network to connect to your self-hosted server, you must configure port forwarding on your router. The default port for Starbound is TCP 21025.

The general steps for port forwarding include:

Finding your router's IP address: This is often the "Default Gateway" in your computer's network settings (e.g., by typing ipconfig in Command Prompt on Windows).

Accessing your router's administration page: Open a web browser and enter your router's IP address. You'll likely need to log in with administrator credentials.

Locating port forwarding settings: This section might be labeled "Port Forwarding," "Gaming," or "NAT."

Creating a new rule: Specify TCP protocol and port 21025. You'll also need to enter the internal IP address of the computer hosting the Starbound server.

Allowing traffic through your firewall: Ensure your operating system's firewall (e.g., Windows Defender Firewall) also permits incoming traffic on port 21025.

You can verify if your ports are open using online port checker tools.

5. Connecting to Your Server

Once the server is running and port forwarding is configured (if self-hosting), players can connect:

Launch Starbound.

From the main menu, select "Multiplayer" or "Join Game."

Choose your character.

Enter the server's IP address. If connecting to a server on the same machine, use 127.0.0.1 (localhost). For external connections, use the public IP address of the server.

If a password was set, enter it.

Click "Join Server."

For Steam users, a simpler method is to right-click a friend's name in your Steam list and select "Join Game," provided both parties have "Multiplayer through Steam" enabled in Starbound's options.

6. Installing Mods (Optional)

Starbound boasts a vibrant modding community. To install mods on your server:

Subscribe to mods on the Steam Workshop: Find the desired mods and subscribe to them.

Launch Starbound (client-side): This allows the game to download the mod files to your computer.

Locate mod files: Mod files (.pak files) are typically found in C:\Program Files (x86)\Steam\steamapps\workshop\content\211820\ (Windows) or similar paths for other OS. Each mod will have a contents.pak file within its workshop ID folder.

Rename mod files: To avoid conflicts, rename contents.pak to something descriptive (e.g., FrackinUniverse.pak).

Upload to server: Transfer these renamed .pak files to the server's /mods folder. This can be done via FTP or the hosting provider's file manager.

Restart the server: The server will load the newly added mods upon restart.

Remember that all players connecting to a modded server must have the exact same mods installed client-side.

Hosting Service Comparison and Recommendations

Choosing the right hosting service for your Starbound server can significantly impact your multiplayer experience. Several providers specialize in game server hosting, offering various features tailored to gamers. When evaluating options, consider factors such as server location, performance, mod support, control panel usability, and customer support.

Here's a comparison of some notable Starbound server hosting providers:

Hostari: Praised for hassle-free server setup and high performance. They offer high-end machines and aim to streamline the process for quick deployment.

PingPerfect: Known for connecting players worldwide with servers in over 10 regions. They provide a user-friendly control panel and 24/7 support.

Nitrous Networks: Offers low-latency connections, utilizing SSD technology, DDoS protection, and instant setup. Their custom control panel, NiTROPanel, is designed for easy server management. Pricing starts around $9.5 per month for 10 game slots, including web hosting, MySQL, and DDoS protection.

Apex Hosting: Provides dedicated Starbound server hosting with a focus on minimizing gameplay interruptions and offering unlimited player slots. They are recognized for their experienced support team and quick server setup.

GameServerKings: A good option for low-budget hosting, offering fast and easy services with 24/7 premium support. They focus on optimizing hardware for a lag-free experience and provide additional services like web hosting and MySQL. Pricing can start around £5.35 for 6 player slots.

Shockbyte: Offers full mod support, 99.9% uptime, low latency, automatic updates and backups, and DDoS protection. They provide various plans based on player slots and RAM.

Streamline Servers: Known for extremely low ping, instant server installation, and a powerful admin panel. They also feature one-click mod installation and can support up to 256 players.

Nodecraft: Allows for easy modification of server settings and offers a user-friendly control panel.

Kamatera: Stands out for its highly customizable cloud solutions, allowing users to scale resources (vCPU, RAM) on demand. Their pay-as-you-go model is suitable for fluctuating player traffic.

Hostinger: Renowned for speed and performance, offering LiteSpeed-powered infrastructure and affordable plans for smooth gameplay.

InterServer: Provides reliability with a 99.9% uptime guarantee, daily backups, and unlimited bandwidth and storage at affordable flat-rate pricing.

AleForge: Offers pay-by-slot subscriptions, with options for up to 64 slots, 99.9% uptime, and an easy-to-use control panel with a mod installer for Steam Workshop content.

Nitrado: Provides a range of subscription plans for various player counts (4 to 200), with multiple global data centers and easy server management.

When making a decision, consider the following:

Player Count: How many players do you anticipate hosting simultaneously? This will directly influence the required RAM and CPU.

Modding: Do you plan to use many mods? Ensure the host offers easy mod installation and sufficient resources to handle them.

Budget: Hosting costs vary, often based on player slots, RAM, and additional features.

Location: Choose a server location geographically close to the majority of your players to minimize latency.

Support: Look for providers with 24/7 support, especially if you're new to server management.

Many providers offer DDoS protection, which is crucial for maintaining server stability against malicious attacks. Additionally, features like automatic backups and updates can save considerable time and effort.

Troubleshooting

Even with careful setup, issues can arise when running a Starbound server. Effective troubleshooting involves systematically identifying and resolving common problems.

1. Connection Issues

"Failed to connect to server" or "Connection refused":

Port Forwarding: This is a frequent culprit for self-hosted servers. Double-check that TCP port 21025 is correctly forwarded on your router and allowed through your firewall. Incorrect port forwarding means external connection requests cannot reach your server.

Server Status: Ensure the Starbound server application is actually running. Check the server console for any error messages.

IP Address: Verify that players are using the correct public IP address of the server. If connecting to a local server, ensure 127.0.0.1 is used.

Firewall/Antivirus: Temporarily disable your firewall or antivirus software to see if it's blocking the connection. If it resolves the issue, add an exception for Starbound and port 21025.

Router Login: If you've recently changed router settings, ensure you can still log into your router's administration page.

Lag or High Latency:

Server Location: If using a hosting service, ensure the server's data center is geographically close to the players.

Bandwidth: Insufficient internet bandwidth on the host's side can cause lag.

Server Resources: The server might be under-resourced (CPU, RAM) for the number of players or mods. Consider upgrading your hosting plan or reducing mod usage.

DDoS Attacks: While many hosting providers offer DDoS protection, persistent attacks can still impact performance.

2. Server Configuration File Issues

Server not starting or reverting to default settings: The starbound_server.config file is sensitive to formatting errors. If the file contains syntax errors (it's in JSON format), the server may fail to start or overwrite it with a default configuration.

Backup: Always make a backup of your starbound_server.config before editing.

JSON Validation: Use an online JSON validator (like JSONLint) to check for syntax errors in your starbound_server.config file.

starbound_server.config.old: If your configuration resets, look for a starbound_server.config.old file in the storage directory. This is a backup created by the server when it detects an invalid configuration. You can often recover your previous settings from this file.

3. Mod-Related Problems

Players cannot join modded server:

Mod Mismatch: All players must have the exact same mods installed, both client-side and server-side. Even a slight version difference can cause connection failures.

Incorrect Mod Installation: Ensure mod .pak files are correctly placed in the server's /mods folder and renamed appropriately to avoid conflicts.

Mod Dependencies: Some mods require other "library" or "dependency" mods to function. Always check a mod's description for prerequisites.

Server Restart: After adding or removing mods, always restart the server to apply the changes.

4. Admin Command Issues

Admin commands not working:

Admin Mode: Ensure you have enabled admin mode in-game by typing /admin.

Server Configuration: Verify that allowAdminCommands is set to true in your starbound_server.config.

Anonymous Admin: If anonymousConnectionsAreAdmin is set to true, any player can use admin commands, which is generally not recommended for public servers. For private servers, ensure serverUsers is correctly configured with your username and admin: true.

5. Server Performance Degradation Over Time

Memory Leaks: Some mods or server processes might have memory leaks, leading to increased RAM usage over time. Regular server restarts can mitigate this.

World Size/Complexity: Large, complex worlds with many player-built structures or active entities can strain server resources.

Updates: Keep both the Starbound server software and any installed mods updated to their latest versions, as updates often include performance improvements and bug fixes.

When troubleshooting, consulting server logs can provide valuable insights into the root cause of issues. These logs often contain error messages or warnings that can guide your diagnostic process.

Performance Optimization Tips

Optimizing your Starbound server's performance is crucial for providing a smooth and enjoyable experience for all players, especially in a game that encourages exploration and building across vast, procedurally generated worlds.

1. Hardware and Hosting Choices

Prioritize CPU and RAM: For a Starbound server, the CPU and RAM are the most critical components. A multi-core processor, preferably a Core i3 or higher, is recommended, as the CPU dictates the number of players the server can support. Adequate RAM is essential; while 1GB can suffice for 2 players, 2GB or more is advisable for larger groups or modded servers.

SSD Storage: Utilizing Solid State Drives (SSDs) for your server's storage will drastically improve loading times for worlds, assets, and player data compared to traditional Hard Disk Drives (HDDs).

Geographic Proximity: Choose a hosting provider with data centers located geographically close to the majority of your player base. This minimizes latency (ping) and provides a more responsive gaming experience.

Dedicated Resources: Opt for hosting plans that offer dedicated resources rather than shared hosting, where server resources are split among multiple users. Dedicated resources ensure consistent performance.

2. Server Configuration Adjustments

starbound_server.config Tuning: The starbound_server.config file offers several parameters that can be adjusted for performance. While specific values may require experimentation, some key areas include:

maxPlayers: While you might be tempted to set a very high player limit, a realistic number based on your server's hardware and network capacity will prevent performance bottlenecks.

serverFidelity: This setting can influence how frequently the server updates game state. Adjusting it might impact performance, though "automatic" is often the default.

scriptInstructionLimit and scriptRecursionLimit: These settings relate to how the server handles in-game scripts, particularly relevant for complex mods. Higher values allow for more complex scripts but can consume more CPU cycles.

Regular Restarts: Even well-optimized servers can benefit from regular restarts. This helps clear any accumulated memory leaks and ensures the server starts fresh, maintaining optimal performance. Some server owners restart their 12-player servers every 12 hours.

3. Mod Management

Curate Mods Carefully: While mods enhance gameplay, they can also be significant performance drains. Be selective about the mods you install, prioritizing those that are well-optimized and essential to your desired experience.

Test Mods Individually: When introducing new mods, add them one by one and monitor server performance. This helps identify any particular mod that might be causing issues.

Check for Updates: Keep all installed mods updated. Mod developers frequently release performance improvements and bug fixes.

4. Network Optimization

DDoS Protection: Ensure your hosting provider (or your own network setup) includes robust DDoS protection. Attacks can severely degrade server performance and availability.

Stable Internet Connection: For self-hosted servers, a stable and high-bandwidth internet connection is paramount. Avoid running other bandwidth-intensive applications on the same network as the server.

5. In-Game Practices

World Management: While Starbound features infinitely generating worlds, excessively large or complex player-built structures, especially those with many active objects or intricate wiring, can contribute to server load. Encourage players to build efficiently.

Player Count Management: If you notice consistent lag, consider temporarily reducing the maximum player count to see if performance improves.

By implementing these optimization strategies, you can significantly enhance the stability and responsiveness of your Starbound server, leading to a more enjoyable gaming experience for everyone involved.

Technical Q&A

This section addresses common technical questions related to Starbound server setup and management, providing concise and accurate answers.

Q1: What is port forwarding and why is it necessary for a Starbound server?

A1: Port forwarding is a network configuration that directs incoming internet traffic to a specific device on a local network. For a Starbound server, it's necessary to allow players outside your local network to connect to your server. By default, routers block unsolicited incoming connections for security reasons. Port forwarding creates a rule that tells your router to send traffic on a specific port (TCP 21025 for Starbound) to the internal IP address of your server machine.

Q2: How do I find my server's IP address for players to connect?

A2: If you are self-hosting, you will need to provide your public (external) IP address to your friends. You can find this by searching "my IP" on a search engine. If you are connecting to your own server on the same machine, use the loopback address 127.0.0.1. For rented servers, the hosting provider will typically display the server's IP address and port in your control panel.

Q3: Can I run a Starbound server on a Linux machine?

A3: Yes, Starbound servers can be run on Linux. A 64-bit Linux operating system, such as Debian Stable or Ubuntu 12.04 LTS or later, is required. The server software can be installed using SteamCMD.

Q4: How do I become an administrator on my Starbound server?

A4: To become an administrator, you first need to configure an admin account in your starbound_server.config file. Locate the "serverUsers" section and add an entry with your desired username, a password, and set "admin": true. After restarting the server, log in with that username and password, and then type /admin in the in-game chat to enable admin commands.

Q5: What are some essential admin commands for managing a Starbound server?

A5: Once admin mode is enabled, you have access to a wide range of commands. Some essential ones include:

/kick [player name] or /kick [player UUID]: Removes a player from the server.

/ban [player name] or /ban [player UUID]: Prevents a player from rejoining. You can specify a reason and duration.

/spawnitem [item ID] [amount]: Spawns a specified item at your cursor.

/warp [location]: Teleports you to a specific location.

/serverreload: Reloads server-side assets and configuration files.

/whoami and /serverwhoami: Displays your local and server username and admin status.

/whereami: Displays your current celestial coordinates.

/pvp: Toggles Player vs. Player mode.

Q6: How do I install mods on my Starbound server?

A6: Installing mods involves a few steps. First, subscribe to the desired mods on the Steam Workshop and launch Starbound client-side to download them. Then, locate the mod .pak files in your Steam workshop content folder (e.g., C:\Program Files (x86)\Steam\steamapps\workshop\content\211820\). Rename these contents.pak files to something unique (e.g., ModName.pak) and upload them to the /mods folder on your Starbound server. Finally, restart your server. Remember that all players must have the same mods installed.

Q7: My server's configuration file keeps resetting. What should I do?

A7: If your starbound_server.config file keeps resetting, it's likely due to a syntax error within the JSON structure. The server detects the error and reverts to a default configuration. Always use a JSON validator to check your configuration file for errors before saving. You can often find a backup of your previous configuration as starbound_server.config.old in the storage directory, which you can use to identify and correct the error.

Q8: Can I host a Starbound server without port forwarding?

A8: If you want players outside your local network to connect directly to your self-hosted server, port forwarding is generally required. However, some alternatives exist, such as using virtual private network (VPN) services that create a secure tunnel, making port forwarding unnecessary for most applications. For local multiplayer, port forwarding is not needed.