Nightingale Dedicated Server Setup Guide (2026)

A Nightingale Realm is not something your group wants to restart, lose, or wait on. Once players start building, exploring, and returning to the same world, the server becomes part of the experience.

A Nightingale dedicated server lets you host that Realm on separate Windows or Linux server software instead of relying on one player’s session.

It can stay available while the server is running, uses UDP 7777 by default, and officially supports up to 6 players in a Realm.

This guide walks you through SteamCMD setup, launch settings, ports, configuration, saves, backups, connection fixes, and the hosting choices that make persistent multiplayer easier to manage.

How Nightingale Dedicated Servers Actually Work?

Nightingale multiplayer changes once you move to a dedicated server. You are no longer joining a player session. You are connecting to a server that runs independently.

Here’s how it works:

• The server runs as a separate application.
• It stays online even when no players are connected, provided the server remains running.
• World state and player progress remain saved.
• Players can join and leave without affecting uptime.

This removes the dependency on a host player and allows consistent access to the same world.

Listen Server vs Dedicated Server

Nightingale supports both co-op hosting and dedicated servers.

Co-op hosting (listen server):

• One player hosts the session
• Other players connect to that host
• The session ends when the host leaves

Dedicated server:

• Runs independently of any player
• Does not require a host to stay online
• Keeps the world available while the server remains online
• Supports continuous access for all players

Dedicated servers are better suited for long-term multiplayer sessions. If you are still comparing hosting models, this guide on dedicated vs non-dedicated servers explains the difference in more detail.

How Players Join a Dedicated Server

Connection depends on the platform being used.

Steam players:

• Can join through the documented Steam option
• Can also connect using IP address and port

Epic players:

• Can use IP/LAN for a direct connection
• Can use Join Codes for cross-platform play where available

Recommended approach:

• Use Steam or IP/LAN as the documented dedicated-server methods
• Use a Join Code when it is available for your hosting setup

Default configuration:

• IP address of the server
• UDP port 7777

Official setup uses port 7777 unless configured otherwise.

First-Connect Behavior

The first character to connect to a fresh server imports its associated Realms into the server’s persistent save.

• The server imports that character’s associated Realms if no player has previously initialized them.
• This defines the server’s initial Realm set.

This step should be controlled to ensure the correct world is loaded.

Server Behavior in Practice

Once the server is running:

• The world remains available while the server remains online
• Progress is saved automatically
• Players can connect at any time
• Server uptime does not depend on any player

This enables a consistent multiplayer experience.

Player Capacity Considerations

Nightingale dedicated servers are designed for small groups.

• The official supported maximum is 6 players in a Realm.
• Increasing beyond this is unsupported and may cause unintended behavior.

Some hosting providers advertise higher limits, but actual performance may vary.

Full Setup Guide: Nightingale Dedicated Server (Windows / SteamCMD)

Let’s discuss how to install, run, and expose a Nightingale dedicated server.

Follow each step carefully and check the server logs if startup or connection problems occur.

Installing via Steam (Tool-Based Setup)

This is the fastest way to get started.

Steps:

• Open Steam
• Go to Library → Tools
• Search for Nightingale Dedicated Server
• Install the tool

The server is available as a separate Steam tool (AppID 3796810).

Common default install location:

C:\Program Files (x86)\Steam\steamapps\common\Nightingale Dedicated Server

Use this method if:

• You are testing locally
• You want a simple setup
• You prefer a GUI workflow

Limitations:

• Not suitable for headless servers
• Hard to automate updates
• Not ideal for production hosting

Installing via SteamCMD

SteamCMD is the standard method for running dedicated servers.

Step 1 - Install SteamCMD

• Download SteamCMD from Valve
• Extract to:

C:\steamcmd\

Step 2 - Launch SteamCMD

steamcmd.exe

Step 3 - Login

login anonymous

Nightingale supports anonymous downloads. No Steam account required.

Step 4 - Download Server Files

force_install_dir C:\nightingale-server\

app_update 3796810 validate

quit

Directory Structure (Important)

After installation, the main server structure is:

nightingale-server/├── NWXServer.exe or NWXServer.sh└── NWX/├── Binaries/├── Config/└── Saved/

Key files and folders:

NWXServer.exe → Windows launch wrapperNWXServer.sh → Linux launch wrapperNWX/Config/ → configuration filesNWX/Saved/ → world data, logs, and persistence

This structure is important for configuration and troubleshooting.

When to Use SteamCMD

Use SteamCMD if:

• You run on VPS or dedicated hardware
• You need automation
• You need scripted installations or separate test and live deployments
• You are deploying on Linux

This is generally better suited to headless or automated deployments. For groups that want remote access, public networking, and full control, dedicated server hosting is usually the cleaner long-term route.

Launching the Server

The server listens on UDP 7777 and all network interfaces by default, although external access may still require firewall and NAT configuration.

Basic Launch

NWXServer.exe -port=7777 -log

Important Parameters

Port binding

-port=7777

Multihome (optional for binding to one specific local interface)

-multihome=YOUR_LOCAL_INTERFACE_IP

Log output

-log

• Opens a console window
• Useful for viewing live startup output on Windows
• Server logs are also stored in NWX/Saved/Logs.
• To stop the server safely, press Ctrl+C once, or twice if required, and allow it to complete a graceful shutdown.

Status endpoint

-statusPort=PORT

• Enables HTTP status monitoring
• Binds to localhost by default
• Useful for local monitoring and automation

Networking & Ports

Networking is a common source of connection problems. The server may start normally even when a firewall, router, CGNAT, version mismatch, or incorrect setting prevents players from joining.

Primary Game Port (UDP 7777)

Nightingale uses UDP port 7777 for gameplay by default. You can select another UDP port with the -port= argument.

If this port is closed or mapped incorrectly, your server will not be reachable from outside your network. The optional HTTP status endpoint uses a separate port only when you enable it with -statusPort=PORT.

Port Forwarding (Home Hosting)

If you are hosting from a local machine, your router must know where to send incoming traffic.

You need to create a port forwarding rule that maps:

• External port: your configured game port
• Internal IP: your server machine (e.g., 192.168.x.x)
• Internal port: the same configured game port
• Protocol: UDP

This step allows external players to reach your server through your network.

Firewall Configuration (Windows)

Your system firewall must allow incoming traffic on the same port.

Create an inbound rule that:

• Allows UDP traffic on the configured game port
• Applies to the appropriate Windows network profile used by the server

Even with correct port forwarding, a blocked firewall will prevent all external connections.

Public IP vs Local IP

Remote players using direct IP joining generally connect through your public IP address.

A local IP (like 192.168.x.x) only works inside your network. External players will not be able to use it. You can find your public IP by searching “what is my IP” on your browser.

If your IP changes often, consider using a static IP or a DNS service for consistency.

Additional Ports (Context)

An additional HTTP port is needed only if you enable the optional status endpoint with -statusPort=PORT.

TCP vs UDP

Nightingale gameplay runs on UDP, not TCP.

Your firewall and router must allow UDP traffic specifically. TCP settings do not replace UDP and will not enable gameplay connectivity on their own.

Server Configuration & Settings

Configuration is limited but critical.

Config Location

NWX/Config/

Required Setup Step

You must create your config file:

1. Go to:

NWX/Config/

2. Copy:

ExampleServerSettings.ini

3. Rename it to:

ServerSettings.ini

This is the file the server actually reads.

Example:[/Script/NWX.NWXServerSettings]Password=AdminPassword=youradminpassword

Set the player limit through the launch command:-ini:Game:[/Script/Engine.GameSession]:MaxPlayers=6

Nightingale server configuration is currently limited. Only a small set of parameters is exposed, and many gameplay systems are not configurable yet.

What You Can Configure

• Connection password
• Administrator password
• Player limit, game port, interface binding, cheats, console or JSON logging, and status monitoring through launch arguments.

Persistence Behavior

Realm data is stored in:

• NWX/Saved/Offline/DedicatedServer/Deploy

Character data is stored in:

• NWX/Saved/Offline/[PlatformID]/Profiles
• [PlatformID] is the connecting player’s Steam or Epic identifier.
• Progress loads automatically
• Server maintains state across graceful restarts

First-Connect Behavior (Critical)

The first character to initialize a fresh server imports its associated Realms.

• The character’s associated Realms are imported into the server
• This sets the server’s initial Realm set

Correct setup approach:

• First, join with a new character
• This creates an empty Abeyance Realm
• Then reconnect with your main character

Otherwise, the existing character’s associated Realms may be imported.

Current Limitations

• Configuration depth is limited
• Not all gameplay systems are configurable

Automatic Backup Behavior

The first time the server launches on each particular weekday, it copies the Offline directory into NWX/Saved/OfflineBackup.

The official guide does not document a setting for changing this behavior.

For a complete backup, copy:

• NWX/Saved/Offline
• NWX/Saved/Config
• NWX/Config

Linux, Docker & Advanced Hosting

If you are moving beyond a basic setup, this is where things change.

More control, more flexibility, but also more responsibility. Let’s break down what actually works and what to expect.

Running on Linux

Nightingale provides an official Linux dedicated-server build that can be installed using SteamCMD. If it does not start, check dependencies, permissions, the working directory, and NWX/Saved/Logs.

Basic Linux Setup (SteamCMD)

sudo apt update

sudo apt install wget tar lib32gcc-s1 -y

mkdir ~/steamcmd && cd ~/steamcmd

wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz

tar -xvzf steamcmd_linux.tar.gz

./steamcmd.sh +login anonymous +force_install_dir "$HOME/nightingale-server" +app_update 3796810 validate +quit

Start the Linux server from its installation directory with:

./NWXServer.sh -port=7777

Review the command output and NWX/Saved/Logs if startup fails.

Docker Deployment (Community-Based)

Inflexion’s official guide does not provide a Docker image or Docker deployment instructions.

When to Use Docker

• Isolated environments
• Repeatable deployments
• Controlled dependency management

What Actually Matters for a Working Setup

Focus on these:

• Use SteamCMD for deployment
• Use -multihome only when binding to one assigned local interface
• Review NWX/Saved/Logs and use -log on Windows for live console output
• Open the configured UDP game port properly
• Create ServerSettings.ini correctly
• Control the first player connection
• Check for CGNAT if LAN connections work but direct internet connections fail

Troubleshooting: Fix Common Nightingale Server Issues

Nightingale server problems can involve networking, server readiness, version compatibility, passwords, launch settings, or the host environment. The following table identifies the issue fast and its fixes

Performance & Hardware Requirements

The official Nightingale dedicated-server guide does not publish minimum or recommended CPU, RAM, storage, or bandwidth requirements.

CPU

No official core-count or clock-speed requirement is published.

Recommended:

• Use a modern CPU
• Monitor total and per-core usage during actual gameplay

RAM

There is no official RAM specification for dedicated servers.

Start with a monitored deployment and track:

• Idle memory use
• Peak memory use with active players
• Memory use during Realm activity
• Increase RAM only when measured usage approaches the available limit.

Storage

The official guide does not publish a fixed storage requirement.

Reserve enough space for:

• Server files
• Realm and character data
• Logs
• Backups
• Update staging
• SSD or NVMe storage is recommended, but it is not listed as mandatory.

Bandwidth

Network quality has a direct impact on player experience.

No official per-player bandwidth requirement is published.

Prioritize:

• Stable latency
• Low packet loss
• Sufficient upload headroom
• Consistent routing to your player group

Player Capacity

Nightingale officially supports up to 6 players in a Realm.

You can enter a higher value through the command line, but it is unsupported and may cause unintended behavior.

Performance still depends on the host, network, and server build.

What Causes Lag

Lag can have more than one cause.

Check:

• CPU saturation
• Memory pressure
• Storage activity
• Packet loss or latency
• Client/server version mismatch
• Errors in NWX/Saved/Logs

Scaling Considerations

Nightingale servers are not designed for large-scale multiplayer.

• Officially supported group size: up to 6 players
• Higher load increases CPU and network pressure
• Stability can depend on player activity, hardware, networking, and the current server build

Some hosting providers advertise higher limits, but real performance varies based on infrastructure and configuration.

Self-Hosting vs Hosting Providers: What Should You Choose?

How you host your Nightingale server affects more than cost. It changes uptime, persistence, setup effort, and how much control you have over updates, networking, and recovery.

A VPS or dedicated machine may be the better option when you want an independently operated, always-on environment.

Choose this route if:

• your group plays regularly
• you want the world online even when you are offline
• you need public connectivity, remote access, and more predictable availability

This gives you more operating-system and file-level control without relying on a home PC. If you want single-tenant hardware with deeper infrastructure control, bare metal servers are another option to consider.

How to Choose

Use this decision logic:

• Choose self-hosting if cost matters most and your group can tolerate downtime.
• Choose a VPS or dedicated server if persistence and control matter most.
• Choose a hosting provider if ease of setup matters most and you want less hands-on work.

How to Join a Nightingale Dedicated Server

Joining a Nightingale dedicated server is simple once you know the correct flow. Connection problems can result from the selected method, incorrect details, blocked traffic, or incompatible client and server versions.

How Joining Works

For dedicated servers, Steam and IP/LAN are the officially documented joining methods.

There is a platform difference here:

• Steam players can join through Steam-based friend joining in supported cases after the dedicated server update.
• Epic players can use IP/LAN, while Join Codes support cross-platform play where available.

For mixed-platform groups, use IP/LAN or a Join Code when that option is available for the hosting setup. The February 2026 Nightingale update introduced Join Codes, Steam Datagram Relay fallback, and Steam–Epic cross-platform play.

Step-By-Step Join Flow

1. Launch Nightingale
2. Click Play
3. Select your character
4. Choose Join
5. Pick the correct connection method:
   • Steam if you are a Steam player joining through Steam
   • IP/LAN if you are joining by direct address
6. Enter the server IP
7. Type the port manually
8. Enter the password if the server is protected
9. Connect

When using IP/LAN, confirm that the port field matches the UDP port configured on the server.

Password-Protected Servers

If the server uses a password, players need that password before joining. A correct IP and port will still fail if the password is wrong.

Common Player Mistakes

The most common join errors are simple:

• using a local IP instead of the server’s public IP
• forgetting to type the port manually
• entering IP:port in one field instead of separating them
• trying to use Steam joining from Epic instead of IP/LAN or an available Join Code
• using the wrong join mode

If you want the cleanest player experience, share the details like this:

• IP: 203.0.113.10
• Port: 7777
• Password: yourpassword

That reduces address and port formatting mistakes.

Running Nightingale at Scale

Running Nightingale “at scale” is not just about adding more players. It is about supporting a persistent shared world that your group expects to be available, stable, and synchronized over time.

A dedicated server is not just hosting a temporary match. It is maintaining the world your group returns to.

Why Latency Matters in Nightingale

Nightingale depends on constant state sync between players and the server. When latency rises, the impact shows up in the places players feel immediately:

• Delayed Interactions
• Slower Combat Response
• Rough Portal Transitions
• Inconsistent shared-world updates

In a temporary co-op session, players may tolerate that. In a persistent server, those issues compound because people expect the world to feel stable every time they log in.

Why Uptime Matters More Here

With a dedicated server, your group is choosing persistence over host-based sessions. That only works if the server stays online reliably.

If uptime is poor:

• Players lose trust in the server
• Shared progression becomes harder to maintain
• The practical value of a dedicated server drops

That is why Nightingale's hosting decisions are tightly linked to uptime. If your world is supposed to stay available, downtime is no longer a minor inconvenience. It reduces one of the main benefits of running a dedicated server.

Why Bandwidth Stability Matters

Nightingale does not just need a connection. It needs a stable one.

Jitter, packet loss, and uneven upload performance create problems even when the server technically remains online. Cloudflare explains that DDoS attacks are designed to disrupt normal server, service, or network traffic.

Players may still see connection issues, sync problems, or degraded play quality. That is why home hosting can work for private testing, but long-term shared-world use benefits from stronger network consistency.

When Stronger Infrastructure Becomes Necessary

You should move beyond casual hosting when:

• Your Group Plays Regularly
• Players Join From Different Locations
• The World Needs To Stay Online Consistently
• You Want Fewer Connection Issues And Better Reliability

At that point, stronger infrastructure can improve availability, remote access, and network consistency while reducing manual intervention.

Why RedSwitches Works for High-Performance Game Servers

A Nightingale dedicated server makes the most sense when your group wants a Realm that stays available, stable, and easier to manage beyond one player’s session.

The setup still depends on correct ports, configuration, backups, updates, and network quality, but the right hosting environment can make daily server management smoother.

For players who want more control than home hosting or a basic game panel, RedSwitches gaming dedicated servers are a strong fit.

Dedicated hardware can reduce resource contention, support consistent multiplayer access, and give you full control over the server environment.

Just remember that final performance still depends on the Nightingale server build, routing, configuration, and how your group uses the Realm.