Still getting the blueprint crash mentioned in the other thread on 1.3.1, this occurs when trying to create a blueprint that contains a silo set to the simple launch on the default launch signal.

The mod Circuit Launchable Rockets (1.3.1) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event CircuitLaunchableRockets::on_player_setup_blueprint (ID 80)
LuaItemStack API call when LuaItemStack was invalid for read.
stack traceback:
[C]: in function 'set_blueprint_entity_tags'
CircuitLaunchableRockets/control.lua:86: in function <CircuitLaunchableRockets/control.lua:73>

I was able to reproduce the issue in 1.3.0 and fixed what I found for 1.31. As of 1.3.1, I can't reproduce this error. Can you give me some more detailed information? What other mods are you using?

If you could post a save file that causes the problem if I immediately make a blueprint, that would help, too.

Oddly enough, I had the crash, upgraded to 1.3.1, and then was able to Control-C copy make a blueprint with a silo at least once... and then when I tried again a few minutes later, it crashed again. And I didn't even so much as click on the silo in the meantime.

The only other mods that would touch the silo at all is your cargo insertion one, but I'll see if I can produce a minimal test case this evening. Or see if I can figure out why I was able to copy it once. I'll try picking up the silo and placing it again and resetting it as well.

I figured it out! I disabled every single other mod and just made a new world and it still crashed every single time in 1.3.1, which was very confusing to me since I thought I remembered it working once.

You CAN blueprint with a silo if you click the 'Create new Blueprint' icon on the hotbar and drag it over, then it pops up the preview and you click the green button and get your blueprint. If you hit Ctrl-C or use the 'Copy' or 'Cut' buttons on the hotbar, as soon as you let go from dragging it crashes with the error message I listed. For some reason there's a difference between creating a blueprint and the quick keys to copy or cut, and there's a bug in that specific case.

Thank you for the additional information. I was able to reproduce the issue and fix it in 1.3.2.