Delverium Lodestone Server Setup: Files, Configuration and Startup

Updated October 4, 2026 · Delverium Guide

LodestoneServer documents a Windows headless setup using your own Delverium installation, server files beside Delverium.exe, a steam_appid.txt file and BepInEx configuration. The important success check is HOSTING in lodestone\boot-report.txt; Steam's launch check remains an explicit limitation in the project's self-hosting instructions.

Early Access · public developer/community documentation; collected October 4, 2026 UTC

Prepare the correct edition and machine

Use Windows 10, 11 or Windows Server and game files from your own Steam copy. Players need retail Delverium plus the Lodestone client app. This community package does not include the game or turn an unmodified Steam client into a direct-IP client.

Place the documented files

1. Get the server archive from the project's release page.
2. Copy the contents of the archive's LodestoneServer\bepinex\ directory into the game folder. Check that winhttp.dll, doorstop_config.ini, BepInEx\ and dotnet\ sit beside Delverium.exe.
3. Create steam_appid.txt beside the executable. The full-game value is 2710040; the separate demo value is 3426800. Use the value matching the actual installation.

Generate and edit configuration

The README gives the initial command below to write default configuration, followed by stopping the process and editing settings:

Delverium.exe -batchmode -nographics

In BepInEx\config\com.humangenome.lodestone.host.cfg, set the gameplay port, server name, world name, world size/difficulty and optional join password. The separate com.humangenome.lodestone.admin.cfg enables admin services when its password is set. Match firewall/NAT settings to the selected base port, then start again.

Check success before inviting players

Read lodestone\boot-report.txt. HOSTING means the world is running and accepts players. Give your group ip:port for the Lodestone app's Connect action. A process that briefly starts or writes a config file has not yet passed this check.

If the executable immediately exits

The project warns that Delverium exits when Steam's launch check is not satisfied. Its complete self-hosted solution for that check is not yet written up; adding the app-ID file is not documented as a universal bypass. Stop at that specific error, retain the build and boot-report details, and use the project's issue/support route rather than repeatedly changing ports. The startup verdict guide separates this failure from world and network failures.