No… you don’t. There is no issue with my script. I am just asking if this is the most efficient way to do what I am doing.
My bad, I don’t even know what nil is so I shouldn’t have said
Uh, it’s quite udmb what you doing.
I don’t understand why you even do this.
Just connect when player leaves in the PlayerAdded event and any event you need there.
Could you elaborate?
PlayerRemoving is very unreliable and does not always fire.
PlayerRemoving always fire…
local e = {}
game.Players.PlayerAdded:Connect(function(p)
local changedevent
changedevent = value.Changed:Connect(function()
end)
e[p] = game.Players.PlayerRemoving:Connect(function(pl)
if (pl ~= p) then
return
end
--do whatever u want
if (changedevent) then
changedevent:Disconnect()
end
e[p]:Disconnect()
end)
end)
1 Like
The reason PlayerRemoving doesn’t fire is because the game is closing and it dosn’t always register all the events with closing time.
Just like in the post you’ve posted, the fix to this is adding a game:BindToClose function.
Would this be better than just breaking the loop if the player doesn’t exist?
I’ve personally never had an issue with it. It catches most of any event fails. If there is another reason as to why playerremoving doesn’t fire I wouldn’t be sure of. most loses are causes because of the game closing.
I’ve tested this multiple times in studio, game:bindtoclose always seems to catch it. without it, it would rarely save at all.
But if both of my loops are broken when the player leaves (player==nil), there would be no more code in the function running. Wouldn’t that be the same as just disconnecting the function?
I would say it would be inefficient to do that, depending on what your loop does it could actually cause latency.
Having an event that fires when it needs to is way more efficient.
How so? What would cause the latency?
Have you had any problems prior with PlayerRemoving? If so have you actually tried BindToClose? What are the results?
Lets say you have a loop constantly looping through a table and checking values in it, the more it loads the more it has to do.
I personally like to keep the same category of loop in 1 single loop, and creating a new loop for every player to check if it exists just seems far more inefficient and stressing.
1 Like
Depends there might be an inbuilt event for what your doing, what value are you constantly checking? (Events would be performant since the run the functions connected to it ONLY when the thing happens internally.
1 Like
Nothing in the loop would run if the player left. The first line makes sure the player is still in the game. No code would run after the player left.
Would making sure the player exists really have that much of an impact on performance?
My anti cheat constantly checks velocity, position, and checks for noclipping.
Actually there’s no event for walking, so for constantly checking you can do one optimization don’t run the checking code if the previous velocity is the same as the velocity now, for the velocity checks.
It only doesn’t fire if the server is shutting down, and it’s rare to see it not fire even if the server is not shutting down therefore it’s reliable.
Still not fully reliable. I am pretty sure it is not fired if the player loses connection as well.
It is fired when the player loses connection.