Creating a blueprint of a constructed entity still waiting for modules to be installed can miss the item request proxy.
One blueprint, placed 5 times. Modules not yet inserted into last two assemblers.
Blueprint misses modules for last assembler, as the rectangle wasn't dragged quite far enough to catch the smaller item request proxy.
Real world case I was hit by this: duplicating a long furnace array. I intentionally kept the blueprint short as belts needed to be a bit different at the end.
[0.13.8] Creating a blueprint can miss the module proxy
Re: [0.13.8] Creating a blueprint can miss the module proxy
That's just how it works. You need to include the proxy entity if you want it in the blueprint.
If you want to get ahold of me I'm almost always on Discord.
-
- Filter Inserter
- Posts: 299
- Joined: Sun Jun 12, 2016 11:29 pm
- Contact:
Re: [0.13.8] Creating a blueprint can miss the module proxy
I think the bug here is the lack of visual feedback. With blueprints, what is included is marked with those edge markers. But those module requests fail to behave the same way.
Re: [0.13.8] Creating a blueprint can miss the module proxy
It's also inconsistent with how ghost entities can be blueprinted.
Re: [0.13.8] Creating a blueprint can miss the module proxy
No it's not, if you don't select a ghost it doesn't get included. The same applies for the module requester.DaveMcW wrote:It's also inconsistent with how ghost entities can be blueprinted.
If you want to get ahold of me I'm almost always on Discord.
Re: [0.13.8] Creating a blueprint can miss the module proxy
It's still inconsistent. Unbuilt entities show up as ghosts, unbuilt modules are invisible and unselectable.
Modules are an essential part of the factory, which is why there was such a huge demand to blueprint them in the first place. But it was only done halfway.
Modules are an essential part of the factory, which is why there was such a huge demand to blueprint them in the first place. But it was only done halfway.