Lodestone Delverium Server Ports: Game, Query, Admin and Map

Updated October 3, 2026 · Delverium Guide

LodestoneServer documents UDP 27016 for gameplay and UDP 27017 for queries, with separate TCP ports for RCON, administration and the live map. Joining players use the gameplay address/port, not the map or admin address. These defaults apply to the community server, not automatically to stock Delverium hosting.

LodestoneServer public defaults and access controls observed October 3, 2026

Read the project's default services

Compare these with the server's actual configuration before changing firewall or forwarding rules. A customised port is not a reason to force the default. The project documentation advises opening the optional TCP services only to the users who need them.

Check a player's failed connection

1. Confirm the player is using the required Lodestone client layer and the host's matching versions.
2. Compare the host's game address and UDP game port with the client's ip:port entry.
3. Confirm the server is running and inspect its lodestone/boot-report.txt readiness output as described by the project.
4. Then have the host inspect the relevant network rule for the configured gameplay service. A working web map does not prove the game UDP connection is reachable.

Treat administration and map access separately

The README describes AdminPassword as activating RCON/API access and MapAccessKey as restricting map access; it says the map can otherwise be public. Set the intended access controls from the project documentation before making an optional service reachable. Players do not need an admin password simply to join the game.

If the server will not start

A Steam-launch check can make the server executable exit according to the current README, which still lacks a complete self-hosting procedure for that step. Port changes will not repair that prerequisite. Use the server overview to understand the limitation, and compare current project instructions before treating it as a firewall failure.