This is still a much needed feature.
Today I had to upload to a group a couple of private places for a project and set them up, and I needed the place links so I could update certain website settings and share them with my partners.
However, since the places were private (because they’re development places which aren’t supposed to be played), I could not use the Share button as it requires the game to be public.
I instead had to go to the website and navigate through three pages, six clicks and a minute for something that could have been done way more quickly, had the Share button allowed it. My flow was:
- I opened my local place file I wanted to publish
- I published it to two different games on the same group
- I opened Roblox in my browser (after intuitively clicking the Share button and realizing that I could not use it)
- I clicked the Create tab (and waited for the page to load)
- I clicked Group Creations (and waited for the page to load again)
- I selected the group I uploaded my places to (and, once again, waited for the page to load)
- I right clicked the places and copied the links
- Finally, I sent them over to my partners.
If the Share button allowed links to private places to be shared:
- I would have opened my local place file
- I would have published it to two different games on the website
- I would have used the Share button to get a link to them
- I would then have sent the links to my partners.
Furthermore, the same problem happens whenever we have a place that we want to run a test session on.
We usually make the testing place private and configure the permissions through the game settings so users above a certain rank in our group are allowed to join.
The Share button, however, does not like us sharing links to private places, so we need to go through that lengthy process every time just to get a link to the place to send to our testers. And this happens multiple times a month.
If the intent was to improve UX so people did not accidentally share links to inaccessible games, a warning near the visible links could be kept, because the current behavior is a legitimate hindrance to our development flow: even newer users who might not know about the Create page and have always accessed their projects through Studio may also have a hard time finding the right path to the place through the website.
Please consider implementing this feature. The infrastructure is already there (fetching the place status/showing an UI element conditionally), and it would go miles towards making development on Studio more streamlined and pleasant to work with.