Question about forward/backward compatibility of export files

Peterk · 04-11-2002, 06:47 AM

I'm running a play-home games league and we've run into this situation a few times and it's quite difficult and time-consuming to diagnose and it's happening a lot now that the patches are coming out quickly.

Basically a coach plays his games out on a version of the game which is not the same as the commish. What generally happens:

1. Commish sends out league files. Commish is using version X of OOTP.

2. Coach using version Y of OOTP gets league files and starts playing games, preparing export files. There are generally no errors/warnings/notifications produces here pertaining to version mismatch.

3. Commish gets version Y exports and starts merging them into his version X league. Generally _some_ games will merge properly, but then you hit one that refused to go in and OOTP simply core dumps.

Now to restart, you basically lose all the games that have already merged properly and have to do them all again at least once until you get to the failure game.

Would it be possible to:

1. To notify the player that his version of the game is different than the commish before he starts playing the games.

AND/OR

2. To tell the commish that the exp was not produced with the same version of the game as his before actually trying to modify the league data so that the commish never has the league crash on him because of this.

I know there aren't too many play-home games leagues around and this is a minor issue for most, but this really is the #1 problem with running such a league. I've lost coaches who have become frustrated with the delays incurred through dealing with this (...the first time it happened, it took 6 weeks to finally find that one coach who was on a different version than everyone else).

04-11-2002, 06:47 AM	#1
Peterk Minors (Triple A) Join Date: Dec 2001 Location: Montreal Posts: 220	Question about forward/backward compatibility of export files I'm running a play-home games league and we've run into this situation a few times and it's quite difficult and time-consuming to diagnose and it's happening a lot now that the patches are coming out quickly. Basically a coach plays his games out on a version of the game which is not the same as the commish. What generally happens: 1. Commish sends out league files. Commish is using version X of OOTP. 2. Coach using version Y of OOTP gets league files and starts playing games, preparing export files. There are generally no errors/warnings/notifications produces here pertaining to version mismatch. 3. Commish gets version Y exports and starts merging them into his version X league. Generally _some_ games will merge properly, but then you hit one that refused to go in and OOTP simply core dumps. Now to restart, you basically lose all the games that have already merged properly and have to do them all again at least once until you get to the failure game. Would it be possible to: 1. To notify the player that his version of the game is different than the commish before he starts playing the games. AND/OR 2. To tell the commish that the exp was not produced with the same version of the game as his before actually trying to modify the league data so that the commish never has the league crash on him because of this. I know there aren't too many play-home games leagues around and this is a minor issue for most, but this really is the #1 problem with running such a league. I've lost coaches who have become frustrated with the delays incurred through dealing with this (...the first time it happened, it took 6 weeks to finally find that one coach who was on a different version than everyone else).