The fixtures are stored in teh Fxt directory. fix09, fix10, etc are the domestic fixtures (actually it contains ALL fixtures, domestic and international. It's used in full games county + international). int09, int10, etc are the fixtures used in international only saved games.
Use a hex editor to view the files. For example, open
int09.fxt. It's easier if you view the data in 2 byte blocks.
The first match is ODI #1, South Africa vs Australia
After the plain text "Cr Fixture", locate the double byte 08 (hexidecimal). That's the starting point.
first byte = match type
second byte = match number in series
third byte = number matches in series
bunch of filler byte. 00 FF 3477, CDCD ...
Immediately after the last CDCD
first 4 bytes = home team
second 4 bytes = visiting team
zeroes
third 4 bytes = date in day number. i.e. april 1st = day 1, march 31st = day 365
The next bytes are day + 1, day + 2 until the day of the next match.
Example, for the first match.
08 01 05 = ODI, first match, 5 match series
00 FF 34 77 000 CD CD...CD
3000 2b00 0000 0300 = South Africa, Australia, day 3 (april 3rd).
Here are the codes for international games. I have decoded codes too, but I doubt anybody wants to edit the domestic schedule. The T20 world cup format is slightly different, and I haven't figured out how the program reads it yet. The problem with this format is it's sequential. There is a counter used to track the number of matches in a year, so adding matches means you have to modify all remaining matches. Shouldn't be TOO hard to write an editor, unfortunately I'm very short on free time at the moment.
In the game, go to fixtures, view all international, and save that to a txt file. Makes it easier to go through the .fxt file and compare.
Code:
SA 0x3000 48
AUS 0x2B00 43
WI 0x3200 50
ENG 0x2C00 44
IND 0x2D00 45
SL 0x3100 49
NZ 0x2E00 46
PAK 0x2F00 47
BAN 0x3300 51
Code:
0x08 = 0DI
0x07 = Test
0x09 = 3 day friendley
0x05 = T20 world cup
0x0A = One Day Friendly
0xOD = International T20
0x04 = ODI World Cup