Necesse Dedicated Server Setup (SteamCMD, Linux & Windows)

Necesse Dedicated Server Setup

A Necesse dedicated server keeps a world available even when the player who created an in-game world is offline. This guide follows the official standalone server files and documented launch options. For the current Rust & Romance release line, check the v1.3.2 update guide before updating a live world.

Install the official server files

You can download the server package from the official Necesse server page. If you use SteamCMD, install the dedicated-server app, not the client:

steamcmd +force_install_dir /srv/necesse +login anonymous +app_update 1169370 validate +quit

Keep the install path explicit. A provider panel may use a different working directory, but it should still expose the current official server files and a repeatable update action.

Start the server

From the directory containing Server.jar, start a named world without the graphical interface:

java -jar Server.jar -nogui -world MyWorld -port 14159 -slots 10 -owner "AdminName" -motd "Welcome to Necesse"

-owner grants owner permissions to a player connecting with the specified name. Use the exact name you intend to administer the server, and run java -jar Server.jar -help against the current package when you need the complete supported option list.

Open the network

Necesse's documented default is UDP 14159. Open that port in the server firewall, router, and provider panel. Do not describe it as TCP/UDP unless your current build or provider explicitly adds another transport.

sudo ufw allow 14159/udp
sudo ufw reload

For home hosting, forward UDP 14159 to the server's stable LAN address. For a managed host, use the assigned address and external port from the panel; home-router forwarding is irrelevant.

Configuration and save paths

Common launch options such as -password, -motd, -pausewhenempty, -giveclientspower, and -logging are documented in the configuration guide. The official wiki places the data under:

Some launch options write to or override these locations. Confirm the actual data directory in the service command before backing up.

Run under a service manager

For a Linux server, use a dedicated OS user and a service manager. Keep the working directory and Java path explicit:

[Unit]
Description=Necesse Dedicated Server
After=network.target

[Service]
Type=simple
User=necesse
WorkingDirectory=/srv/necesse
ExecStart=/usr/bin/java -jar Server.jar -nogui -world MyWorld -port 14159 -slots 10
Restart=on-failure

[Install]
WantedBy=multi-user.target

Backups and updates

1. Stop the server before copying a save.
2. Back up the save directory and relevant configuration or launch command.
3. Update with the same official app/package and keep the pre-update copy.
4. Start privately, join with a test account, and verify the world before inviting everyone.

Never treat a fresh binary install as a save backup. See the cost guide when comparing managed backups with self-hosting.

Troubleshooting

• Not visible: check UDP 14159, the public address, firewall, and whether the process is running.
• World missing: check -world, -datadir/-localdir, and the actual save path.
• Version mismatch: update the server and clients to compatible builds.
• Server pauses: inspect -pausewhenempty and use the value format documented by the current jar.

Official references

• Necesse official server download
• Necesse Wiki: Multiplayer
• Necesse Wiki: Linux multiplayer

Want managed updates, saves, and backups? Launch a Necesse server with Supercraft.