Making a Game Updater
You will need:
- Get object
- String Parser
- Download object

1. Either load your updated file into the String Parser or any other client with MD5 hashing abilities. Set any string or other text object to mdFive$("String Parser") and record this information.

2. Create a .txt file or HTML/PHP file with this information:
Latest_version_number,Oldest_allowable_version_number,Update_url,Update_MD5
Note that each field is separated by a comma. Oldest_allowable_version_number is optional, so you only include it if you're going to allow users to not immediately update. The first two are version numbers, the third is an actual url, and the fourth is the MD5 hash you generated in step 1.

3. On boot or otherwise, your game should use the Get object to retrieve the .txt file you made in step 2. It then takes that information and puts it into String Parser, with a comma set as the delimiter. Take the first field and compare it to your current version. If it's higher than your current version, check the second field and compare. If it is higher than your current version, go to step 4a, else, go to step 4b.

4a. Your game is both not the latest available, nor is it new enough to be allowed to play. At this point, the game opens a separate updater application that uses the Download object to download the file specified in the Get request. Once the download is complete, it checks the MD5 hash of the downloaded file and if it matches the one in the Get request, it deletes the old game and opens the new one. The updater should know what file to delete based on the same MD5 strategy but I haven't really thought that one out so yeah. If you're wondering why you don't just download the new file on top of the old one, it's for security, make sure that it isn't being tricked into deleting anything besides the old version in favor of something that might not be the actual update.

4b. This step is pretty much 4a except you ask the user if they want to download first.