sig.axel at gmail.com
Wed Mar 30 07:51:39 EST 2005
Because in function WriteGame () in game/g_save.c, the date of the
binary is written to the savegame. Later, in function ReadGame ()
(same file), the DLL's date is compared to what's read from the file,
and the save isn't loaded unless the dates match.
For a simple hack, you could always hardcode a certain date string
instead of using the date when the game module was built (just replace
the strcpy (str, __DATE__); in WriteGame (), and strcmp (str,
__DATE__) in ReadGame ()).
And now I just spotted the oldsave cvar. By setting "oldsave" to 1,
you can bypass the check and load older/newer saves (assuming they are
still compatible, of course). That's even simpler. :)
On Wed, 30 Mar 2005 12:25:17 +0200, Andreas 'GlaDiaC' Schneider
<mail at cynapses.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> why isn't it possible to use an older savegame with a new version. I
> played with 0.16 and now I'm not able to load the savegame with 0.16.1
> ==== InitGame ====
> ERROR: Game Error: Savegame from an older version.
> This should not happen.
> -- andreas
> - --
> http://www.cynapses.org/ -- the geek source
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
More information about the quake2