-
Notifications
You must be signed in to change notification settings - Fork 4
Modded Support #2
Comments
Hi, the content of Your bind mount example would override all server files of the docker image, but i doubt this is what you want to achieve? According to the unofficial stationeers wiki entry on modding dedicated servers, you need to mount the mod files into the docker container: |
No, usage of The xml files need to be added or modified directly onto the server itself. Hence needing actual access to the server install location in order to modify/change whats located in `/path/to/server/rocketstation_DedicatedServer_Data/StreamingAssets/Data One such workshop item - take note of the "RUNNING DEDICATED SERVER" part. Even joining the actual Stationeers Discord it is well known that the usage of modconfig.xml is ignored. Once you join (if you do) just do a search within the And because the way you have your docker images creating a container that doesn't auto update is handy - as you can move/copy out those modified files and later put them back in once a new tag is grabbed. Edit: In fact I suggest you even "try" to follow that modding guide over at that wiki. Many people have tried and attempted to follow that. It never ends up working.
|
I totally believe you, it would not be the first time the unofficial wiki would contain false information. 😁 To get to the server files, you can use the docker cp command while the container is running: But if you only want to override the original .xml file to apply a mod you can just mount the modded .xml on top: Does this solve your problem? |
Actually yes it does! Forgive me I am trying to get my head around the way that docker operates. I'm going to assume if I If that is the case then The two commands being; And;
For smaller changes this would be fine, but for those that wish to setup not just simple autolathe changes, or mining drop rates or larger stacking but mods that change much more (ie mods that add different starting conditions) that would be a major PITA. |
You are correct.
You can also further specify the source path and just copy one file from the container:
Also correct.
I agree. You can also override a directory and apply many mods at once:
But until there is a standardized way to load mods this will remain hacky. |
I think this would be better overall. I'm going to test it now - and especially since the new update ( https://steamcommunity.com/games/544550/announcements/detail/5212326506783997647 ). Don't worry I'll pull the correct docker tag as I saw you just updated the docker file a little bit ago 😛 and wait for DockherHub to update too. |
Akright, I did some testing. Using However Personally as I only have ~3 xml files it is no issue. But if anyone wants to use any custom world start settings and so on that mount list will be endless with however this docker image is setup. Just to make sure and so that you don't need to ask;
Edit: My current docker compose (if you are curious); version: "3.3"
services:
stationeers:
container_name: stationeers
stdin_open: true # docker run -i - added for testing
tty: true # docker run -t - added for testing
ports:
- "27500:27500/udp"
- "27500:27500/tcp"
- "27015:27015/udp"
image: hetsh/stationeers:7290294188270596278-1
environment:
- WORLD_TYPE=Mars
- WORLD_NAME=mars_save
- SAVE_INTERVAL=300
- CLEAR_INTERVAL=-1
- SERVER_OPTS=-bindip 192.168.196.212
volumes:
- "/share/stationeers_docker/modded_Data/Stacked.xml:/var/lib/steam/linux32/steamapps/content/app_600760/depot_600762/rocketstation_DedicatedServer_Data/StreamingAssets/Data/Stacked.xml:ro"
- "/share/stationeers_docker/modded_Data/mineables.xml:/var/lib/steam/linux32/steamapps/content/app_600760/depot_600762/rocketstation_DedicatedServer_Data/StreamingAssets/Data/mineables.xml:ro"
- "/share/stationeers_docker/modded_Data/autolathe.xml:/var/lib/steam/linux32/steamapps/content/app_600760/depot_600762/rocketstation_DedicatedServer_Data/StreamingAssets/Data/autolathe.xml:ro"
- "/share/stationeers_docker/server_data:/stationeers"
- "/etc/localtime:/etc/localtime:ro"
|
This overrides the whole directory and if you only place the 3 modded .xml files in the modded_Data directory, the server is missing all of the other non-modded .xml files. |
Good compose file BTW. You can omit the |
The general direction you desire is not a direction I wish to take. I thank you for your time. Issue resolved. |
I understand. Your contributions are still greatly appreciated, thank you! |
There is now a direction that the modding community is heading towards. https://github.com/Erdroy/Stationeers.Addons Example of one mod out of several from different mod devs; https://steamcommunity.com/sharedfiles/filedetails/?id=2403825928 The way that you have your current docker setup will be (soon) impossible as the actual game server directory must be set as a mount point ( ref: #2 (comment) ) |
I don't have much time at the moment. I would appreciate you answering me some questions. |
Until Rocketwerkz changes how they develop their game there hasn't been any major changes needed to be made. Think of this as like the forge mod loader that can be added to minecraft. If Rocketwerkz changes anything critical I will assume that the modding community will shift towards using a system akin to https://github.com/BepInEx/BepInEx
I am already running a standard non docker instance setup using https://github.com/Erdroy/Stationeers.Addons . But I knew the pandantic type of person would ask such a thing .. so.. StationeersAddons/Stationeers.Addons#10
This doesn't apply to a dedicated server - so not sure how this question would even apply. Wrokshop subs in regards to stationeers only apply to a client - not the server. Never have. Edit: I am sure I stated this before but I will again. The most current up to date info about modding stationeers is always on their discord, in the |
Hi,
To be able to mod stationeers I need to be able to mount the stationeers server location to an external location. For example;
--mount type=bind,source=/path/to/server_install,target=$APP_DIR
and whatever$APP_DIR
happens to be from looking at https://github.com/Hetsh/docker-stationeers/blob/master/Dockerfile#L38The text was updated successfully, but these errors were encountered: