It appears to be possible to play a ~30 sec sound after the Roblox client is closed (the way it’s closed literally does not matter - it’s possible to make it so it always runs whether you use Alt F4, close button or the leave button).
Some games use it in really fancy way which seems awesome (eg. Pressure - Roblox which plays you a “good luck out there” / “goodbye” sound but it could become easily abusable and scare the player out of nowhere (eg. 15 secs of silence and then some sort of insanely loud or otherwise inappropriate sound).
Roblox client is already in “closed” state so it could be hard for the player to spot the cause of the problem (and could be otherwise misleading for them). Imagine a player leaving a game because it’s inappropriate but the game takes the opportunity to play some inappropriate sound for ~30 secs after the player already leaves - it’s unacceptable.
Expected behavior
I believe it should not be possible to play the sound after the player attempts to close the client.
yeah, i’m pretty sure thats before you disconnect and all. most of the times freezes after you leave a laggy game or something if you are on a lower end laptop like i am.
also i’m pretty sure its aswell a toggleable feature on the Sound class on roblox, with the property PlayOnRemove
It only happens on laggy games where it takes ages for the Roblox client to fully exit. The window is closed but if you look in task manager, the Roblox client is still there running.
FYI, this is used a lot by developers and it’s purpose is to play sounds when they’re destroyed (if you only want to play them once and then get rid of them to clean them up), but this could be the issue as maybe the engine calls :Destroy() on sounds when a player leaves. However, I highly doubt this as sounds that were already playing, like music, continue to play when the client is closed (without restarting or anything), so it’s probably some other cause.
@bvetterdays
It’s not PlayOnRemove-related. Sounds that have this property on do not play when the client leaves.
This issue is triggered in another way that lets a sound be played after nothing game-related still exists. @TaxFraudBruh
The mentioned issue is also not caused by laggy / low-end devices, but indeed it may also happen on laggy games.
It is fully replicable (doesnt depend on “luck”, device or some other performance variables) so you are able to consistently play a 30secs sound after the client is already closed (no matters whether you use alt f4, close button or the in-roblox menu Leave button) and does not appear in the task bar anymore, hence this could be considered a vulnerability (and due to some other consequences - a DoS) [more details are shared with admins via private message].