You would have to run several traces to determine the impact points all around.
There are nodes to check an area like you want. Nor can there be really.
A viable alternative is to make the container box have 6 colliders, one for each side.
Then you can know an object is inside it when the container overlaps, but the external ones do not collide.
In practice, if you have an actual box to trace against, running a line trace from the object would be faster.
The difference though is that the trace is a single point, and tracing a sphere or a box ends up costing more than having the container have 6 extra colliders.
The fastest possible way is to just do the math.
Collide with the container.
get the container bonds and x2 for it’s size.
get the object location. get the box size of the object.
do the math to check that the box is contained based on those parameters.
No traces. no bs. and even a mobile CPU will complete the calculations in milliseconds…
It also works from engine bounds, so it’s probably more accurate than a single line trace.
You have to check each vert of the bounding box. that’s 8 calculations per object.
16 calcs for 2 boxes…