This optional functionality would be really appreciated when publishing games.
I can give a very solid use case for such a feature. Some developers, such as myself have different variants of our games within our game’s universe. For example, a PC version, a mobile version, a console version, all contained within the same universe.
The place file which I publish to each of the place slots is identical. Within the game’s code it detects the current PlaceId and changes stuff to suit the platform. This saves me from having to maintain three varying place files. The issue is I have to update 3 different place slots every time I make an update. It’s tedious and it’s daunting. Having an option to publish a place file simultaneously to multiple place slots would be a godsend.
I’m a bit confused about the use case. Why are you publishing one place to three different place slots? Why not just have one place slot that accepts players from all your supported platforms?
Think about in games that are more competitive where you want to separate different platforms apart to prevent unfair competition amongst players.
If you think about a mobile player vs a PC player in a game where they have to shoot each other with a laser gun or something, the mobile player will easily be at a handicap in almost all circumstances.
It sounds like the solution to this is to have per-platform servers. Not a hacky workaround using places. That would split your visit count, revenue reports, etc.
Perhaps, but I was just using that as an easy to understand example of a use case. I have more use cases, and even one I’m facing right now personally where having this as a feature would greatly improve my developing experience.
For me personally, I have a testing place and a live server - quite often I’ve needed to upload to both place files. Having a check box next to each place file in the upload box to select the ones to upload would be really useful!
This would actually help me a lot. I have a lobby server and the main game server, and their place files are identical. Being able to upload the same place file once would be nice.
Well normally I make changes and upload to the testing place to test, but quite often, if I make a change on the testing place, I want it to go live on the main place as well so it would just be useful to have this feature
Five years later and this feature is still request amongst developers.
As someone who uses the same code and builds in multiple places under the same experience, this would be such a boost to the quality of life when it comes to the workflow of my games.
We have a competitive boxing game that has elo servers! We use different places (but with the same code) to allow players to find their friends, but let it be separated by elo server. We do matchmaking in a separate way, but this lets us do social stuff.
Right now, you cannot publish to more than one place, which makes updates take 3-5 minutes. If we’re doing a lot of frequent updates, as do you on Roblox, this costs our development team 30-45 minutes per a day.
This would significantly improve publishing UX, which would in turn make our playerbase happier. Note that we are considering trying to automate this with open cloud, but it doesn’t seem very easy, and it’d be very easy to adjust this UI.
I would also like to see this feature added. Currently, my experience has two separate places linked via teleports: a single player server which acts as the main menu (and also allows the player to access single-player modes), and a multiplayer server that the player is teleported to after matchmaking.
Because we cannot dynamically change the server size of reserved server instances, I am forced to have these two server sizes be two separate places, despite the fact that they have identical code and identical assets.
If we can select multiple places and batch publish to them, this would be significantly more convenient.
This would boost my updating process as I use one place to hold all my game data, and to load different assets depending on the place id, being able to publish to multiple places would help my use case
This is technically do-able now with packages and having them auto-update, but I do admit that this won’t fully allow multiple places to be updated simultaneously.
Yes! Multi-place publishing would be incredibly helpful. Simply changing the Publish Game UI to use a checkbox instead of a radio button, and then a warning prompt when selecting “Overwrite” that asks if the developer is sure they want to overwrite x places would save so much development time.
We could technically write software that uses the open cloud api to push a file to multiple places, but it makes a lot of sense to be able to do this natively.
Can u give the script as a resource? i am kinda new with APIs and i was trying to “Auto Publish” all the places of my game with external code but it fails a lot of times
