[Fabrice Lete, a developer at Fishing Cactus, warns of the problems that you may face when trying to exhume an old project, in this #altdevblogaday-reprinted opinion piece.] Continuous integration and an automated asset pipeline should guarantee that you can produce an up-to-date working version of the game you are currently working on in very little time. And usually that pretty much works, besides the eventual “damn, old texture” self-note during demos. But what happens when you have to exhume an old project? That usually doesn’t go that smooth, but why would you do that anyway? Here are a few reasons from the top of my head:
- To issue a patch long after the game has been released.
- To put back in production a game that was waiting for financing.
- To re-publish a game at budget price, or as a bundled freebie.
- To port an old game to a new platform.
- To use the old game as a sandbox for testing ideas.