http://linkware.clan-mac.com/wc3autosave
For Windows, by Slackweed: http://wcautosave.slackpages.com/
Hi there!
Let me first explain what you might use this for...
WarCraft 3 automatically, after every game you play, saves a replay of the game you played, whether you want it to or not. It saves this to the "LastReplay.w3g" file, in the replays folder of your WarCraft 3 installation.
So, if you forget to save a replay, but immediately remember (after going back to Battle.net's
chat screen), you can still get your replay... But if you play another game, and then remember
that you had forgotten to save the replay, then it's gone.
Why? WarCraft 3 overwrites the file.
Get it? If you play a game, forget to save, then play another game..., you lose the replay.
However, if you run this program, you won't. This program checks to see if that file exists or if it doesn't. If it exists, then it moves and renames it, to something more descriptive. That way, when you play another WarCraft 3 game, you don't need to worry about whether or not you saved the last game.
Currently, it checks for the file once every minute. It wouldn't be hard to increase or decrease this value if you find that it's too much time (you immediately go from one game to another), or too little time (you hardly ever play).
The current version is 1.0d4. You can download it (and the source code) here:
http://linkware.clan-mac.com/wc3autosave/Release/1.0d4/wc3autosave-10d4.zip
If you find any bugs, or have any questions, or perhaps a comment or anything, please let me know by sending me an email (kane@clan-mac.com), contacting me on AIM (Kanezor), or send me a message on Battle.net (MacBinaryBot@USEast, tA-Kane@Azeroth).
Version 1.0d4 Known bugs:
If an error occurs while trying to open the replay, a SIOUX console will appear, and you cannot get rid of it, or quit the program. You can still, however, quit the program with the included AppleScript.
WC3 Autosave is not able to tell where you installed WarCraft 3, and so cannot find the LastReplay.w3g file without a little help. WC3 Autosave currently must be installed and running from either the WarCraft III folder, or the replays folder (both *should* work...).
If there's a lot of players, the new generated filename may be truncated by the system. I hope to figure out a different approach to naming the files... if you have an idea, contact me!
If WC3 Autosave encounters an error, it should beep and then create a "Debug.txt" file in the
same folder that it in running in. Please check for this file every now-and-then, and if you find
it, please send it to me, as well as your LastReplay.w3g file.
Especially watch for this file if your system beeps shortly after playing a game of WarCraft 3!
That's all the bugs I currently know of for myself... now I'll list the couple (2) of features I plan on adding in the near or distant future:
Make WC3 Autosave a faceless background application (like a daemon).
Add preferences
What to include in the renaming of the replay
Where WarCraft 3 is installed (so that you can have WC3 Autosave somewhere else)
Statistical counting (how many replays found, how many players counted, how much total time
WarCraft 3 has been played for, etc)
Version History:
(November 19, 2004) 1.0d4 - (src)
- Added a support to verify the new file has a unique filename
- Fixed a bug which would cause error -4 (unimplemented core routine) for ConvertUTCToLocalDateTime().
(October 21, 2004) 1.0d3 - (src)
- Fixed a bug which would cause WC3 Autosave to only work for the first LastReplay.w3g file found.
1.0d1 - (src)
- Initial Release
I hope you enjoy this program!
Credits:
Thanks to Blizzard for making such a fine game!
Thank you Jon Kliegman, for writing (distributing?) source code
to read the WarCraft 3 replay file (at least, the header portion, which is all this program needs).
Shout-outs to Slackweed for some assistance, and for writing the origional WarCraft 3 Autosave,
for Windows. You can download his Windows version here:
http://wcautosave.slackpages.com.
MacMark deserves countless thanks, for asking me
to do this :)
And last, but not least, I thank you for reading this readme file!