How do I securely backup my work?
From OHRRPGCE-Wiki
Contents |
[edit] Which files?
Always make backup coies of your RPG file and your script file. The filenames vary, but they are usually going to be something like MYGAME.RPG and MYGAME.HSS
[edit] Local Backups
A local backup is when you copy your files into a different folder on your hard drive. This is easy to do, and can save you from data-loss.
To do this, simply select RPG file (and your script file), press CTRL+C then open a different folder and press CTRL+V
[edit] To a ZIP File
A nice way to back-up your files is to put them into a ZIP file. Windows XP users can do this every easily by right-clicking on the RPG file, and then picking "Compressed (Zip) folder" from the "Send To" menu.
[edit] Backup to a removable disk
If you game is small enough you can back it up to an old fasioned floppy disk. For larger games and newer computers you can get a USB thumb drive to back up your files.
[edit] Backup to a CD
If you have a CD burner, you can use it to back-up your files. One thing to be careful of: when you restore your RPG file from a CD back to your hard-drive, it may have the "Read-Only" bit set. You need to right-click on the file, and pick "Properties". On the properties window you can turn off "Read-Only" so that you can continue to edit your game.
[edit] Backup to the Internet
If you have a website, you can upload your RPG file there. (it is a good idea to put it in a ZIP file first.) You can also upload your game to Castle Paradox's gamelist.
[edit] Back Up by E-Mail
Another method is to e-mail your RPG file to a friend. If your own copy is lost or damaged, you can ask your friend to send it back.
[edit] Backup via a Repository
Version Control software such as CVS or Subversion require slightly more effort to set up, but are a breeze to use after that. Essentially, you set up a "server" which holds your files in a format that (very broadly speaking) remembers every change you've made to a file. You, on the other hand, work on a "local copy" just as you normally would, then periodically "commit" any new changes to the server. For more detailed information, please see our guide to setting up version control with Subversion.
