3D transition Phase B: real item.gd/stand.gd

scruffydude commented

2026-10-03 10:33:41 -04:00

Owner

Writes fresh 3D item.gd (RigidBody3D) and stand.gd (Node3D), porting the exact item_id/stand_id/group-membership/placed_changed-signal architecture already proven in the 2D version. Only the trigger mechanism changes: a public try_snap() method called from player.gd on drop (Phase A's carry system), instead of being called internally from a mouse-drag handler.

Test room (player_test.tscn) gets a matching Stand added so the full pickup->drop->snap flow is provable, same kind of proof the 2D version got for #3.

Win-counting/area-controller work stays out of scope - thats Phase C/D.

Writes fresh 3D item.gd (RigidBody3D) and stand.gd (Node3D), porting the exact item_id/stand_id/group-membership/placed_changed-signal architecture already proven in the 2D version. Only the trigger mechanism changes: a public try_snap() method called from player.gd on drop (Phase A's carry system), instead of being called internally from a mouse-drag handler. Test room (player_test.tscn) gets a matching Stand added so the full pickup->drop->snap flow is provable, same kind of proof the 2D version got for #3. Win-counting/area-controller work stays out of scope - thats Phase C/D.