Can't save place in roblox studio that was created with CreatePlaceAsync() API

Help and Feedback Scripting Support
#1

Hello,

I’m not sure if this is supposed to be like this or if it is a bug I should post in studio bugs so I thought I’d ask here first.

Whenever I try to publish/save a place that was created using the CreatePlaceAsync API I get the following errors:

  21:59:28.364  Saving to Roblox...  -  Studio
  21:59:32.052  Server Save Failure: HTTP (400): Bad Request  -  Studio
  21:59:32.062  Game World 1 save failed.  -  Studio
  22:02:59.260  Server Save Failure: HTTP (400): Bad Request  -  Studio
  22:03:08.361  Sent message to server to publish.  -  Studio
  22:03:11.976  Server Publish Failure: HTTP (400): Bad Request  -  Studio
  22:03:11.986  Game World 1 publish failed.  -  Studio

(saving/publishing works fine on the normal places created manually (e.g. the template place))

Does anyone know if it’s normal behaviour that you can’t save/publish these types of places in studio or not?

2 Likes
#2

I finally found a post from 2014 and apparently it’s supposed to not work

1 Like
#3

Hello KingBr1ck,

If you’re still facing the issue, I came across the same thing.
For whatever wild reasoning TeamCreate was turned on preventing me from publishing and saving my progress made on a dynamic server.

I assume this had to do with the teamcreate session and the api trying to overwrite each other and giving bad requests, after turning it off and restarting studio i was able to save & publish again.

1 Like
#4

This is a bad bug for my game, Blockate, a world-based building game. I want to experiment with adopting new Roblox features that are locked behind non-scriptable properties, but in order to do so I need to be able to republish places in my game, which there are millions of (2,199,941 as of writing). I’d love to just be able to use the open cloud APIs to modify these properties from a backend in order to gradually migrate to using newer Roblox features like StreamingEnabled and new lighting, but because of this bug, I’m unable to since places created with CreatePlaceAsync can’t be published. Having this bug fixed, or properties no longer being non-scriptable would be great.

1 Like
#5

If i’m not mistaken you should be able to change the lighting serivce with the devloper console accessable ingame using F9

If the bug is still happening after turning off Teamcreate in studio you would have to create a new post on the forum and see if other people could help you with your issue as this mehtode:

should have fixed the issue