Setting a player's parent to nil closes the Team Create session with an error

[PosFind (dev)]

Reproduction Steps

1. Open a baseplate with Team Create on.
2. Find the player with your name.
3. Open its properties.
4. Click Parent property and click the cross.

Expected Behaviour
An error, possibly a locked option for its parent property appears on the screen, but the game keeps running as normal.

Actual Behaviour
The session disconnects and an error pops up on the screen after failing to reconnect:

Issue Area: Studio
Issue Type: Team Create
Impact: Low
Frequency: Always

[SubtotalAnt8185]

@PosFind

An error, possibly a locked option for its parent property appears on the screen

But how? All those scripts that remove the player from the game will break.

[PosFind (dev)]

I mean an error like The Parent property of Player is locked. It wouldn’t allow it to change, like a service.

[yipiokay]

Thx for reporting this! We are considering ways to provide a warning here for better user feedback, but for now it is by design that we do not enforce this restriction in Team Create at a per property level.