Page 1 of 1

Achievement progress multiplied by player count

Posted: Sun Nov 19, 2017 3:26 pm
by bobucles
I was watching a stream and they had 10M progress towards the green circuit achievement, but only produced 1.2M in the prod tab. They said that every player in the game multiplies the achivement, so with 8 players the circuit count gets multiplied by 8. This is probably true for all production achivements.

Re: Achievement progress multiplied by player count

Posted: Sun Nov 19, 2017 5:35 pm
by Jap2.0
I''m not sure how this works in multiplayer, but in singleplayer the amound towards that achievement is from all your maps combined - I'm not sure if this is exactly how it works in multiplayer, but it is possible that if the streamer had 8.8M produced in other maps, that would be 10M.

Re: Achievement progress multiplied by player count

Posted: Sun Nov 19, 2017 6:28 pm
by zyklame
Jap2.0 wrote:I''m not sure how this works in multiplayer, but in singleplayer the amound towards that achievement is from all your maps combined - I'm not sure if this is exactly how it works in multiplayer, but it is possible that if the streamer had 8.8M produced in other maps, that would be 10M.
That's not correct. All players started with a fresh installation without any achievements started.
The error accumulated over the game itself.

Re: Achievement progress multiplied by player count

Posted: Sun Nov 19, 2017 7:16 pm
by Bilka
I was one of the players and can confirm this issue. At the end of the map we had produced about 4.5M circuits, but everyone already had the 20M achievement after we produced around 2.5M. Every single one of us reset our achievements, so the progress can't be from other maps, especially since this issue occured for everybody. I personally actually never opened another map on this installation.Here is the save and I attached my achievement dat (zipped because the forum doesn't allow files with .dat).

Re: Achievement progress multiplied by player count

Posted: Sun Nov 19, 2017 10:36 pm
by posila
Thanks for the report.
Should be fixed in 0.16