2 Bugs here:
1. If you take a map string from a pre space age version with cliffs disabled and load it in space age, you now have cliffs disabled on Vulcanus. The cliffs will still show on the preview but will not exist in game.
It seems vulcanus reuses the old cliff_settings portion of the map string.
I expect to not be able to modify Vulcanus cliffs as the preview has no controls for them.
2. Once a game has been started with the Vulcanus cliffs disabled, starting a new game with the default settings preset still has the cliffs disabled.
Restarting factorio resets to default.
I expect the default preset to be default and not retain settings from previously started games.
[Genhis][2.0.35] Able to disable vulcanus cliffs.
-
- Long Handed Inserter
- Posts: 56
- Joined: Mon Aug 27, 2018 12:46 pm
- Contact:
Re: [2.0.35] Able to disable vulcanus cliffs.
For 2, do you mean the new game starts with Vulcanus cliffs disabled even if the cliffs are not disabled on Nauvis?Phoenix27833 wrote: Sun Feb 23, 2025 9:18 am 2 Bugs here:
1. If you take a map string from a pre space age version with cliffs disabled and load it in space age, you now have cliffs disabled on Vulcanus. The cliffs will still show on the preview but will not exist in game.
It seems vulcanus reuses the old cliff_settings portion of the map string.
I expect to not be able to modify Vulcanus cliffs as the preview has no controls for them.
02-23-2025, 11-12-42.png
2. Once a game has been started with the Vulcanus cliffs disabled, starting a new game with the default settings preset still has the cliffs disabled.
Restarting factorio resets to default.
I expect the default preset to be default and not retain settings from previously started games.
-
- Long Handed Inserter
- Posts: 56
- Joined: Mon Aug 27, 2018 12:46 pm
- Contact:
Re: [2.0.35] Able to disable vulcanus cliffs.
YesFor 2, do you mean the new game starts with Vulcanus cliffs disabled even if the cliffs are not disabled on Nauvis?
Re: [Genhis][2.0.35] Able to disable vulcanus cliffs.
Thanks for the report, this is fixed for 2.0.40.