I was able to destroy myself, however I wasn’t able to move nor walk anymore.
1 Like
They might have changed that in the new PlayerScript rewrite, some games have the old PlayerScripts so it works on some older games
Did you just do :Destroy() on the player?
Yeah, it worked decently until that.
Try getting older versions of PlayerScripts from old uncopylocked games and put them where they belong
You’re using a custom leaderboard right?
I’m unsure how to grab old playerscripts.
I’m using the Default playerlist.
They’re under player scripts in some uncopylocked games (mostly in stolen games with exploits) but you can use those
1 Like
Sorry, this isn’t processing right through my head. Can you explain more? Inside of StarterPlayer then to StarterPlayerScripts?
1 Like
I’m unable to reproduce this server-sided. Calling Player::Destroy on the server still disconnects the player and renders their chat gui useless.
I was able to reproduce this client-sided, but the player is not actually removed from other users lists.
Player1’s view:
Player 2’s view:
Server’s view:
It should be (somewhat?) expected that doing something like this on the client wouldn’t actually disconnect the local Player. In order to make use of this, like I said earlier, you’d need a RemoteEvent that calls ::FireAllClients then remove the target player locally on each player’s client. However, this circles back to my other point:
This is obviously a hack which is subject to change in the future. So it should not be used for new work.
That is quite strange, on my friends screen it was actually visible
Is the command bar server sided?
They might also have changed a lot of stuff in their scripts in the past few months so I don’t really know why it wouldn’t work
The command bar is either client or server sided depending on which mode you are viewing in Studio
This is because it’s not intended behavior. Nor should it be intended behavior. If nobody makes a bug report writeup by the end of the weekend for it I likely will.
Don’t make a bug report about it yet.
I know games and admin systems which use this bug, it would be very hacky to work around this.
Yes it’s a bug, but it has existed for years and years, and has become more of a feature now
Reporting it as a bug also makes it so there’s no answer to the topic… since it wouldn’t be possible anymore
If they would fix it, I would atleast like a work around which they should make
There is an answer to this topic, and that is to create a custom PlayerList gui. And no it would not be hacky to work around. There’s absolutely no good use-case for keeping this bug as a “feature” other than for users to troll one another - because it screws with Roblox’s internal CoreScript code.
I’ll say it one more time. There is no good reason for calling ::Destroy on a Player but keeping them connected to the server. Anyone who’s doing this should know that such behavior is subject to change/removal.
With the player list he probably means that the player isn’t in the esc player list either, and the games I have seen that function in had the roblox player list, nothing different
There is absolutely no reason that a Player should be hidden from the PlayerList one sees when they press the ESC key. Users should always be able to tell who’s in their server or not by using that PlayerList
This was solved by a quite simple method but was somewhat fixed.
If you parent the character to nil on connected clients, it should work fine.