What will happen to the documentation for all of these? Will it be removed completely like it had never existed or will it have a warning that it no longer works with a link to this post? Or will it remain the same as it currently is?
Also, with Player:SaveInstance(key, value) and Player:LoadInstance(key) methods does this mean we will be getting a built-in serialization method for saving instances with the new Data Store improvements?
Happy Scripting!. I, unfortunately, canāt build with datastores.
Not gonna lie: I didnāt know this was a thing.
I honestly forgot that these were still a thing.
I heard it was useful for game copying, glad that itās FINALLY copied!
Most exploiting tools already rewrite the function anyway, so I donāt see that problem going away anytime soon.
Wow. May this service Rest In Piece. I remember using it in 2018 when I was still trying to learn how to code, but I didnāt know it was deprecated. 
epic update, it was very painful to use the dataStore service, and now, this api is insaneā¦ no longet datastore service, but a data that can be scripted using a simple function. this is awesomeā¦ GG!
I think you misread the topicā¦
Roblox is removing the Data Persistence system in favor of DataStores, not the other way around.
You misread the topic. The function is losing its functionality in favor for datastore service. Also you should be using DataStoreService anyways because it is more reliable, has more functionality (ordered data stores, global datastores, etc.), and is being updated regularly by ROBLOX. Also, soon there will be support for backups. And Iām not sure about the backend stuff behind the two but if you wanted data to be saved for sure, use DataStoreService.
Pretty sure what youāre thinking about is DataModel:SavePlace. The stamper just inserted models and SavePlace published changes. However, SaveInstance() was used for games such as WTRB to save any instance/object and was limited by the instanceās DataCost.
However, to save an instance now, you are required to use a script that converts an instance to a different format that can saved in DataStores such as a table.
could this mean faster loading? if were getting a datasave upgrade id assume so. would be interesting to see where this goes.
RIP to everything that people made in the stamper tool building places. (If Welcome to Roblox Buildingās closure didnāt already put the final nail in the coffin)
The removal is understandable though, data persistence was very quickly replaced with datastores. Funny how almost nobody here knows what DP is lol.
Iām still waiting for that one guy to be like āMy game solely runs on this service!ā
The first and last time I used Data Persistance was in 2014 when I was a begginer scripter! I canāt say I totally forgot about it because I remember its ability to save instances! Later I learned that you could nest tables and make your own instance savesā¦
I wonder if everyone at Roblox just forgot that this once existed for years and noticed now lol
Try this:
function getSaveableColor3(color)
return {r = color.r, g = color.g, b = color.b}
end
function loadColorFromDataStore(t)
return Color3.new(t.r, t.g, t.b)
end
Data loss is developer error, not something Roblox has to fix (it is perfectly possible to write loss-free datastore code), maybe have someone proficient proofread your datastore interaction code or use the #help-and-feedback:code-review category.
You donāt need a module as complicated as Datastore2 to do it.
This seems to be very sad. Will there be a replacement for this feature?
There has been a replacement for half a decade. DataStores.