Page 1 of 1

[Lou][2.0.23] Instant blueprint building does not always work in Editor mode

Posted: Wed Dec 04, 2024 7:29 pm
by Yodo
Instant blueprint building does not work in Remote view Editor mode, but Instant deconstruction does work.

Steps to reproduce:
1. Enter editor mode
2. Hold an item in hand
3. Enter Remote view
4. Build with item - > ghosts are created and not placed automatically

Steps 2&3 can also be reversed, if you pipette or open "Set ghost cursor" when in remote view.

Related bug:
Instant blueprint building does not work when force- and super-force-building items, even outside Remote view.

Steps to reproduce:
1. Enter editor mode
2. Hold an item in hand (not a copied item)
3. (Super-) Force build with item - > ghosts are created and not placed automatically


I expected the blueprints to be build automatically in all cases, as "Instant blueprint building" has been selected while in Editor mode.

To be clear, the both bugs are perfectly reproducible by me. The "not always" in the title refers to instant-blueprinting working for normal building outside remote view, and for all ways of placing blueprints that I tried.

Re: [Lou][2.0.28] Instant blueprint building does not always work in Editor mode

Posted: Mon Dec 23, 2024 6:49 pm
by Yodo
I saw 124805 and decided to add some more info:

For the second bug in the first post, I'm (super-) force building the entities (splitters) on normal tiles without entities, where normal building would work.

Both bugs occur in 2.0.28 as well.

Re: [Lou][2.0.23] Instant blueprint building does not always work in Editor mode

Posted: Wed Jan 01, 2025 5:29 pm
by Yodo
I found a related bug which might be causing the instant blueprinting to not work in remote view: 656839.

Re: [Lou][2.0.23] Instant blueprint building does not always work in Editor mode

Posted: Mon Mar 03, 2025 11:21 am
by Lou
Thank you for the reports.

These are not bugs, because it is ghost building not blueprint building (and as such should produce ghosts).

If that was the behaviour for actual blueprints, that would be considered a bug, but at least in 2.0.37 I was not able to observe this with blueprints.