Hey, I recently have seen a view games being leaked using saveinstance() and I am curious is there any way you are able to patch this? I have seen a few games patch this, for example…
Now Deprecated, save instance was used back when Data Persistence was used, Data Persistence was what came before datastores. SaveInstance() was apart commonly used back in the day to save things like models or physical objects with Data Persistence. Like most other parts of the Roblox API, it can’t necessarily be disabled. It only downside for exploiters is the fact it can only save Client Sided Scripts and maps. Basically, anything a local script can access. For the map, there’s not really anything you can do sadly. On the other hand, for the client scripts, you can try to utilize remote events, remote functions, and bindable events to minimize the amount of damage created by save instance().
Hope this helped and gave you some insight into save instance() and how you can protect against it.
It’s impossible to patch SaveInstance(), Roblox developers can’t do anything about it. Look at H0R1FFIC’s explanation on SaveInstance().
1 Like
How come that game I mentioned can patch it or detect it.
1 Like
Thank you very much for that info.
1 Like
Some developers try to avoid this problem as much as possible by checking when the client stops responding.
This works in part but detects connection problems in general and not only the use of saveinstance().
1 Like