Arch Linux User Repository

With the upgrade to 0.15, I changed the default save file location and how it is set in /etc/conf.d/factorio (to match with the factorio-headless-experimental package) Before: SAVE_FILE=/var/lib/factorio/.factorio/saves/factorio-service-save.zip After: SAVE_NAME=factorio-service-save This will put the save file in /var/lib/factorio/factorio-service-save.zip The old factorio-service-save.zip file will be automatically copied to the new location upon upgrading (unless it already exists for some reason...). If you haven't changed /etc/conf.d/factorio, you shouldn't need to do anything. If you have modified /etc/conf.d/factorio, you'll have to set the SAVE_NAME correctly (the install script should give you a sensible value based on your previous SAVE_FILE value). In all cases, the old 0.14 default save will stay in .factorio/saves/factorio-service-save.zip Please also note that the factorio service will automatically be stopped when doing the upgrade to make sure it's copying an up-to-date save file.

This package tracks the stable release. Factorio has consistently been releasing experimental ahead of stable for significant periods of time since 1.0. Please don't flag this out of date if it's not actually out of date. Current stable is 1.1.70.

1.1.42 just released; this PKGBUILD diff successfully updated the package for me:

7c7
< pkgver=1.1.41
---
> pkgver=1.1.42
33c33
<             '824cd413ed056e4a28dbce76f743961d42e5aef87b385e27a9c57f1e924a9a5e')
---
>             '42909906a258dcd538148258dcb0ee9e03ca063851d3d8ca03d17126993b41d0')

I mistook 1.1.40 as stable and only noticed my mistake after I'd pushed changes. I've bumped pkgrel and brought this package back to 1.1.39 (which is still the stable).

@xiretza Sorry about that, should be fixed now.

The upgrade to 1.0.0 changed LICENSE, but the sha256sums weren't updated accordingly, causing the build to fail.

I would like to see --start-server-load-latest instead of --start-server '${SAVE_NAME}.zip': The service is automatically restarting on crash so with the load latest command it would automatically load the latest save. The current savegame should be placed then in the saves folder?

If the service is started the first time, it would generate the save and then load it. And also I assume there is only one save and autosaves there, not multiple games since its a headless server made for one purpose?

Correct me if I'm wrong :)

Also it would be nice to see the server-banlist.json and server-whitelist.json also in /etc/factorio where all of the settings files are located. (And initialize the banlist with an empty json array?)

Looks good now, thank you for the quick fix. An update fixed my file permissions too.

@netmonger Thanks for the report, this should be fixed now. You might want to set the file mode back to 600 if it contains credentials

After upgrading from 0.15 to 0.16 I am getting the following error:

Apr 03 20:29:52 factorio[13646]: 0.000 Error Util.cpp:49: Error when opening /etc/factorio/server-settings.json for reading: Permission denied

I got the server to finally launch after changing the perms from 600 to 644 for server-settings.json. However, I am not sure if that is the correct solution since the file can contain sensitive data.

As version 0.15.34 is released, current package fail with a 404 Not found when trying to download 0.15.33. curl: (22) The requested URL returned error: 404 NOT FOUND ==> ERROR: Failure while downloading http://www.factorio.com/get-download/0.15.33/headless/linux64 Aborting...