Uploading a project creates a new project, rather than replacing the current project’s data

[benjiwheeler]

Expected Behavior

Logged in, viewing a project I own, clicking File->upload from your computer... it should ask me if I want to replace the project's content, and if I confirm, load the uploaded project into the vm, maintaining the id.

Actual Behavior

Creates a new project with the uploaded content.

Question: there's no way that's the behavior we want, is there?

[cyx2015s]

I agree! Sometimes I want to upload a new project, so I click the upload button but it replaces my old project then I lost my old project!

[Alzter]

I agree! Sometimes I want to upload a new project, so I click the upload button but it replaces my old project then I lost my old project!

See, that's what File>Revert is for. That being said it should be more obvious.

[towerofnix]

Do note that uploading a project via file -> upload is frequently used for sharing a "new version" of a project. I think the issue acknowledges this.

For example, I have created a large project that I want to share an initial version of; I call this my "alpha" version. I share it, then I click "file -> save a copy"; this creates a version of the project which I do further development on. Then when I want to share that version, I download it, then in the original "alpha" project, I upload the project downloaded from the dev version. That way I preserve all the comments and stats from the original project, but have the project itself updated for anyone who plays in the future.

I've also seen people do basically the exact same thing for "updates" to projects, e.g. a "1.1.0" update adding a bunch of new things, which was mostly developed in a separate, unshared project, then uploaded over the original "1.0.0" project.