[2.0.28] Instant blueprint building does not work when ghost is in cursor

[Yodo]

Steps to reproduce:
1. Turn on instant blueprinting.
2. Add an item to the quickbar that is not in your inventory by setting the hotbar filter.
3. Now select that item from the quickbar and build with it -> ghosts are built and not "revived".

I expected the ghosts to be revived instantly.

Does this always happen:
Yes

Notes
This happens even when the player is not in remote view.
I think this may cause instant blueprint building to not work in remote view, see 123728.

[Rseding91]

Thanks for the report however that's working correctly. Ghost building is not blueprint building. Blueprint building is when you hold a blueprint in the cursor.

[Yodo]

Okay, is the following behaviour then a bug? (items running out in editor mode)
This is what caused me to notice the behaviour in my previous post.

Steps to reproduce:
1. Turn on instant blueprinting.
2. Add item to inventory and quickbar.
3. Build with the item until it runs out in your inventory.
4. Re-select the item from your quickbar (not using pipette).
5. Build with the item.

What happens:
The item is not replenished in the inventory and the player starts placing ghosts that are not instantly revived.

I expected the item to replenished or the ghosts to be revived instantly.

Note that pipetting to "re-select" the item will cause it to replenish.

PS. I didn't get a notification for your reply, I think the "subscription" is cancelled when the post is moved to a different category in the forum, which is a bit annoying.
Edit: it seems that I'm not automatically subscribed when I create a new topic, at least for the bug reports forum. Since replying does automatically subscribe (outside bug reports at least), this seems inconsistent.

[robot256]

That is the same as your original post. As Rseding said, if you want ghosts to revive instantly when they are not part of a blueprint, you will need to use a different setting. I don't remember if there is a built in setting for instant ghost revival, but I know it is an option in some of the editor/creative mods.

Cheat mode intentionally allows you to place ghosts if you do not replenish your inventory with pipette or the crafting menu. If you want to place entities without worrying about inventory at all, use editor mode.

[Yodo]

I am using editor mode. I reproduced both behaviours it in a new world with "map editor" as well.

The difference between the two behaviours is that in the first, the item was never in the inventory, while in the second, it was, but it runs out. The second case can happen even if the player is aware to avoid the first behaviour.

[robot256]

If you select entities from the "entity placement" GUI in editor mode rather than the quick bar, they never run out.

[Yodo]

Ah, the entities tab in the Map editor window (top left by default) - I never used that that much. It does seem like it doesn't run out, but using that makes it a bit harder to access my upgrade/deconstruction planners and blueprints, as a lot of the usual keyboard shortcuts don't work anymore (creating new planners/blueprints does exit the menu, but that's about it).

Edit: I've though about it for a bit, and I think I'll keep using the inventory. Being able to use the quick-bar and access my blueprints and planners is just too useful to me. I'll just have to make sure to always pipette an item to get it into my cursor.

[Yodo]

I found a workaround for the items running out: in Editor mode you have "infinity filters" where the logistics section usually is, and setting requests for items here will keep them in your inventory. But if the request is low, the item can still run out, but I haven't found any problems when requesting 50. Smaller amounts like 10 also work usually, but not when moving and placing entities quickly, so for items with low stack sizes, like rocket silos it can still be a bit annoying (unless you expand inventory size with a mod).

[Muche]

in Editor mode you have "infinity filters" where the logistics section usually is

Thanks for making me revisit Editor mode's settings.