https://www.roblox.com/games/3487742603/Work-at-a-Restaurant-Chicken-Shack-V1
I’ve added a patch script for multiple different FE crashers. Haven’t seen the servers being crashed since I added them.
I’ve enabled the fix for the following places. Let me know if you see anything weird.
4837595186
4586741827
3487742603
2747834912
4388574342
@ThePhantomG @zaytuls @Sudden_Demise @Nimblz @MetatableIndex
5 Likes
The fix for this has now been enabled for the whole platform.
20 Likes
I assume this fix is why I can’t drop tools anymore? Tool gets stuck to arm, then can’t re-equip. Any way
to make the fix less draconian?
2 Likes
This is a major problem for me. I can’t even parent tools to workspace from a LocalScript anymore. I hope they fix this bug. It’s been a major issue for me.
I submitted a bug report. I hope they do something about this.
1 Like
Thanks for responding. I’ve already implemented big workarounds, but what worked previously
on the client was:
tool.CanBeDropped = true
tool.Parent = workspace
With the new setup, not only does this not work anymore to drop, but now Unequipped also does not
get fired on the server. (If you parent it to nil on the server, then it will fire on the server.)
It seems that once you try to parent to the tool to workspace, FU bits seem to get set in the tool,
forcing a reconstruction of the tool to allow proper use in the world.
Sorry, this is intentional!
If you’d still like to have tool.Parent = workspace work from the client side, you should set tool.CanBeDropped = true on the server side.
Previously, in games where tool.CanBeDropped was false, exploiters could reparent their tools to Workspace (or anywhere else for that matter…). We now check tool.CanBeDropped before allowing the parent change to replicate.
10 Likes
Thanks for the explanation! I hope it’s been put in the documentation update queue.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.