How might a studio find an old sound effect to reuse in a new game? And how would it preserve source code while keeping it safe from unauthorized access?
How do game studios keep old source files and assets around?
Answers
A studio could keep source assets in a version control system or an archive, organized by project and asset type. Searching an asset catalog would be easier than digging through an entire project, though the quality of the catalog would make a big difference.
A sound effect might also need conversion or cleanup before it works with a newer game's audio tools. Having the original file is more useful than having to extract a compressed version from the finished game.
Reply to this answer
Preservation is more than copying the code somewhere. Old projects can depend on specific compilers, development tools, libraries, and hardware. Saving documentation and build instructions alongside the files gives a future team a better chance of getting them working again.
Backups also need to be readable. Multiple copies, checks for corruption, and occasional tests of restoring the files would help. None of that guarantees an old game can still be built, though.
Reply to this answer
For security, access can be limited to people who need it, with separate protected backups in case files are deleted, corrupted, or held for ransom. Encryption and access logs can help too.
There's a tradeoff: an archive that's easy for a team to search may need different access controls from an offline backup. The exact setup would depend on the studio.
Reply to this answer
Having a file doesn't automatically mean the company can reuse it. A sound effect, piece of music, or other asset might have been licensed from someone else, so the rights and any original agreement matter too.
Reply to this answer
Add your answer
Answers are reviewed before publication.
speedrunLaundryDay:
That makes sense. The archive would need records about the asset as well as the file itself.