OpenCloud has been an amazing addition that has helped us speed up our workflow tremendously, automating some procedures and adding external tooling to control certain aspects of our experiences.
We have been able to automate a lot. So much that it I could even say almost everything - except for one thing; the experience’s public / private status.
In the many projects we operate on with different development teams, there is one factor that is still entirely manual - QA testing.
For our QA tests, we have a QA version of each development place, where more in-depth testing can occur. In order not to have this place constantly visible and accessible from the group page, it is kept private until a test occurs.
Right now, we must manually make it public. There is no way to automate this with scheduled testing sessions or external commands.
The ability to change the experience’s status to public or private using OpenCloud would benefit our workflow.
Some more use cases I can think of for this:
- Scheduling a release where the experience goes public on an exact date
- Opening / closing an experience through external tooling during emergencies
- Controlling the ability to join a specific place from outside Roblox (e.g. automated place uploads that become outdated)