Video of the issue: Error shown at 2:37 after long timeout
What I have tried:
I contacted Roblox support before, but tech support only answered it.
Checked VPN and firewall
Removed all plugins.
Reinstall the studio.
Restarting PC
I used another wifi but still the same.
Created a new experience and created a new place with CreatePlaceAsync(). Try to publish changes from the studio and return with the internal server error.
I’m using Windows 11., publishing in-game using SavePlaceAsync() works. Earlier this year, I was able to publish updates from the studio without any issues.
hi. thanks for getting back to us, we looked into our system and found that it seems place 18940209498 was created in game using createPlaceAsync(). Can you confirm that you are only experiencing issue saving from team create sessions places you created in game this way?
We have a rule that places created that way can only be updated in game using SavePlaceAsync(). In creator dashboard or studio, you cannot open those in game created places in studio for editing. But I found that in roblox.com you could, and we acknowledge thats a bug given the current rule. We are not sure why it worked before but that is perhaps a bug. That being said, I would still like to know what is your use case of editing a game created in game? Also where did you Thanks.
It appears that trying to publish/save to any place created using createPlaceAsync() will throw this internal server error. It used to work before without any issues (as long as team create was disabled). However even with team create disabled this error is occuring.
I like to publish to places created using createPlaceAsync() because I like to build stuff in game with tools and then make changes in studio (usually in scripts). Unfortunately I can’t publish my changes anymore from studio and would really like if this was possible again.
This was always possible since the creation of createPlaceAsync(), and not being able to directly publish/save to these places from studio is disappointing.
The only workaround is to go through the entire process of creating another place again using createPlaceAsync() and then having to teleport to the newly created place, which is such a hassle if I just want to make small changes. And doing this means the created places tab will fill up quickly with old places that are useless just because I can’t publish to them.
hi sorry for necroposting but this has become quite of an issue on my side
my game Wubby uses createplaceasync/saveplaceasync to create/save worlds made by my players. recently, a moderator accidentally cleared a world’s save data and i’m trying to revert it using the “version history” feature roblox has. every time i try publishing the changes i reverted roblox goes “nope!” :3
oddly enough, this somehow used to work like a year ago but i guess it stopped working?? idk it doesn’t work in my testing realm either.
some time ago, you could actually workaround this publishing bug by disabling team create??? idk how this was a thing but it used to work, nowadays it doesn’t work anymore.
could you pretty please fix this? it has bothered me for so long and i wish that this gets patched eventually so i can revert some worlds that my player base messed up big time :3 thank u
