Multiplayer: Mornedhel Docker server (Wine): Difference between revisions
More actions
Bonsaibauer (talk | contribs) Create English multiplayer setup guide |
Bonsaibauer (talk | contribs) Marked this version for translation |
||
| Line 10: | Line 10: | ||
<translate> | <translate> | ||
<!--T:1--> | |||
This guide covers the Mornedhel Enshrouded Dedicated Server Docker image using Wine. The upstream repository currently lists Wine image tags such as <code>stable-wine</code> and version-pinned <code>*-wine</code> tags. Check its [https://github.com/mornedhels/enshrouded-server current tag list] before choosing an image. | This guide covers the Mornedhel Enshrouded Dedicated Server Docker image using Wine. The upstream repository currently lists Wine image tags such as <code>stable-wine</code> and version-pinned <code>*-wine</code> tags. Check its [https://github.com/mornedhels/enshrouded-server current tag list] before choosing an image. | ||
== Compatibility note == | == Compatibility note == <!--T:2--> | ||
<!--T:3--> | |||
The ShroudForge server instructions currently document <code>WINEDLLOVERRIDES=dbghelp=native,builtin;winmm=native,builtin</code> for the Proton Docker image. They do not confirm that this exact override is required or tested for the Wine image. Do not assume that the Proton setting is a verified Wine configuration. Check the current Mornedhel image instructions and ShroudForge support notes before changing Wine-specific environment values. | The ShroudForge server instructions currently document <code>WINEDLLOVERRIDES=dbghelp=native,builtin;winmm=native,builtin</code> for the Proton Docker image. They do not confirm that this exact override is required or tested for the Wine image. Do not assume that the Proton setting is a verified Wine configuration. Check the current Mornedhel image instructions and ShroudForge support notes before changing Wine-specific environment values. | ||
<!--T:4--> | |||
Community reports describe successful ShroudForge asset preparation on a Wine Dedicated Server, but that is not a release-level compatibility guarantee for every feature or image tag. See [https://github.com/bonsaibauer/shroudforge/issues/75 the Wine server test discussion]. | Community reports describe successful ShroudForge asset preparation on a Wine Dedicated Server, but that is not a release-level compatibility guarantee for every feature or image tag. See [https://github.com/bonsaibauer/shroudforge/issues/75 the Wine server test discussion]. | ||
== Back up and find the game files == | == Back up and find the game files == <!--T:5--> | ||
<!--T:6--> | |||
Stop the server and back up the mounted game files. On the Linux host, find the container and record its current image tag, ports, mounts, restart policy, and environment values. Container inspection output can contain private values, so do not share it publicly. | Stop the server and back up the mounted game files. On the Linux host, find the container and record its current image tag, ports, mounts, restart policy, and environment values. Container inspection output can contain private values, so do not share it publicly. | ||
<!--T:7--> | |||
<pre> | <pre> | ||
docker ps -a | docker ps -a | ||
| Line 28: | Line 33: | ||
</pre> | </pre> | ||
<!--T:8--> | |||
The Mornedhel image uses <code>/opt/enshrouded</code> as its game-files mount. Use the host <code>Source</code> path associated with that mount. Confirm the exact server executable location: | The Mornedhel image uses <code>/opt/enshrouded</code> as its game-files mount. Use the host <code>Source</code> path associated with that mount. Confirm the exact server executable location: | ||
<!--T:9--> | |||
<pre> | <pre> | ||
docker exec "$NAME" find /opt/enshrouded -name enshrouded_server.exe -print | docker exec "$NAME" find /opt/enshrouded -name enshrouded_server.exe -print | ||
</pre> | </pre> | ||
== Install ShroudForge == | == Install ShroudForge == <!--T:10--> | ||
<!--T:11--> | |||
Follow [[Multiplayer: Install server files|the shared server-file setup]]. Copy the full ShroudForge release and the mod package into the host folder mounted into the Wine container, beside the server executable. Do not copy the files only into the container's temporary writable layer. | Follow [[Multiplayer: Install server files|the shared server-file setup]]. Copy the full ShroudForge release and the mod package into the host folder mounted into the Wine container, beside the server executable. Do not copy the files only into the container's temporary writable layer. | ||
<!--T:12--> | |||
Keep the existing Wine image tag unless you have a reason to change it. When updating the image, preserve the port mapping, mount, restart policy, and all existing environment values. Use the image's documented Wine tag, such as <code>stable-wine</code> or a version-pinned <code>*-wine</code> tag, rather than substituting a Proton tag. | Keep the existing Wine image tag unless you have a reason to change it. When updating the image, preserve the port mapping, mount, restart policy, and all existing environment values. Use the image's documented Wine tag, such as <code>stable-wine</code> or a version-pinned <code>*-wine</code> tag, rather than substituting a Proton tag. | ||
== Start and verify == | == Start and verify == <!--T:13--> | ||
<!--T:14--> | |||
Recreate or start the container using its existing Docker or Compose configuration. Check <code>shroudforge/logs/shroudforge-server.log</code> in the mounted host folder. Confirm that ShroudForge started, then verify the mod's behavior with a client connected to the server. | Recreate or start the container using its existing Docker or Compose configuration. Check <code>shroudforge/logs/shroudforge-server.log</code> in the mounted host folder. Confirm that ShroudForge started, then verify the mod's behavior with a client connected to the server. | ||
<!--T:15--> | |||
If the server starts but ShroudForge does not load, do not treat the setup as complete. Check the Wine image logs and the current ShroudForge compatibility guidance before adding or changing DLL overrides. | If the server starts but ShroudForge does not load, do not treat the setup as complete. Check the Wine image logs and the current ShroudForge compatibility guidance before adding or changing DLL overrides. | ||
Latest revision as of 11:54, 18 November 2026
This guide covers the Mornedhel Enshrouded Dedicated Server Docker image using Wine. The upstream repository currently lists Wine image tags such as stable-wine and version-pinned *-wine tags. Check its current tag list before choosing an image.
Compatibility note
The ShroudForge server instructions currently document WINEDLLOVERRIDES=dbghelp=native,builtin;winmm=native,builtin for the Proton Docker image. They do not confirm that this exact override is required or tested for the Wine image. Do not assume that the Proton setting is a verified Wine configuration. Check the current Mornedhel image instructions and ShroudForge support notes before changing Wine-specific environment values.
Community reports describe successful ShroudForge asset preparation on a Wine Dedicated Server, but that is not a release-level compatibility guarantee for every feature or image tag. See the Wine server test discussion.
Back up and find the game files
Stop the server and back up the mounted game files. On the Linux host, find the container and record its current image tag, ports, mounts, restart policy, and environment values. Container inspection output can contain private values, so do not share it publicly.
docker ps -a
NAME=YOUR_CONTAINER_NAME
docker inspect "$NAME" --format 'Image={{.Config.Image}} Ports={{json .HostConfig.PortBindings}} Mounts={{json .Mounts}} Environment={{json .Config.Env}} Restart={{.HostConfig.RestartPolicy.Name}}'
The Mornedhel image uses /opt/enshrouded as its game-files mount. Use the host Source path associated with that mount. Confirm the exact server executable location:
docker exec "$NAME" find /opt/enshrouded -name enshrouded_server.exe -print
Install ShroudForge
Follow the shared server-file setup. Copy the full ShroudForge release and the mod package into the host folder mounted into the Wine container, beside the server executable. Do not copy the files only into the container's temporary writable layer.
Keep the existing Wine image tag unless you have a reason to change it. When updating the image, preserve the port mapping, mount, restart policy, and all existing environment values. Use the image's documented Wine tag, such as stable-wine or a version-pinned *-wine tag, rather than substituting a Proton tag.
Start and verify
Recreate or start the container using its existing Docker or Compose configuration. Check shroudforge/logs/shroudforge-server.log in the mounted host folder. Confirm that ShroudForge started, then verify the mod's behavior with a client connected to the server.
If the server starts but ShroudForge does not load, do not treat the setup as complete. Check the Wine image logs and the current ShroudForge compatibility guidance before adding or changing DLL overrides.