You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to interpreting the version incorrectly, the update command always thinks factorio is out of date. This has been causing the server to restart whenever it is run, which, in the case of the container version I'm using, is every hour by default.
Game
Factorio
Linux distro
Ubuntu 22.04
Command
command: update
Further information
Pre 2.0, the --version command output was formatted like this:
I think this also causes malformed JSON when sending (in my case) Discord hook, due to the LF control character:
[ .... ] Updating fctrserver: Sending Discord alertparse error: Invalid string: control characters from U+0000 through U+001F must be escaped at line 28, column 4
[ FAIL ] Updating fctrserver: Sending Discord alert: {"message": "The request body contains invalid JSON.", "code": 50109}
From /log/scripts:
Oct 24 14:56:57.359 fctrserver: START: PASS: Started [redacted]
Oct 24 14:56:57.380 fctrserver: UPDATE: INFO: Sending alert: fctrserver has received a game server update: 2.0.9
64
Oct 24 14:56:58.065 fctrserver: UPDATE: PASS: Using cached IP as public IP address
Oct 24 14:56:59.816 fctrserver: UPDATE: FATAL: Sending Discord alert: {"message": "The request body contains invalid JSON.", "code": 50109}
Oct 24 14:56:59.828 fctrserver: UPDATE: INFO: LinuxGSM version: v24.3.1
Oct 24 14:56:59.830 fctrserver: UPDATE: FATAL: core_exit.sh exiting with code: 1
User story
Due to interpreting the version incorrectly, the
update
command always thinks factorio is out of date. This has been causing the server to restart whenever it is run, which, in the case of the container version I'm using, is every hour by default.Game
Factorio
Linux distro
Ubuntu 22.04
Command
command: update
Further information
Pre 2.0, the
--version
command output was formatted like this:With the 2.0 update it is now formatted like this:
This causes LinuxGSM to interpret the version as
instead of
2.0.8
Relevant log output
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: