First: Might be use/beginner error.
Importing the same BluePrint behaves different between .36 and .38. I haven't played in a long time and always got some error on .36 while important, so I just thought maybe it's gone in .38, so tried again but now some blueprints were missing and since you redid so much blueprints I thought I mention it.
The missing blueprints don't look broken though that I imported with .36
blueprint string: https://factorioprints.com/view/-LI0gc-a-2_VLWR-tx1d
[kovarex][0.18.38] Same Blueprint string different behaviour 0.18.36 <-> 0.18.38
[kovarex][0.18.38] Same Blueprint string different behaviour 0.18.36 <-> 0.18.38
- Attachments
-
- blueprint
- 3.jpg (712.88 KiB) Viewed 4356 times
-
- imported with .38
- 2.jpg (761.42 KiB) Viewed 4356 times
-
- imported with .36
- 1.jpg (774.85 KiB) Viewed 4356 times
Re: [0.18.38] Same Blueprint string different behaviour 0.18.36 <-> 0.18.38
This bug is still present in 1.0
Re: [kovarex][0.18.38] Same Blueprint string different behaviour 0.18.36 <-> 0.18.38
Hello, the import engine continues on error when loading individual entities, but the blueprint also contains invalid preview icons (with the old name). In that case, the blueprint is not loaded at all, to prevent bigger confusion.
As this is specific to the one-time renaming of the science packs (from science-pack-1, to automation-science-pack etc.), I would leave the logic as it is.
If you want to migrate this blueprint into newer version, the best way is to load it in older version of factorio (not sure in which we still called it science-pack-1), save the blueprint to a save or blueprint library and then load the save in the 1.0 version. The blueprint would be migrated properly and you can export the string
As this is specific to the one-time renaming of the science packs (from science-pack-1, to automation-science-pack etc.), I would leave the logic as it is.
If you want to migrate this blueprint into newer version, the best way is to load it in older version of factorio (not sure in which we still called it science-pack-1), save the blueprint to a save or blueprint library and then load the save in the 1.0 version. The blueprint would be migrated properly and you can export the string
Re: [kovarex][0.18.38] Same Blueprint string different behaviour 0.18.36 <-> 0.18.38
Ok, boskid changed my mind, invalid blueprint icon names will load as unknowns instead of cancelling the blueprint import.