OOTP Developments Forums - View Single Post

Zeyes · 04-24-2007, 02:23 PM

FWIW, it seems the game uses a different numbering when importing schedules than it does when exporting them.

I used a 4-team division, which we'll mock-up like this:

TeamAAA
TeamBBB
TeamCCC
TeamDDD

Entering them alphabetically like that, they're also numbered in the same order. I then deleted CCC, and added a new team, which I then renamed to TeamABC. That way, the 3rd slot team was deleted, the new team went into the 4th slot as per the screen display (and the team ID, as per a csv export), and by alpha-sorting it moved into the 2nd slot.

That covered a few possibilities. :-) Then I imported the same schedule again.

TeamAAA's first home game is set up like this in the schedule file:

<GAME home="1" away="2" time="1905" day="5" />
< GAME day="5" time="1905" away="2" home="1" / >

Correctly, it was TeamBBB @ TeamAAA before the team changes. Afterwards, it was TeamABC @ TeamAAA, which seems to indicate that for importing purposes, OOTP is ordering the teams in alphabetical order in each division when it maps them to the schedule file numbering.

However, if I now export the new schedule, AAA's first home game shows up like this:

<GAME home="1" away="4" time="1905" day="5" />
< GAME day="5" time="1905" away="4" home="1" / >

Apparently, once the schedule was loaded, the regular ordering by Team ID takes over within the game, and TeamABC becomes the 4th team instead of the 2nd.

That messes things up if one repeatedly imports and exports the same schedule...in the above example, re-importing the exported schedule results in the game being TeamDDD @ TeamAAA, because DDD is the 4th team in alpha order.

(And if I export it yet again, the schedule entry becomes < GAME day="5" time="1905" away="3" home="1" / > because TeamDDD is the 3rd team by Team ID. Etc. Etc.)

04-24-2007, 02:23 PM	#7
Zeyes All Star Reserve Join Date: Jun 2006 Posts: 818	FWIW, it seems the game uses a different numbering when importing schedules than it does when exporting them. I used a 4-team division, which we'll mock-up like this: TeamAAA TeamBBB TeamCCC TeamDDD Entering them alphabetically like that, they're also numbered in the same order. I then deleted CCC, and added a new team, which I then renamed to TeamABC. That way, the 3rd slot team was deleted, the new team went into the 4th slot as per the screen display (and the team ID, as per a csv export), and by alpha-sorting it moved into the 2nd slot. That covered a few possibilities. :-) Then I imported the same schedule again. TeamAAA's first home game is set up like this in the schedule file: <GAME home="1" away="2" time="1905" day="5" /> < GAME day="5" time="1905" away="2" home="1" / > Correctly, it was TeamBBB @ TeamAAA before the team changes. Afterwards, it was TeamABC @ TeamAAA, which seems to indicate that for importing purposes, OOTP is ordering the teams in alphabetical order in each division when it maps them to the schedule file numbering. However, if I now export the new schedule, AAA's first home game shows up like this: <GAME home="1" away="4" time="1905" day="5" /> < GAME day="5" time="1905" away="4" home="1" / > Apparently, once the schedule was loaded, the regular ordering by Team ID takes over within the game, and TeamABC becomes the 4th team instead of the 2nd. That messes things up if one repeatedly imports and exports the same schedule...in the above example, re-importing the exported schedule results in the game being TeamDDD @ TeamAAA, because DDD is the 4th team in alpha order. (And if I export it yet again, the schedule entry becomes < GAME day="5" time="1905" away="3" home="1" / > because TeamDDD is the 3rd team by Team ID. Etc. Etc.)