Currently, as of 6/5/22, the new collaboration widget automatically enables team-create if team-create is disabled. Automatically enabling team-create is unexpected behavior, as the new widget is meant to replace the game permission settings under the main game settings widget.
Expected Behavior
It is expected that changing game access settings would not automatically enable team create if team create is disabled. This is bad UX and it destroys my workflow, which consists of external tooling.
Actual Behavior
Team create is automatically enabled whenever game access settings are changed, forcing me to manually disable team create after I change game access settings through the beta widget.
Workaround
Not using the beta widget
Issue Area: Studio Issue Type: Other Impact: High Frequency: Constantly Date First Experienced: 2022-09-05 00:09:00 (-04:00)
hi @Noble_Draconian thanks for the feedback! Can you give me a bit more details about this:
Why does turning on Team Create impact your workflow, especially with external tooling? Are there tools that don’t work within Team Create? Or something else? We’re trying to ensure TC doesn’t disturb any workflows, so any insight here would be great.
It looks like you are giving access to other collaborators to your experience. Can you tell me more about your scenario where you’re adding collaborators but don’t want Team Create on?
Are you in a group-owned experience? Are you giving collaborators Edit access?
I’m making use of rojo, specifically its live-syncing feature to sync changes from the filesystem into studio. TC being enabled breaks this, forcing me to disable TC before enabling live-sync. It’s a few extra steps that I don’t need. This also results in scripts needing to be published through script versioning, which I do not want. I simply want to have my changes from the filesystem applied directly to the scripts so that I can publish at any time, without needing to go through the script version history widget.
Overall, having TC disabled is ideal for me. I keep it intentionally off in most scenarios, only enabling it when I have an actual need for it.
I’m actually not! The only changes I made was giving “Play” perms to a specific group role. No one was given edit perms.
It is group owned, however I am not giving collabs edit access, only play access.
@Noble_Draconian thanks for the extra context - this is super useful. We definitely don’t want TC to be disruptive to your Rojo flow. Let me sync with the team on what we can do here. Will get back to you soon!
Also just curious, are you giving Play access for Playtesting with QA?
Ideally enabling / disabling team create should be an explicit, separate control as it always has been until this beta was introduced! If I edit settings, I don’t expect unrelated things to be turned on without my consent.
That’s the main usecase, yeah. We want only our QA testers to have play access to a private build of our game.
hey @Noble_Draconian I think we chatted on this after this post but wanted to confirm - are you still seeing disruptions to Rojo workflows in TC? Rojo should work the same regardless of whether TC is on or not. Let us know! We are working on enabling creators to work seamlessly with externals tools, so wanted to revisit this thread.
