Not sure if this issue existed prior 4.13 so making new post on it.

From what I have seen, if you have an object in a container, and the container is open, if you have a script that calls to make object inaccessible, the object in question, does vanish. However if you look at the container again, the object comes back and can be interacted with.

During the script process, if you remove the object from its parent and then make it inaccessible, then the desired effect works. Looking at the container does not bring the object back into the game.

Removing object from parent can seem like a viable work around, or maybe this was the design intent. However the issue I see if during the game development, you cant seem to always determine what the parent object may be. This will come into play, when a player picks up a bag and stores items into the bag to help clear up his inventory.

I uploaded an example asl file.
Grey Goose has 2 shots, shot1 will be removed from parent, while shot2 will not. You will see different results.

Thanks,

Thanks, I'll take a look. It probably existed before 4.1.3 (as I don't think I've changed anything in that area).

This is a limitation of how containers work in Quest 4.x. When an object is inside another one, it's not "really" inside it as far as Quest is concerned - it's in the parent room. If the parent object is closed, then the child object is inaccessible.

It's all much more sensible in Quest 5.0, but for now I think you'll have to work around the issue by moving objects to a different room if they're not supposed to be interacted with.