Video Game asset and source control retention was _terrible_. Hell, it's still terrible.

Prior to ~2010 we were simply deleting source code and assets for finished projects; either because they weren't owned by the developer due to a publishing deal, or because the developers didn't want to reuse their garbage code. Same follows for assets, often they were owned by the publisher and not the developer, but if the developer did happen to own them they'd rarely see reuse in future projects. And publishers didn't catch on to the value of data retention until remakes started to make serious money.

Wild culture! At almost[1] every (non game) software company I've ever worked, the source code was sacrosanct. If nothing else in the company was backed up, controlled, audited, and kept precious, at least the source code was. The idea of just casually deleting stuff because you think you're done sounds crazy to me as a software practitioner.

I still have backed up copies of the full source code of personal projects that I wrote 25 years ago. These will probably never be deleted until I'm dead.

1: One company I worked for didn't have a clue about managing their source code, and didn't even use source control. They were a hardware manufacturer that just didn't understand or care about software at all. Not what I'd think of when I think a professional game developer.

There were a few patches to RA2 through, so the code clearly exists for a bit of time post completion.

Makes sense I guess, but still seems absurd.