Schedule import issue

cbbl · 06-10-2021, 02:22 PM

I am trying to customize a schedule by directly editing the .lsdl file. But I'm having an issue.

It's a simple 4-team league. The four team IDs are 9, 10, 11, and 12. I let OOTP autocreate the schedule and then export it. When I open it the teams are listed as 1, 2, 3, and 4. If I were to map it out team 9 = schedule team 1, team 10 = schedule team 3, team 11 = schedule team 4, and team 12 = schedule team 2.

I mass edit the start times in the .lsdl file and save it. I make no other changes.

When I re-import the schedule, 1, 2, 3 and 4 are now different teams (team 9 is now schedule team 3, team 10 is now schedule team 1, etc.). This is causing havoc with planned double headers.

How can you edit the .lsdl files such that the re-import doesn't shift the teams?

(BTW, I tried changing the teams in the .lsdl file from 1, 2, 3, 4 to 9, 10, 11, and 12, but this caused OOTP to not be able to import the file)

JudgeGio · 06-10-2021, 07:30 PM

I reported this issue last year to the devs, sent them all my data files, and they ignored it. If you have only four teams none of them should have a number greater than 4. If you are going by the “Internal Team ID” number in the game’s Team Settings screen, those don’t count for anything in an .lsdl file. How the teams are SUPPOSED to be numbered is in alphabetical order by city, per division. So in the AL East, Baltimore would be 1, Boston 2, New York 3, Tampa Bay 4 and Toronto 5. Then in the AL Central, Chicago would be 6, Cleveland 7, Detroit 8, etc. But when you export from OOTP to an .lsdl file the numbers get scrambled. What I do is within OOTP, on day 1 of the schedule give each game a unique starting time, so when you export to an .lsdl you can more easily trace the numbers given to each team. I take a screen shot of day 1 within OOTP, export to an .lsdl, reimport it, then see how day 1 of the schedule changes. So if the 1 PM game was Baltimore at Boston before the import, but Tampa Bay at Toronto after the import, you know the export changed team 1 to team 4, and team 2 to team 5. To get the schedule back to the original one I have to do a mass replace in the .lsdl of all 4’s to 1’s, and all 5’s to 2’s.

cbbl · 06-11-2021, 01:14 PM

JudgeGio...

Well, that's frustrating. I'll have to post on the mod boards too, to see how those guys handle it.

The problem I see with your solution, though, is that every time you import the .lsdl file, the team #s change. So, in your example, you've now discovered that if Baltimore was team 1 before the import, then Tampa Bay was team 1 and Baltimore was now team 4, you'd edit the .lsdl file to replace 4 with 1, setting Baltimore back to team 1.

But then when you imported it again, OOTP will change it again...so now maybe Toronto is team 1.

And you find yourself in an endless loop.

Or am I mistaken? Does OOTP only jostle the #s once? I'll have to experiment to see, but your perspective is helpful.

JudgeGio · 06-11-2021, 03:03 PM

One good thing is that exporting a schedule always changes a number to the exact same other number. So if the game changes team 4 to team 1, the next time you export, 4 will be changed to 1 again. I made a side text file with instructions like “do a mass find->replace of 1 with 4, find->replace 8 with 10, etc.

06-10-2021, 02:22 PM	#1
cbbl All Star Starter Join Date: Apr 2003 Location: Massachusetts Posts: 1,179	Schedule import issue I am trying to customize a schedule by directly editing the .lsdl file. But I'm having an issue. It's a simple 4-team league. The four team IDs are 9, 10, 11, and 12. I let OOTP autocreate the schedule and then export it. When I open it the teams are listed as 1, 2, 3, and 4. If I were to map it out team 9 = schedule team 1, team 10 = schedule team 3, team 11 = schedule team 4, and team 12 = schedule team 2. I mass edit the start times in the .lsdl file and save it. I make no other changes. When I re-import the schedule, 1, 2, 3 and 4 are now different teams (team 9 is now schedule team 3, team 10 is now schedule team 1, etc.). This is causing havoc with planned double headers. How can you edit the .lsdl files such that the re-import doesn't shift the teams? (BTW, I tried changing the teams in the .lsdl file from 1, 2, 3, 4 to 9, 10, 11, and 12, but this caused OOTP to not be able to import the file) Last edited by cbbl; 06-10-2021 at 02:23 PM.

06-10-2021, 07:30 PM	#2
JudgeGio Minors (Double A) Join Date: Aug 2019 Location: New Jersey Posts: 129	I reported this issue last year to the devs, sent them all my data files, and they ignored it. If you have only four teams none of them should have a number greater than 4. If you are going by the “Internal Team ID” number in the game’s Team Settings screen, those don’t count for anything in an .lsdl file. How the teams are SUPPOSED to be numbered is in alphabetical order by city, per division. So in the AL East, Baltimore would be 1, Boston 2, New York 3, Tampa Bay 4 and Toronto 5. Then in the AL Central, Chicago would be 6, Cleveland 7, Detroit 8, etc. But when you export from OOTP to an .lsdl file the numbers get scrambled. What I do is within OOTP, on day 1 of the schedule give each game a unique starting time, so when you export to an .lsdl you can more easily trace the numbers given to each team. I take a screen shot of day 1 within OOTP, export to an .lsdl, reimport it, then see how day 1 of the schedule changes. So if the 1 PM game was Baltimore at Boston before the import, but Tampa Bay at Toronto after the import, you know the export changed team 1 to team 4, and team 2 to team 5. To get the schedule back to the original one I have to do a mass replace in the .lsdl of all 4’s to 1’s, and all 5’s to 2’s.

06-11-2021, 01:14 PM	#3
cbbl All Star Starter Join Date: Apr 2003 Location: Massachusetts Posts: 1,179	JudgeGio... Well, that's frustrating. I'll have to post on the mod boards too, to see how those guys handle it. The problem I see with your solution, though, is that every time you import the .lsdl file, the team #s change. So, in your example, you've now discovered that if Baltimore was team 1 before the import, then Tampa Bay was team 1 and Baltimore was now team 4, you'd edit the .lsdl file to replace 4 with 1, setting Baltimore back to team 1. But then when you imported it again, OOTP will change it again...so now maybe Toronto is team 1. And you find yourself in an endless loop. Or am I mistaken? Does OOTP only jostle the #s once? I'll have to experiment to see, but your perspective is helpful.

06-11-2021, 03:03 PM	#4
JudgeGio Minors (Double A) Join Date: Aug 2019 Location: New Jersey Posts: 129	One good thing is that exporting a schedule always changes a number to the exact same other number. So if the game changes team 4 to team 1, the next time you export, 4 will be changed to 1 again. I made a side text file with instructions like “do a mass find->replace of 1 with 4, find->replace 8 with 10, etc.