Why does it matter where this issue was encountered? If people can freeze and crash people’s games via an animation, all you are doing by stopping it is playing cat & mouse with the exploiters. RejectCharacterDeletion shouldn’t be the only networking security feature we have… just a thought.
My assumption is that it possibly matters for triaging how exactly the crash is caused; I doubt the goal is to just block/fix that particular experience.
Oh yeah I totally get that. I’m just saying that we need more networking features that entirely prevent certain exploits.
Rejecting a character from deleting its body parts kind of feels like a joke.
They can’t delete their head, so instead they will change their walkspeed. They can’t delete their humanoid, so instead they will change their gravity. Oh and then if they patch those, they can just hook meta method on local scripts and completely ruin games that depend on local scripts. So on and so forth.
That’s why I’m trying to encourage them to focus on that and not things that play cat & mouse.
It should get to a point where there’s enough networking features devs can enable that exploiters no longer have complete control over their client like they do currently
Even when they finally introduce the Server Authoritative Characters that they have discussed a few times, they will still need to fix problems with this system because games released before will depend on it. I’m not sure where you’re coming from with this, you’re sort of saying that needing a way to test fixes is a bad thing?
Surprised that this can even be done at all. Roblox should automatically reject animations that have invalid animation data from being replicated to clients. The server should ensure that it rejects data that can crash clients. That is the whole job of a dedicated server infrastructure
This just feels like Roblox failing server networking 101. This should not be something that exists on such a large platform
No. It’s fine that they want to know where this issue occurred… it’s not fine that they didn’t add anything to the message implying that they are working on anything that will stop this vicious cycle of them patching a single crash animation when the exploiters just end up discovering more of them to exploit. @WheretIB should have said something like:
Thank you for the report.
It would be useful for us to know the experience where this issue was encountered.
We are working on not only fixing this issue… but also preventing future incidents from occurring so that exploiters cannot discover new animations that could crash servers at their free will.