Grab smuggled items drop themselves on root
Describe the bug?
when taking an item from one world to another via grab smuggling the item does not spawn in the slot above your user root, but in fact on root. this is fine for grid worlds or worlds with active cleanup systems in place that scan for items on root but for worlds without this that are a wip or say you are in a car/spaceship this can be very anoying as now your item is sticking to global space possibly km behind you by the time you get out of the vehicle/ship
To Reproduce
grab smuggle something when your parented to not root
Reproduction Item/World
n/a
Expected behavior
items spawned in to always be parented to the same slot as your user root is parented to
Screenshots
No response
Resonite Version Number
Beta 2025.11.21.1164
What Platforms does this occur on?
Linux
What headset if any do you use?
No response
Log Files
reddspc - 2025.11.21.1164 - 2025-11-23 22_34_55.log
Additional Context
No response
Reporters
redd56
Hello! Here are the results of the automated log parsing:
| Version | OS | CPU | GPU | VRAM | RAM | Headset | Plug-ins/Mods | Renderer | Clean Exit |
|---|---|---|---|---|---|---|---|---|---|
| Beta 2025.11.21.1164 | Steam Runtime | AMD Ryzen 7 5800X 8-Core Processor | Navi 32 [Radeon RX 7700 XT / 7800 XT] (rev c8) | 31.36 GB | 62.72 GB | SteamVR | no | Renderite.Renderer.Unity 2025.11.18.1147 (2019.4.19f1) (WindowPtr: 0x30080 | ✅ |
This message has been auto-generated using logscanner.
I have a hunch this is due to the re-parenting behavior of the Grabbable component. It remembers what slot an object was previously parented to when grabbing it, so that it can restore the object to that hierarchy once released. But when a transient object is moved into a new world, any stored slot references of the previous world would become null. I would have to test this, but I imagine a possible solution to this could be defaulting to the local user space as the re-parent target in this case.