Headless 2.0.74 vs Docker availability (Switch version mismatch)

[mimoswk]

Hi,

Nintendo Switch version of Factorio was recently updated to 2.0.74. However, the commonly used Docker image (factoriotools/factorio) does not yet provide a 2.0.74 tag, and stable still points to 2.0.73. As a result, dedicated servers running 2.0.73 cannot be joined by Switch players due to version mismatch.

The 2.0.74 headless build is available, but experimental.

Questions

• Why is experimental release published to Switch ?

• Is 2.0.74 considered experimental-only for headless, but safe for Nintendo Switch ?

• Is there a recommended way to run a 2.0.74 server until Docker images are updated ?

• Is there an expected delay between experimental releases and Docker image availability ?

Environment:

• Synology NAS with Docker support

• Docker-based dedicated server on NAS

• Previously working fine since 2.0.23 - first issue with this

Switch clients cannot downgrade, so currently there is no way to connect to self-hosted servers unless the server is upgraded to 2.0.74.

I also created issue here: GitHub issue .


Thanks.

[boskid]

Mentioned github repository is a third party repository, we have no control over it and as such there is nothing we can do about it.

2.0.74 contains some important fixes for switch to help prevent save file losses, unfortunately it also contains a bug with rocket silo launching fish that prevents one of the achievements from being obtainable. When looking from PC point of view with no losses of save files, we do not want it to become stable due to fish achievement bug, but at the same time when looking from switch point of view, save file losses are significantly more severe issue than an achievement one and we want switch to be on 2.0.74 as soon as possible so we are where we are.

[mimoswk]

Thanks for help and clarification.

If someone hits this thread:

• Download docker directory from https://github.com/factoriotools/factorio-docker/

• Edit locally Dockerfile in line 66-67 to:

Code: Select all

ENV VERSION=2.0.74 \
SHA256=ad39bcc6e75a2e36552cf45ade270a4619f26ac782377aef4b16a2e1a68f9ff1

• build Docker image with these edits of Dockerfile

• run factorio-server with this new Docker image

I'm using Portainer to manage Docker on Synology NAS so I'm not able to pass ENV variables directly and version must be directly edited in Dockerfile.
I hope this "dirty" workaround is needed just for few days / weeks until stable 2.0.74 is released and Docker image factorio-server:2.0.74 also.

[Loewchen]

I hope this "dirty" workaround is needed just for few days / weeks until stable 2.0.74 is released and Docker image factorio-server:2.0.74 also.

The bug in .74 should rule out that it will ever declared stable.

[mimoswk]

Yes, sorry. I understand now.

I hope this "dirty" workaround is needed just for few days / weeks until stable 2.0.75 is released on Switch and also stable Docker image factoriotools/factorio:2.0.75.

[Twinsen]

We are planning a .76 release that should normalize everything. Unfortunately a Switch release with DLC will take at least 3 weeks.