Snap slot "place_only" items and suggestions

[OvercastInteractive]

I think it would make sense to add the option of "place_only" to prevent the player from retaking placed items from snap slots. It certainly makes sense from puzzle design perspective, as there would likely be more one-off scenarios, such as placing the correct statue on a pedestal to open a door or whatnot and not allowing the player to pick it back up and take it with them.

I was able to get this working by duplicating the battery pickup twice, one as my own "placed_battery" and another as the drop scene battery from which I removed it's carryable and pick up components, and by duplicating the battery inventory item pd and plugging all of the references in the Laboratory scene.

I have a couple of ideas to get around this:

1. Remove the CarryableComponent and PickupComponent of the spawned_object upon placement, which produces the same result as my explained workaround (and avoid the asset duplication and referencing)

2. Perhaps even better, instead of using the drop scene of the expected item, have a separate @exported drop scene variable which would be used if populated, else use the expected items drop scene as it currently does. This makes even more sense, as you could do things like snapping an unlit lightbulb pickup into place and your custom drop scene could instantiate a lit lightbulb, or slot a lever pickup into place, which instantiates a separate lever asset with a cogito_turnwheel and so on.

Or perhaps offering both makes the most sense?

Thoughts?

[Phazorknight]

I get what you mean, it's actually already implemented in the Legacy Demo scene:

The CogitoSwitch SocketForDiamondKey works as you described. It simple hides/shows nodes when the item is "placed".

Looking more into the snap_slot script, I'm actually running into a few issues when using it for items, the main one being the reference to the spawned cogito object bing saved/loaded correctly and tying it to the snap_slot. Using an "included node" inside the slot scene would eliminate this problem so I might remove that functionality from snap_slot and refer people to use the CogitoSwitch instead. (and cleaning that one up a bit)