@xiretza Sorry about that, should be fixed now.
Search Criteria
Package Details: factorio-headless 1.1.32-1
Git Clone URL: | https://aur.archlinux.org/factorio-headless.git (read-only, click to copy) |
---|---|
Package Base: | factorio-headless |
Description: | A 2D game about building and maintaining factories - Server version (stable branch) |
Upstream URL: | http://www.factorio.com/ |
Keywords: | game |
Licenses: | |
Conflicts: | |
Submitter: | duthils |
Maintainer: | mxmeinhold |
Last Packager: | mxmeinhold |
Votes: | 12 |
Popularity: | 0.187949 |
First Submitted: | 2015-12-08 23:26 |
Last Updated: | 2021-04-17 02:15 |
Dependencies (1)
Required by (1)
Sources (5)
mxmeinhold commented on 2020-12-05 16:30
xiretza commented on 2020-12-05 10:31
The upgrade to 1.0.0 changed LICENSE
, but the sha256sums weren't updated accordingly, causing the build to fail.
edjopato commented on 2018-04-09 14:02
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?)
netmonger commented on 2018-04-04 19:19
Looks good now, thank you for the quick fix. An update fixed my file permissions too.
mickael9 commented on 2018-04-04 11:57
@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
netmonger commented on 2018-04-04 11:10
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.
yapbreak commented on 2017-09-06 07:33
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...
mickael9 commented on 2017-07-28 00:21
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.
TilmanV commented on 2017-07-27 18:17
0.15.31 is stable!
mickael9 commented on 2016-11-10 01:22
Here it goes!
Pinned Comments
mickael9 commented on 2017-07-28 00:21
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.