Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
1. Your blueprints still exist in a file, but are not readable due to downgrade, or marked as coming from higher version and thus invisible/ignored. Easiest way to get them back would be to go back to the version you had when the blueprints worked, export them manually to strings, and then re-import after you downgraded the version again.
2. If that does not work... it would suggesdt the file itself was wiped clean, and they are gone for good. F.
It requires that you use the hidden super-user 'The rest' menu option under the main Settings menu. This menu is made visible by holding CTRL+ALT while clicking on Settings.
In this menu you find and enable the bypass-library-sync flag, which disables synchronization of the global blueprint library with the loaded game.
You see: each game save stores a complete local copy of the blueprint library of each player who has ever partaken in that game. This is how Factorio ensures blueprint libraries are in a consistent state shared among all players in multiplayer games, because the blueprint library can be accessed via Lua script.
It never actually directly operates on the global blueprints. Just on a mirror local to the save. And if the game engine detects that 'you' - i.e. your user's blueprints were modified, it copies those changes back to your global blueprint storage.
By enabling the flag, you prevent Factorio from copying your now empty blueprint library over the top of your user's per-user library as retained in the save. And thus, the per-user blueprints - i.e. the blueprints that are your global blueprint library - are kept as they last were recorded in the save; intact, when you load the game.
After flipping the flag and loading the game, you have two choices on how to continue to recover your saves:
The first and most straightforward, but also tedious is:
When you do this do not save the game before quitting! It shouldn't be necessary as syncs from the per-user blueprint category to the global library should be instant. The worst that could happen is you screwed something up and you lose the backed up local library state of your precious save!
Alternatively, if you have a lot of blueprints and don't want to export and re-import everything as strings:
For the full official rundown:
https://forums.factorio.com/viewtopic.php?t=94427
build your blueprints. Bonus points if you put a copy of the blueprint in a chest next to the built blueprint.
Save the game, call it "BLUEPRINTS" or something else super obvious.
You have now most certainly made a future proof blueprint library that exists both locally and on Steam Cloud.
It's not quite so simple. Really.
SE even has terrain restrictions for some entities. Not even sure those space buildings all work on a lab-tile environment...
I'm assuming nobody has improved the SE compatibility with lab tiles since then, especially not Earendel himself, but I could be mistaken.