Thanks for continuing this mod, it's so useful for automation geeks like myself who enjoy watching bases spring up with as little input as possible. I hope Wube includes this functionality by default in 2.1.

Had a suggestion, maybe it's worthwhile: I'd love a way to embed blueprints/export strings within the blueprint of a BAD chest. I don't know what the game engine is capable of, but I thought maybe a (very long) text field on the BAD chest object could store an export string, which would be captured when the object is blueprinted. That way, when the BAD chest is placed from that blueprint later on, the export string could be copied out of that very long text field by the player and imported for use. (Or, when placed, the BAD chest itself could read that text field and automatically import it to the slot.)

Interested in your thoughts on this!

It's a very recursive idea =)

Unfortunately, we are facing difficulties:
1) The engine has an unreliable mechanism for saving custom information in a blueprints. (For this reason, I removed the option to save the scanner settings in the blueprints)
2) Importing/exporting large blueprints (especially books) can cause significant lag.

In the new version (I hope to publish it soon), I added the ability to use blueprints directly from the blueprints library. I hope this alternative will help your ideas.

Oooh, yes, it might help! Thank you!

Edit: just tested the new version... wonderful. Added the new signal and cloned a blueprint book from the main library to the game library - worked first go. Genius. Thank you!