What did you do?
- Tried to Pipette various Signals from a Combinator
- Place anything that yields a "Ghost" into a Chest
- "no-item" turns into a Request Ghost! (0m6s)
- "green-wire" turns into a Request Ghost! (0m14s)
- "spidertron-remote" turns into a Request Ghost! (1m6s, 1m15s)
- "parameter-0" turns into a Request Ghost (0m24s). This is semi-Expected, since you may want to Parameterize Item Requests in a Blueprint.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
Items which are not obtainable because they have the "only-in-cursor" flag would disappear when Left-clicking - similar to the Quality Signals (0m35s), Virtual Signals (0m59s, 1m30s) and Fluids (1m38s), or would not be Pipette-able at all like "item-request-proxy" (0m39s), "character" (1m02s), and other Unobtainable Items/Entities (1m20s, 1m22s)
Does it happen always, once, or sometimes?
Only when Pipette-ing from a Signal - does not work when using Alt+R/G/A (0m16s)
This is tangential to "no-item" item can be placed in Editor inventory (which is "Not a Bug") and Pipette does not work on all signals. I found that (some?) Items marked "only-in-cursor" can actually be turned into an unfulfillable Item Request Ghost if they are pipetted from a Signal, rather than using the Shortcut (Alt+R/G/A)
I do actually think that having "no-item" be usable as a Request Ghost is helpful, since it can be placed into Inventory Slots to exclude other Items from being placed there. I have previously used "deconstruction-planner" for this purpose, which occasionally leads to a mess if one is evicted from the Character Inventory accidentally. I am trying to determine if this is Intended Behavior which can be depended-upon in the Future.
Thanks for Reading!
