[2.0.66] Achievements disabled when decreasing tree coverage

[Drakken]

I am setting up literally the hardest map settings possible on vanilla Factorio. Deathworld Marathon, highest desert/sand settings, no water, minimal grass, minimal trees. Enemies at 600% and 600%.

I turned trees down to the absolute minimum, but I am getting the message for almost all available achievements: "Cannot be unlocked when tree spawning is higher than default."

Well... I have it set at much, much lower than default, so I think I deserve extra achievements, not less.

Good sirs, what say you?

[Rseding91]

Can you please post the save file?

[Drakken]

There is no save file. It is disabling achievements when I am trying to create and start the map. Is this not happening when lowering tree settings on the current version for the devs?

I could start the map after confirming that the achievements will be disabled, save the game, and then send that if you would like.

However, since I will be streaming this attempt, I don't really want to start it with the achievements disabled. Viewers would be disappointed and confused.

[Drakken]

To reproduce this issue. Start a new map and turn tree frequency and coverage all the way down. Then try to start the map.

It is happening on standard settings and deathworld marathon settings. Likely the case in all scenarios.

[eugenekay]

I turned trees down to the absolute minimum, but I am getting the message for almost all available achievements: "Cannot be unlocked when tree spawning is higher than default."

Well... I have it set at much, much lower than default, so I think I deserve extra achievements, not less.

Good sirs, what say you?

2.0.45 changed the conditions for Achievement eligibility:

Bugfixes

• Fixed that the achievements checks of map startup difficulty settings didn't check for pollution, expansion settings, starting area and trees.

Now, if you touch the sliders then Achievements are Disabled. The error message does indeed say higher when it ought to say lower or even changed from - but it really seems like this is Intentional to ensure uniform conditions for Achievements by everybody - so I say it’s a good thing. The prior “Bugged” behavior where you could adjust the sliders to make it much easier / harder depending upon the playstyle did feel cheesy.

Good Luck!

[naahuc]

reproducible with this map string (tested on 2.0.64)

Code: Select all

>>>eNp1VL+LE0EUnklcc+Y8DRIE4ThTXGETxdPCQrKjICKi/8I62Uzi4GY3Nz8ip4UpUio2NorgtZ5wnYLdgeAPUDi0sjuxsVCJKNoIcWZ3Z7O7iQPz9tv3vXnvfW+HLQAAECgAsFjBq5J6geMy2SJOQD0ABrbZJRd7LhUk7dvlBjgTVHaDXo+wesAycXvCjPVcxjLxSXet3sQ8E7zQ9mTAqE+cPvFFlpFeJ2DYcT3abqeZ/Yah3MN+i6e5+Y5HmjPOVCJ/2ISTb2JvRPZUNjErGxeBT2b4r2NBWNo/R1ng5+ex4FFxlcqu09Q6M3V9LPuUT3drscC9lunE4i7DvbTnIBeYCep3HMwIdroB5UJmK1tTjVe59NqSUdfBLm05HbLGswoswQjhTzY2Jk0K6Xe4IL6T0zUvGfaVrim9fem52JdKV+7CHEiYfqAB5d1M7al5AmgNXz0cDJeA3uNboDYe663QjrrIegM4iKKhcpplxRMFtTNqn52kg/BmdfP8pxv3bBhFHkUxGMWerabxXDDgMvovtWzAyVSeE+H6mQJRUaFKxFFzaAIicqhJCO98e7r+5+V2A/59/OP9peYVGx4/V/0+WtlsKLKk5RYS8+C+Xs+NFGBy7tgx9dGG797q9dWGlj5R1QadUmbrYhHAyj6F1m8rU1sEprWGSVNFsB2u30bJZwM+2HkdahCndfIlbV5rExZMOoMRRHcRRIcNe2gSos6vgHQPrYnCN6bsi1T9XCPTHyKtI+dZRjM+Q1kXbCXmSzHpRs1zu2Te0CMEixroqF/KF72Fv9U4VfSsoHDcxeRSjuzsTdNAJ9l97NmRfwDJOZE=<<<

It appears the tree scale condition is inverted, so that scale < 100% counts as increased tree spawning and triggers the disabler. Conversely scale at 600% is completely fine.
Might be an in-house discussion topic if that slider might be better served as a range, as minor changes up or down from 100% have very little effect, but there's major differences the closer you move to the extremes.

[jodokus31]

I could start the map after confirming that the achievements will be disabled, save the game, and then send that if you would like.

A savegame would contain the exact map settings, which makes it easier to reproduce.
The map string provided from the previous post should do it, too, i guess

[Drakken]

For me the achievements are disabled if I change tree settings up or down on the current experimental 2.0.66 build. I guess I will have to keep them at 100% until this is addressed.

Once again, the script explaining why the achievements are disabled could be changed to say any adjustment of trees disables achievements.

However, in the spirit of the game, it really should only be disabled when making the game easier, turning up tree settings, and not when you turn them down. I would think this is obvious and would not be very hard to accomplish.

[Skellitor301]

I thought this was just for steam achievements? IIRC the game wouldn't let you earn steam achievements if you play modded, used console commands, or set certain map settings across specific thresholds. But you can still earn achievements in the save itself, they just don't count towards steam achievements.

[jodokus31]

I thought this was just for steam achievements? IIRC the game wouldn't let you earn steam achievements if you play modded, used console commands, or set certain map settings across specific thresholds. But you can still earn achievements in the save itself, they just don't count towards steam achievements.

It's not modded (no additional mods from modportal), it's just changes in the vanilla/spage-age map settings. It's about the new restrictions, which were added in 2.0.45ff regarding map settings, that prevent you to get certain achievements, which otherwise wouldn't be much of an achievement
And I think, it affects both, Steam and ingame achievments

[Rseding91]

I believe I found the underlying issue. The way tree coverage works, the internal numeric value gets smaller as coverage increases, and larger as it decreases. However the check for “was it increased beyond normal” only ever checks if the numeric value is larger than normal.

[Skellitor301]

I thought this was just for steam achievements? IIRC the game wouldn't let you earn steam achievements if you play modded, used console commands, or set certain map settings across specific thresholds. But you can still earn achievements in the save itself, they just don't count towards steam achievements.

It's not modded (no additional mods from modportal), it's just changes in the vanilla/spage-age map settings. It's about the new restrictions, which were added in 2.0.45ff regarding map settings, that prevent you to get certain achievements, which otherwise wouldn't be much of an achievement
And I think, it affects both, Steam and ingame achievments

Yeah, what I mean is I thought the disabling of achievements was only for Steam achievements. I only brought up modded because that's one of the things that would cause a save to have disabled achievements. The thing I was thinking of that I had to double-check is the case though. When you play a modded save you still can earn achievements for that save, but they don't synchronize with Steam, making it so you can still use the achievements as goals. When it comes to modifying settings that disable achievements, it's not all achievements and if you've already unlocked the achievements on Steam then the only thing you'd be missing out is a portion of the achievements list for that specific safe.

You can find more info on the wiki about it.

[Drakken]

I believe I found the underlying issue. The way tree coverage works, the internal numeric value gets smaller as coverage increases, and larger as it decreases. However the check for “was it increased beyond normal” only ever checks if the numeric value is larger than normal.

I hope this can be fixed relatively easily. Thanks for your attention in this matter.

[Rseding91]

This is now fixed for the next release.