Home Artists Posts Import Register

Content

A few days ago, the coder wrote to me that in an instant his PC has gone haywire and RPGMaker spoiled the system files of version 0.65 that were in work.

Of course, he had backups but even so that trouble could become a great challenge because it could've destroyed the month's work!

I called him immediately and then, after a short conversation, decided to come to him to help or just to cheer him up somehow.

I won't bore you with the details, I'll just tell you that after many hours of hard battle to that problem the coder finally found the way to avoid deleting of important data and all the hellish work to rewrite the text within the time remaining. (we didn't find how to do it on the Internet, he figured it out himself)

Anyway, everything went well. We've lost ultimately about 10 minutes of work, not the whole month!

He's learned through that hard experience to save everything he did onto a flash drive every day, so nothing can happen to it. He left the broken version 0.65 on the desktop as a reminder.

P.S.: The development process didn't suffer and now we're working with the double force to release the game in time.

Files

Comments

Anonymous

The lesson should be to use a version control system with frequent checkins and backup the repository instead. That way you can even track where you might have introduced a bug and otherwise can look into the history of changes.

futabox

Of course, you're right but when everything goes fine for some time, you get relaxed, and then such sort of things happen.

Klinger

And what was the point at all in this post? So that subscribers can sympathize with you?

futabox

First of all, this is a real-life experience that directly concerns the game, and secondly, the players can be happy that nothing bad has happened.

Kawaii poni

так мне стало интересно что у кодеро сломалось можно паподробнее))

cthonianmessiah

I can see how regular flash drive backups fits the need to keep the work private while avoiding dependency on one piece of hardware. I agree with the other commenter that a git server would be the way to go to preserve the code base indefinitely, but I'm guessing you don't have a big IT department, lol.