Disabling Team Create Wipes "uncommitted" scripts.

When disabling team create to remove the Roblox source control, I lost access to all uncommitted scripts. This outcome was not clear when choosing to disable team create. To be clear, they were saved, but not published/commited. This wiped 2 days of work and is not available through any saved history in the asset manager. It somehow dynamically wiped the script changes from all version historys.

Expected behavior

When disabling Team Create, I expect uncommitted scripts to stay in their existing state, require immediate action by the user turning off Team Create, or, at the very least, a warning that it will wipe saved but uncommitted scripts. In addition, I expect previous versions that did, in fact, have them saved and available in version history to retain these changes and not disappear into thin air. Its possible that it did not save remotely to these versions, but this seems unlikely.

1 Like

Turning the team create and drafts back on seems to have recovered them. So no longer as big of a deal, but definitely still would be nice to have a warning as to the outcome of the drafted script when turning off team create.

1 Like

Hi, thanks the bug report!

Apologies that it wasn’t clear that Drafts mode is disabled when TeamCreate is turned off. Fortunately, Drafts are kept when TeamCreate is turned off, and re-enabling TeamCreate should restore the Drafts.

Adding a warning message is a good idea! As we add more functionality to Studio, we rely more on cloud-based solutions. This means lots of features rely on TeamCreate ON.

That makes since. Thanks for responding!!