Build: 1.5 3362 and 1.4.7 3283 Mode: Single player Creative in 1.5 and then Survival in 1.4.7 SERVER NAME: N/A SEED-ID: In Survival was 839139, but game has COQ before load is finished. Reproducibility: Always Severity: Fatal/Critical Type: COQ Summary: 1.5 3362 CREATIVE creates BLUEPRINTS that cause a COQ in 1.4.7 3283 SURVIVAL. NOT RELATED TO SAVE GAMES. Description: Blueprints created in Experimental cause a new game in Public to throw a COQ at Loading screen. Again, this is about bad BLUEPRINTS. No attempt was made to load a 1.5 save game into 1.4.7 Steps to reproduce: Download Experimental 3362 from Steam Start a new CREATIVE game and create a starter block SV. Just starter block is sufficient. Save Blueprint Quit and Exit. Revert to Public game 1.4.7 3283 and download from Steam Start a new SURVIVAL Game COQ occurs during loading process. Attachments: Two log files attached. The one from build 1.5 3362 that created the blueprint and the one from 1.4.7 3283 that tried to initialize.
I believe this is not a bug. When you create a blueprint, it's usually not going to be compatible with an older version of the game.
Sorry to repost here, but I could not respond in Archive. Just a little more griping. Ravien, I have played this game a lot (mostly RE, lol) and made many blueprints, and I understand that blueprints might be incompatible between builds. But I wasn't really creating something new. Instead, I was correcting a very small error in my existing blueprint. Because the file format was changed (not the content of the blueprint), I ended up losing this blueprint entirely from the public game. Perhaps it will come back after 1.5 is released. I looked at the Wiki and Empyropedia on the workshop, blueprints, and the factory, and found nothing about this possibility. I suggest that a general warning to beta testers that they should backup their *blueprint database* before subscribing to experimental. I did not realize that it was at risk. Maybe everyone else knows this but me, lol. -- end tirade here --
Here's the disclaimer from the experimental branch: So yes it doesn't specifically mention every single thing that can break. Maybe it could be edited to include that any user created content in experimental might not be compatible with the public branch, including new or existing save games, blueprints, and any files associated with custom scenarios or modding. A lot of people don't even remember that they are on the experimental branch. I'm a big fan of the way some other games handle experimental builds by giving you a giant popup you have to click on whenever you start the game in experimental mode. That way it reminds people that they are playing an experimental branch and that there are risks involved. This doesn't belong in the bug report though, maybe it can be moved to the feedback forum.
