Save Anxiety

Every time I save... I am extremely anxious. As much as I really Love C3, there isn't another piece of software that gives me this much anxiety when just hitting the Save button.

As a former audio engineer, I am well aware of the need to constantly back up... which I do... but the sheer amount of times my project has been corrupted is a little wild.

I also understand that game projects are so multifaceted that they, in general, invite problems. fair enough.

But, I am wondering if there are any specific things that one can do to lessen this?

Are there behaviors to look out for that might indicate that something is amiss so I can look for culprit BEFORE I save and lock in the corrupted parts?

What are the common things to look out for that corrupt projects? Do projects folders get corrupted more often than a single project file?

For example, one time I wanted to clone a bunch of objects and then strip them of all their animations except for one frame (standard dummy objects that would be off stage).

Cloning a few of them, removing their animations corrupted my project silently.... i didn't know anything was amiss, then did a bunch of work... saved... and could not reopen.

I tried it multiple times. cloning one object at a time... etc... The project kept getting corrupted because, though I had deleted the animations from the object, for some reason it was still looking for them.

Is removing animations notoriously a problem? It isn't the kind of thing that I can make an official bug report for because It's not reproducable, really...

Does anyone else have this problem? or am I just a total hack? both could be true, of course lol.

use git or source control. it works better with a project folder instead of a single file save. but it is worth it.

There are a ton of free git UI tools, so you don't need to mess with the command line if you don't want to.

you also don't need to use github or an online service, you can keep a local repo on you're PC (having an online one is an extra layer of backup)

Yeah github is the way to go. I use github desktop for a nice GUI, it's quite simple. Add auto-backup and have it save into a cloud storage for bonus safety.

the sheer amount of times my project has been corrupted is a little wild

What in the world are you doing exactly? Because this basically never ever happens to me. I had maybe 2-3 corrupted projects over all the years and I'm always on the susceptible beta-branch too.

Yeah, Git. In the off chance your project does get corrupted, you can just revert the commit and will have a list of the exact changes to help narrow down the source of the corruption. Also, developer console (f12).

I appreciate the responses but none of them actually are responsive to my post. I already have a backup system and version control on git. Not a problem. I'm specifically asking if anyone has any insight to the actual problem of why, in my experience, C3 seems more prone to corrupt files than I had ever experienced.

If you're saying it's that I am a hack. Fair enough but you coulda just said that straight. lol anyway thanks, I have learned my lesson and backup often in multiple places on top of git already.

I'm working on huge projects (5-10k events) and had not much of a problem with the saves.

If you have problems it might be your browser or your addons.

I had issues with Edge, but Chrome has been working great.

After you save successfully just push to git.

Another idea is to make your save files smaller by offloading data into files in the C3 projects, rather than having them in the events (works great for visual novels for example).

Good luck!