Game Crashes when I manually expand

michaeldanger19 · 05-12-2021, 09:41 AM

I spent a week creating 5 custom expansion team brands with the idea to grow each division by 1 team (plus the Montreal Expos, obviously)

In my head, I would take 3 seasons to get to this number. First I tried with Montreal and Portland, and used some newly dead minor league teams as the brands. I ran into an issue where certain leagues had an odd number of teams. I ignored, and the game crashed.

Okay that’s the problem then. I had lost 30 minutes setting it up. I’ll do all 6 teams at one time.

So an hour setting up the expansion teams and minors, and I press finalize and the game crashes again. Not sure if anyone has had this problem. I do it the first day of the off-season in 2021. I posted this on r/OOTP and someone said the same thing happened to them.

Thanks!

Matt Arnold · 05-12-2021, 01:29 PM

For cases like this, can you let us know what breakdown you used of teams to the minors? Was it simply in a new standard game, after the first season that you ran it? It's quite likely that one of the minors leagues got confused by the expansion, so knowing what you chose can help us dig into the specific issue.

michaeldanger19 · 05-12-2021, 03:25 PM

Absolutely.

It was a new standard start where I simmed through the 2021 season, then was hoping to expand for 2022.

Here's my breakdown of teams and divisions. I had a loose idea when I did my first attempt with the error message, but after that I built this to make sure I didn't have any odd teams. The AA, High-A, and Low-A leagues have 3 leagues and each would grow by 2. Then I made sure the divisions were balanced out.

The 4 teams with existing minor league teams would be brought under the expansion team's affiliation, so on paper two Nashville Sounds in a division might confuse the game. But I was going to move the teams that use those names to a different city once the game expanded. Problem with that is the initial crash happened without any duplicate teams. Nashville I put in AAA East as a placeholder for swapping with the Brewers' affiliate Nashville.

I didn't get a message about wonky divisions this time and thought I was in the clear. Just going from team creation > minors > expansion rules > finish

michaeldanger19 · 05-12-2021, 09:12 PM

small update and thought I'd include. Just opened the game to try and replicate the issue, starting from the last save point the day after the season ended.

"an error occurred while loading the database!
Could not load world file"

The game prompted me to create the incident file, then it loaded from the last backup save, which was the start of the season. Looks like my Rays may go from an ALCS appearance to a 500 year! haha.

Got to the end of the year, I didn't mess around with any minor league stuff and actually got past the loading screen, fwiw

05-12-2021, 09:41 AM	#1
michaeldanger19 Minors (Single A) Join Date: Sep 2016 Location: St. Petersburg, FL Posts: 63	Game Crashes when I manually expand I spent a week creating 5 custom expansion team brands with the idea to grow each division by 1 team (plus the Montreal Expos, obviously) In my head, I would take 3 seasons to get to this number. First I tried with Montreal and Portland, and used some newly dead minor league teams as the brands. I ran into an issue where certain leagues had an odd number of teams. I ignored, and the game crashed. Okay that’s the problem then. I had lost 30 minutes setting it up. I’ll do all 6 teams at one time. So an hour setting up the expansion teams and minors, and I press finalize and the game crashes again. Not sure if anyone has had this problem. I do it the first day of the off-season in 2021. I posted this on r/OOTP and someone said the same thing happened to them. Thanks!

05-12-2021, 03:25 PM	#3
michaeldanger19 Minors (Single A) Join Date: Sep 2016 Location: St. Petersburg, FL Posts: 63	Absolutely. It was a new standard start where I simmed through the 2021 season, then was hoping to expand for 2022. Here's my breakdown of teams and divisions. I had a loose idea when I did my first attempt with the error message, but after that I built this to make sure I didn't have any odd teams. The AA, High-A, and Low-A leagues have 3 leagues and each would grow by 2. Then I made sure the divisions were balanced out. The 4 teams with existing minor league teams would be brought under the expansion team's affiliation, so on paper two Nashville Sounds in a division might confuse the game. But I was going to move the teams that use those names to a different city once the game expanded. Problem with that is the initial crash happened without any duplicate teams. Nashville I put in AAA East as a placeholder for swapping with the Brewers' affiliate Nashville. I didn't get a message about wonky divisions this time and thought I was in the clear. Just going from team creation > minors > expansion rules > finish Last edited by michaeldanger19; 05-12-2021 at 03:38 PM.

05-12-2021, 09:12 PM	#4
michaeldanger19 Minors (Single A) Join Date: Sep 2016 Location: St. Petersburg, FL Posts: 63	small update and thought I'd include. Just opened the game to try and replicate the issue, starting from the last save point the day after the season ended. "an error occurred while loading the database! Could not load world file" The game prompted me to create the incident file, then it loaded from the last backup save, which was the start of the season. Looks like my Rays may go from an ALCS appearance to a 500 year! haha. Got to the end of the year, I didn't mess around with any minor league stuff and actually got past the loading screen, fwiw Last edited by michaeldanger19; 05-12-2021 at 09:24 PM.

05-12-2021, 01:29 PM	#2
Matt Arnold OOTP Developer Join Date: Jun 2009 Location: Here and there Posts: 16,249	For cases like this, can you let us know what breakdown you used of teams to the minors? Was it simply in a new standard game, after the first season that you ran it? It's quite likely that one of the minors leagues got confused by the expansion, so knowing what you chose can help us dig into the specific issue.