Factorio Forums

On my playthrough when i land on vulcanus it only generates coal patches, demolishers and clifs. But the map generation is creating it on a grass land without the other resources. I've tried reloading from other saves but still is the same.
Im playing this on a headless server, I did generate the map with the cli using --map-gen-settings

~/factorio/bin/x64$ ./factorio --version
Version: 2.0.10 (build 79578, linux64, headless)
Version: 64
Map input version: 1.0.0-0
Map output version: 2.0.10-1

Thanks for the report. Please attach your save file and the CLI command you used to generate the map.

I've attached the savefile and the map-gen-settings I've used to create the map

These were my steps for creating the map-gen-settings from a exange string:

1) I generated the map using this string 2) Then I've used the console to create the settings file 3) I've copied the file from %appdata%\Factorio\script-output into the server using scp
4) I used this command to create the map 5) I had realised the map was correctly generated but the deathworld settings werent applied, so i typed these commands on the game

Now I understand more where the issue comes from, I did try generating the map using the Windows factorio version with the map exchange string. Using the editor I went to vulcanus, this time everything was correctly generated, the things it share in common were the cliff patterns, demolisher regions and the coal patches locations.
Then I tried checking the map settings using the lua command on the surface of vulcanus on both saves (Windows[map-gen-settings-vulcanus.json] and the Headless[map-gen-settings-vulcanus3.json] versions).
There I found out where the issue came from. On the Headless version where I was doing the playthrough, almost all the vulcanus settings had 0 defaults thus many vulcanus things weren't generated. I believe the issue comes from how someone can generate a map using the create option with specific settings in mind (https://wiki.factorio.com/Multiplayer#D ... ess_server) the only option is using the --map-gen-settings and --map-settings arguments but there's not an option to use directly the map export string that contains all of the information.

In order to obtain the map-gen-setting.json from my particular map exchange string, I looked at the answers on this 5 years old post where the most recent answer was using this command:
viewtopic.php?t=71563
But that map-gen-settings.json that I was using didn't contain the information about the other planets because it used game.player.surface.map_gen_settings those are the settings specific for the surface of nauvis and that did work fine for the previous plays before Space Age.

But now after taking a deeper look at the lua-api seems I should have used game.default_map_gen_settings instead. I have tesed out if this map-gen-settings-default.json and indeed it generated vulcanus properly and I guess the other planets too. I think, an on going game can be fixed under /editor -> surfaces -> edit map gen settings.

Some possible solutions I can think to avoid this problem
1) Allowing to directly use the map exchange string as an argument for factorio --create
2) Updating the defaults to generate the map surfaces correctly(not just demolishers) if no information is present on map-gen-settings.
3) Doing some validity checks on factorio --create --map-gen-settings. Checking if the input json was generated using game.player.surface.map_gen_settings or game.default_map_gen_settings
4) Adding more documentation on how to generate the map-gen-settings and map-settings there is not much more than looking on the forums.

I was thinking about this issue a bit because it could be attributed to user error - applying Nauvis map gen settings globally. In the end I decided to do "solution 2" and enable autoplace objects which haven't been explicitly disabled. This will apply to all ungenerated planets in your save file.

The map exchange string idea in --create seems nice, we could consider it if there is demand from server owners.

Thanks for the reply