Thanks for this code very useful. But I keep getting {“code”:3,“message”:“API Key has insufficient scopes.”} when the program cycles through all the places in my universe. Could I get some help troubleshooting?
1 Like
From the error message it looks like your API key is not configured correctly.
Make sure your key:
-
has place management permission:
-
has the permission to manage your game:
-
has write permission to your game for publishing:
Let me know if that helped.
1 Like
It was an issue with my IP address but I figured it out. Thank you
2 Likes
This is really good thank you, but I keep getting this problem
1 Like
Make sure the API key is enabled and has not expired (in your creator dashboard), or generate a new one.
2 Likes
I have done all that but it still brings up the same error, could it be because I have my Experience inside a group?
I found out that it was because of the group, THANK you for the code. It genuinely helped a lot, but if there is a way to make it work with the groups, please let me know.
1 Like
I also use this script for group games and it works.
Make sure the API key was generated using your group’s profile in the creator dashboard, like below.
1 Like
Thank you so much for creating this and sharing it with the devforum. You have saved me so much time!
For some reason every time I try to use this, it doesn’t actually publish the places, but there aren’t any errors or anything. It just says it published the place, but it has the previous version number in the “published” print instead of the new one, and every time I try to re-do it, the version number stays the same. I checked to make sure the cookie and the API key were set up correctly and they seemed fine. Any idea on what might be the problem here?
1 Like
The script did run fine.
Did you check in-game to see if changes you made have actually been applied ?
Because I know that when you try publishing a place that is the same as the latest version and that this version is published, the version number is not incremented (so not published again, as it’s the same place).
Also make sure you used the “Update all” feature of packages before running the script, otherwise, no changes will be present so the version number won’t change.
1 Like
Oh, that was the issue! I always only just publish the packages and have them set to “auto update” in all the places so I don’t have to update them manually, but it seems like that only applies the changes once you actually open the places. Thanks for the help!
2 Likes
Works great, would recommend. Thanks!
1 Like
Probably too old to ask, but would there be any way to do this in java? Been trying for a while and havent been able to whatsoever.
It’s definitely possible, as long as you can handle HTTP requests, download and upload files.
I’ve tried quickly in Java but I have a lots of trouble getting it to work because of my poor knowledge of the language. What’s blocking you ?
1 Like
For me its the fact that attempting to update more than 3-4 places within a couple minutes doesnt actually publish them. Its really annoying for me to mass update if half the places dont get updated.
I tried this in java, and javascript. It still happens.
I also noticed this occuring in the python code as well.
Are you saying that the script first works for a few places, then stops working for the rest of places you are publishing ?
Could you send a screenshot of the output using the Python script ?
In my game, I have 11 places to publish, and it always works.
Make sure you use the “Update all” feature of packages before running the script by the way.
2 Likes
I can describe it, If you have discord though I can add you to make contacting easier.
Lets say the places version is 11, and I want it updated to 12.
The place sometimes does update, and returns {version:12}, but sometimes it returns {version:11} instead, showing that it didnt update.
1 Like
Someone had the same thing here: Publishing all places of a universe after package mass-update - #13 by homermafia1
Basically, it happens when you try publishing a place that is the same as the latest version and that this version is published already.
So make sure you used the “Update all” feature of packages before running the script, otherwise, no changes will be present so the version number won’t change.
Interesting, thank you!
“but it seems like that only applies the changes once you actually open the places. Thanks for the help!” To quote that person, I wish roblox made this not the case however.