Greetings everyone,
The bug I encounter are related to the 2 Achievements "Keeping your hands clean" & "Logistics Networks Embargo".
Step 1) Both Achievements can be unlocked without issue both in Steam & During a respective playthrough (and will show as completed if you continue that save)
Step 2) Starting a new game the game does not recognize either as completed and shows them as "not unlocked" in Factorio (Steam still shows them as unlocked)
Optional Step 3) The achievement can once again be unlocked during the new playthrough (but won't carry over)
----------------
Working theory: During the start of a new playthrough the game initially checks whether the (steam?) achievement is unlocked and updates your game accordingly. But I venture something was changed with the condition the game checks for when looking for these two achievements where it is unable to recognize them (i.e. Logistics Networks Embargo was updated in 2.0.9).
Not a horrible issue but atleast for me personally - I can enjoy playthroughs much more knowing I got all achievements done previously and don't have any pressures to play in a specific way and this is stopping me from starting a new playthrough.
[2.0.14] Achievement Validation Bug - "Keeping your hands clean" & "Logistics Networks Embargo"
Re: [2.0.14] Achievement Validation Bug - "Keeping your hands clean" & "Logistics Networks Embargo"
Thanks for the report. Can you reproduce this issue in the latest release? There was a fix somewhat related to this and I'm unsure if it solved this exact issue.
If you want to get ahold of me I'm almost always on Discord.
Re: [2.0.14] Achievement Validation Bug - "Keeping your hands clean" & "Logistics Networks Embargo"
At least, "Logistics Networks Embargo" is not fixed in the latest 2.0.27, it still doesn't stay between games and resets when I start the new game (cannot test "Keeping your hands clean" yet)Rseding91 wrote: Mon Dec 09, 2024 9:20 pm Thanks for the report. Can you reproduce this issue in the latest release? There was a fix somewhat related to this and I'm unsure if it solved this exact issue.