Will this become integrated as an analytics stat?
how would we know when the game is shutting down exactly? like after the task.wait in the function?
5 Likes
The documentation of BindToClose states that “Multiple functions can be bound using BindToClose if it is called repeatedly. The game will wait a maximum of 30 seconds for all bound functions to complete running before shutting down. After 30 seconds, the game will shut down regardless if all bound functions have completed or not.”
8 Likes
It would be awesome if this could be added to our analytics as well. Would love to see a chart of average server lifetimes, as well as a display of which of these close reasons happens more often. It could be an actionable signal if we were to see high numbers of OutOfMemory, for example.
15 Likes
currently looking for the “omg i’ve waited for soooo many years, finally my life is fulfilled!” ahh comment
8 Likes
There’s a Memory Limit? What’s the Memory Limit even?
5 Likes
Just to clarify, When you now bind a function using BindToClose, The game server itself will pass the enum to your bound function as the first parameter. It’s not necessary for you to pass anything in your own code.
Previously creators didn’t have direct information as to why the server was closing.
17 Likes
Memory limit for most servers is 6.5GB, whilst for larger (600?+) servers it’s 12GB.
12 Likes
Thanks!
We’re hoping creators find this useful for a variety of scenarios! Some experience developers who tested this feature have also found this helpful for tracking down memory leaks by collecting information for servers that shutdown due to the OutOfMemory reason.
10 Likes
It’s not part of this update but it is something we want to consider for the future!
8 Likes
W update. This will help track why my servers keep crashing
6 Likes
This announcement also provides some information around game servers and memory limits: Increasing Server Memory Experiments
8 Likes
Thanks a lot! This is such a good change! Our game had a problem in the early days where memory leaks caused server crashes. Everyone in the server would lose their hard-earned winstreaks if they were mid-game during a server crash.
Now, this seems to never happen, but if it ever does, I can be confident that they won’t be recognized as having “left the game during a match” and losing their winstreak, because BindToClose automatically removes the mid-game status in our game.
6 Likes
This helps improve the migration feature, it allows us to trigger migration teleports when necessary.
It helps, but not 100%, and I appreciate that this was added. It’s very useful.
8 Likes
Just want to throw my hat in the ring to support this idea.
This is absolutely the main use case for us and, pending an official analytics integration, all I see us using this Enum for is passing it to our own analytics to get this data.
9 Likes
Pretty cool, I like this kind of additions, keep it up 
5 Likes
This is a great update! What happens if a private server owner shuts down their server? Does it count as a developer shutdown or something else
5 Likes
I would really appreciate if BindToClose function would return RBXScriptConnection, so I can disconnect the event. Right now it returns () (AKA nothing), and there seems to be no way of disconnecting it.
My library allows to start a service, and stop the service. If the service is stopped by the script, it can’t disconnect BindToClose and will most likely result in a memory leak.
4 Likes
I don’t know about BindToClose returning an event, however, for your issue, I’d make your service store the methods in a seperate table that can be accessed from DataModel:BindToClose and just add/remove methods from the list when necessary.
And, in the BindToClose method, you can just iterate over the list and call each method. If the list is empty, nothing happens
function service:BindToClose(identifier: string, method: (closeReason: Enum.CloseReason) -> ())
methodsList[identifier] = method -- assign the method to the list of methods
end
function service:UnbindFromClose(identifier: string)
methodsList[identifier] = nil -- remove the method from the list
end
-- ^^ This is a more simplified version of what I mean
-- (a seperate script)
-- Run each method from a BindToClose callback
game:BindToClose(function(closeReason)
for _, boundMethod in methodsList do
task.spawn(boundMethod, closeReason)
end
end)
But I don’t know if this would work for you
5 Likes