Currently, SavePlaceAsync on games is not working.
Here’s a list of games it’s happening on that I know of:
Expected behavior
Expected:
It works and duplicates a place
8 Likes
What error are you getting? You’ve provided 0 info here
1 Like
Saves the state of the current place. Only works for places that are created with AssetService:CreatePlaceAsync() or which have the API enabled through place settings.
Are these experiences created through AssetService:CreatePlaceAsync()? If not, this function won’t work 
1 Like
Hi, I’m not entirely sure about the backend.
It’s not even my games, to be honest.
They’re created using CreatePlaceAsync, but are not saving.
I heard though that apparantly there isn’t any errors.
1 Like
it only works half of the time when you spam it
hi hey, i’m the owner of wubby, one of the games mentioned. i’ve done a bit of research and apparently SavePlaceAsync() “works”:
it’s returning “true, nil”, as a result of a pcall() call.
apparently, roblox is INDEED saving the place, it’s just not publishing it:
this was 13h ago aprox (before the bug took place):
i’ve tried the spamming solution and it works half of the time. strangely, it has better chances of working on the command bar than in a regular script.
i’ve been using this function for 1.5 years w/o a problem and now it’s suddenly not working,
pls fix this, it’s affecting similar games ultra-negatively and i can’t do anything about it 
2 Likes
Thanks for posting this thread.
Yes, Blockate is completely broken now. Blockate has been using the SavePlaceAsync API for 7 years, and it’s based off a game created back in 2014 that originally used the API. This is a huge regression that breaks an API that’s been in used for 11 years.
This is very urgent as builds people make in Blockate no longer auto save. This breaks the whole point of building games that use this API. Until this is fixed, Blockate is going to be completely broken, and people’s builds aren’t going to save so this is a really bad regression.
5 Likes
Has Roblox changed how SavePlaceAsync API works? If so, is there another DevForum post explaining this or is it just simply broken? Genuinely curious.
Roblox changed it so SavePlaceAsync now “saves” the changes without publishing them. Here’s a screenshot from Version History showing that the versions aren’t published anymore:
It used to always publish the changes immediately, which is how live-building games like Blockate and Wubby worked, here’s another screenshot from Version History showing proof of the previous behavior of the API:
Without changes publishing immediately anymore, which is a regression none-the-less, building games can’t persist changes made to the places, which is how these kinds of building games have worked for 10+ years, since the API was introduced.
My bad - I thought hazel’s post explained it
4 Likes
Thank you all for the reports. We’re investigating the issue now to see if this was a regression, and if it can be reversed. In the meanwhile, does anyone know when this issue began?
3 Likes
I saw people in wubby start making reports yesterday (the first being 21 hours ago)
Hi all,
We have pushed out a fix, please could you try again and let us know if you still encounter the issue
10 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.