Players dont go back into the game.Players

[waves5217 (waves)]

@HugeCoolboy2007

if you parent an Instance to nil, that doesn’t necessarily mean that it can’t be brought back

^^

Just for some Roblox history @pumpkyrofl, it was possible to utilize this on players until 20th of April this year.

Disconnect Player on Removal from DataModel

[Update] April 20, 2023 [Update] November 30, 2022 Hi Developers, Currently, removing the Player object from the DataModel will not result in a disconnect. This results in broken/unusable behaviors because complex systems in the Engine/Roblox rely on a Player Instance existing for each player. To address these concerns, we will be rolling out a change on November 28, 2022 that will disconnect a player if their corresponding Player object is removed from the DataModel (on the Server or Cl…

Before the update that disconnects players from the data model, it was possible for devs of famous games to hide in nil and observe/investigate/… Sneaky lol.

@PANDASonNOOB

Player leaving leads to the player object being completely deleted

Players don’t get disconnected (right away?) if you don’t disconnect manually. I’ve done a lot of tests, and came to the conclusion that it’s great to have the following clear the player.

Players.PlayerRemoving:Connect(function(player)
	-- clear character
	-- save data
	task.wait(10) --> some reasonable time
	player:Destroy()
end)

[VSCPlays]

The solution became (post deleted by author) so why not solve the topic?

I do believe putting the Player instance to nil would kick the player, so that’s a bad idea

[ali432567 (Alizabeth)]

I did that by accident I have been rate limited for 6 hours after that I will undelete it if I can but the solution was that you can’t parent it nil without kicking