mschnitzer / ark-survival-ascended-linux-container-image

A docker/podman container that is able to run an ARK: Survival Ascended on a Linux host.
93 stars 18 forks source link

Adding Mods #21

Closed njakes closed 1 year ago

njakes commented 1 year ago

Is it possible to add mods via environment variable with MOD_IDS?

mschnitzer commented 1 year ago

Yes, you can add mods, but they need to be put behind ASA_START_PARAMS like so:

ASA_START_PARAMS=TheIsland_WP?listen?Port=7777?RCONPort=27020?RCONEnabled=True -WinLiveMaxPlayers=50 -mods=123,456,789

It automatically downloads all pending mods, so it might take a while until all mods have been downloaded.

There's a plan to make this process a little easier, but this is not yet released as an implementation in asa-ctrl yet ( see #7 )

mschnitzer commented 1 year ago

@njakes since you gave my reply a like, were you able to install mods?

njakes commented 1 year ago

I haven't tried yet but will report back when I do.

heusmich commented 1 year ago

Yes, you can add mods, but they need to be put behind ASA_START_PARAMS like so:

ASA_START_PARAMS=TheIsland_WP?listen?Port=7777?RCONPort=27020?RCONEnabled=True -WinLiveMaxPlayers=50 -mods=123,456,789

It automatically downloads all pending mods, so it might take a while until all mods have been downloaded.

There's a plan to make this process a little easier, but this is not yet released as an implementation in asa-ctrl yet ( see #7 )

Hi, For me this is not working. I added the mod IDs in the start parameters but they will not be loaded. My server is still without any mods. So currently the start parameters line in the docker-compose.yml file looks like this:

**environment:

Is there anything more that has to be done besides adding the mods to the start parameters? I already tried to add the mod IDs also to the GameUserSettings.ini as entry "ActiveMods=123,456,..." but it´s also not working. Would be nice if you could help me with that. In general the server is working and we can play on it.

Best regards heusmich

heusmich commented 1 year ago

OK, I think I found the problem.

I always restarted my server with the command docker-compose restart asa-server-1. But it seems that everytime a change was made in the start parameters, the container has to be recreated with the command docker-compose up -d.

mschnitzer commented 1 year ago

Yes, you need to use docker-compose up -d. Using your three mods, I was able to launch my test server successfully and it downloaded all mods. Any other change besides -mods is not needed.

I'm glad it's working for you.

heusmich commented 1 year ago

One additional question. When I change the start parameters, I have to use the docker-compose up -d command. Which command do I have to use when I change settings in Game.ini or GameUserSettings.ini? Is the command docker-compose restart asa-server-1 OK or do I also have to use the docker-compose up -d command?

mschnitzer commented 1 year ago

up -d recreates the container if the docker-compose.yml file has changed. In your case, where you want to edit the game config files, you can do a simple docker-compose restart asa-server-1.

heusmich commented 1 year ago

up -d recreates the container if the docker-compose.yml file has changed. In your case, where you want to edit the game config files, you can do a simple docker-compose restart asa-server-1.

OK, thanks!

mschnitzer commented 1 year ago

I'm closing this issue, as there's no response from the issue creator yet. If it's not working, please reopen this issue.