What does "Removed blueprint: map version too old" mean?
Posted: Thu Apr 15, 2021 4:37 pm
What has happend:
I just upgraded my non-dev installation from 1.0.0 to 1.1.32 and noticed that when I load *any* savegame I get a migration dialogue telling me that a bunch of blueprints were removed. Looking at the names it looks like all of them contained entities from mods that I don't currently use.
The weird thing is that a) I can still see them in the library as a bunch of named but empty blueprints, and b) I get that dialogue *every time* I load a not-yet-migrated savegame.
What do I do now?
Does this mean that blueprints are only migrated to a new version while the appropriate mods are installed? I always assumed that all blueprints are always migrated. Doesn't make much sense to me that they can't at least get their internal version number bumped instead of being forcefully deleted.
I managed to rescue one of the blueprints that had only a single modded entity amongst thousands of vanilla buildings by loading it in a seperate 1.0.0 installation, exporting it to string and then importing it into 1.1.32. But tracking down every affected blueprint and manually ex/import it is too much of a hazzle. Is there no automatic way to do this? Preferably one that doesn't require tracking down all the mods possibly involved.
Also the migration warning continues to show even for the one blueprint that I "rescued" by ex/import, and as you can see in the picture the warning also lists the same blueprint twice sometimes. Do I have to be worried about my "rescued" being deleted because it has the same name or something?
I just upgraded my non-dev installation from 1.0.0 to 1.1.32 and noticed that when I load *any* savegame I get a migration dialogue telling me that a bunch of blueprints were removed. Looking at the names it looks like all of them contained entities from mods that I don't currently use.
The weird thing is that a) I can still see them in the library as a bunch of named but empty blueprints, and b) I get that dialogue *every time* I load a not-yet-migrated savegame.
What do I do now?
Does this mean that blueprints are only migrated to a new version while the appropriate mods are installed? I always assumed that all blueprints are always migrated. Doesn't make much sense to me that they can't at least get their internal version number bumped instead of being forcefully deleted.
I managed to rescue one of the blueprints that had only a single modded entity amongst thousands of vanilla buildings by loading it in a seperate 1.0.0 installation, exporting it to string and then importing it into 1.1.32. But tracking down every affected blueprint and manually ex/import it is too much of a hazzle. Is there no automatic way to do this? Preferably one that doesn't require tracking down all the mods possibly involved.
Also the migration warning continues to show even for the one blueprint that I "rescued" by ex/import, and as you can see in the picture the warning also lists the same blueprint twice sometimes. Do I have to be worried about my "rescued" being deleted because it has the same name or something?