Noticed it after I tried editing a CameraModule. I don’t know why my Player Instance got there, if it’s an update where the dev can edit their player in studio, but It is a bit annoying because I can’t edit starter player camera script
That Player instance is not a new Studio feature that lets developers edit their own Player. It is most likely a runtime instance created by Roblox Studio when you are testing the game.
When you press Play/Test, Roblox creates a Player object inside the Players service to represent your test player. You cannot delete it because it is controlled by the engine, and it will disappear when you stop the test.
I know, but the problem is that i stop the test and the instance persists and can’t be deleted and it just. Even after reopening studio it’s still there
That’s normal afaik, it’s always been there. It doesn’t affect the game nor saves.
1 Like
game.Players.Dfzoz:Destroy()
run in command bar
your player is probably there because something called Players:CreateLocalPlayer()
This can also happen if you’re in a Team Create enabled place, where, you know, you’d have to connect to a non-local server
Check if you have any plugins or scripts that might be creating it, because a real Player object normally cannot be saved inside the Players service. Try disabling plugins and opening the place again to see if it disappears.
It’s a persistent instance of Team Create enabled studio places. It doesn’t affect anything and it isn’t published with the place.
The only way to “Destroy” it is setting .Parent = nil, but it will disconnect the said user from the Team Create session.
It doesn’t impact you anyhow from being there, and if you think that it does - you might be misunderstanding something.
Yeah, it was team create, thanks a lot. It seems like the problem for the playercamera was actually server authority, which changes how the player module works
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.