rhavinx/moria repository overview

⁠The Lord of the Rings: Return to Moria — Dedicated Server (Docker)

⁠Description

Docker container for hosting a dedicated server for The Lord of the Rings: Return to Moria⁠. The game server is a Windows binary and runs under Wine.

Server files are downloaded via DepotDownloader⁠ using an anonymous Steam login — no Steam account or credentials required. The container also pulls the Steamworks Common Redistributables (AppID 228980) alongside the game (AppID 3349480) — Moria ships steamclient.dll/steamclient64.dll next to its binary and needs this depot present to run.

⁠Container data life cycle

Initial container start → "data" volume is empty, new files are created in live "server" volume.

:Loop Container shutdown → Live data is copied to the "data" volume. Container start (subsequent launches) → Files in "data" volume are copied to live "server" volume (overwriting existing). Environment variables are then applied on top. Goto Loop

If you modify files in the "server" volume directly, they will be overwritten the next time the server starts.

⁠Directory Structure

.
├── data                          # Volume bind mount
│   ├── .wine                     # Wine prefix (initialized on first run, persistent)
│   ├── SaveGamesDedicated         # Synced with server folder on container start / shutdown
│   └── MoriaServerConfig.ini      # Synced with server folder on container start / shutdown
└── server                        # Volume bind mount, populated via DepotDownloader
    ├── Engine
    ├── Moria
    │   ├── Binaries
    │   │   └── Win64
    │   │       └── MoriaServer-Win64-Shipping.exe
    │   └── Saved
    │       └── SaveGamesDedicated # Contents synced with data folder on start / shutdown
    ├── MoriaServerConfig.ini      # Synced with data folder on start / shutdown
    └── ...

⁠Quick Start (Docker)

1. Create a docker-compose.yml file from the example below.
2. Start the container: docker compose up -d and monitor with docker compose logs -f.
3. Forward port 7777 (UDP) on your router.
4. See First Run Notes⁠ below — the Moria server binary itself needs a couple of restarts on a brand-new world before it is fully set up.
5. Connect to your server in the game client (AdvertiseAddress=auto is the default and works for most setups behind NAT with the port forwarded).

⁠First Run Notes

The Moria dedicated server binary (not this container) has its own first-run quirk: on a completely fresh world, the very first launch will log a line similar to:

LogOptions: Warning: Key 'None' doesn't exist in Action 'MenuToggleLast'.

When you see this, stop the container (docker compose down or docker stop moria) and start it again. On the second start, the game finishes creating its saved-data folders (including SaveGamesDedicated). At that point you can, if you wish:

• Edit data/MoriaServerConfig.ini directly for settings not covered by environment variables (do this while the container is stopped — see MoriaServerConfig.ini⁠ below).
• Drop an existing save into data/SaveGamesDedicated.

Then start the container normally going forward.

⁠MoriaServerConfig.ini

MoriaServerConfig.ini lives in the data volume and is synced into the server volume on every start (and back out to the data volume on every shutdown), the same way saves are. It is patched with your environment variable settings (where set) on every container start.

Any settings not covered by the environment variables below can still be hand-edited in data/MoriaServerConfig.ini — the container only patches the specific keys listed in the table; everything else is left as the game wrote it.

⁠REMOVE_SERVER_FILES

If DepotDownloader gets into a bad state or you want a clean reinstall:

• Set REMOVE_SERVER_FILES: "1" in your docker-compose.yml for one launch.
• Then set it back to "0". Your saves and MoriaServerConfig.ini are preserved in the data volume and will be restored automatically.

⁠Docker Compose (docker-compose.yml)

⁠Environment variables

services:
  moria:
    image: rhavinx/moria:latest
    container_name: moria
    stop_grace_period: 30s
    environment:
      TZ: "UTC"
      # PUID: "1000"
      # PGID: "1000"
      SKIP_UPDATE: "0"
      WORLD_NAME: "My Moria Server"
      WORLD_SEED: "random"
      DIFFICULTY_PRESET: "normal"
      SERVER_PASSWORD: "changeme"
      LISTEN_PORT: "7777"
      # ADVERTISE_ADDRESS: "auto"
      # SERVER_FPS: "60"
      # LOADED_AREA_LIMIT: "12"
      # REMOVE_SERVER_FILES: "0"
    volumes:
      - /path/to/server:/home/steam/moria/server
      - /path/to/data:/home/steam/moria/data
    ports:
      - "7777:7777/udp"
    restart: unless-stopped

⁠Volumes

⁠Ports

⁠Known Issues

• First-run double-start — see First Run Notes⁠ above. This is a quirk of the game server binary itself, not the container.
• Slow first connection — the server takes time to preload the world on a cold start. Subsequent connections are faster once the server is warm.