OOTP 26 Patch Released: 26.7.77

[zevus]

The AI teams in my save do not have enough players in their rookie league rosters, or their A or A+ rosters. My ACL team ended with a ~95% winning percentage & DSL at ~99%.

It seemed to bleed into the A and A+ a bit, as well. ~88% and ~80% winning percentages there. Typically these teams run ~60% for me.

AA and AAA results weren't as extreme so could be more of a variation issue. AA team was ~67% and AAA team was ~55%.

This save started from a live 2025 start, w/ the patch hitting sometime during the offseason prior to the 2030 season start. I haven't gotten into the 2031 season yet, so I'm not sure if it corrects itself.

[Jor97]

The AI is still releasing 2025 draftees, albeit not the first or second rounders. Currently, the most likely to be released are the draftees from the later rounds, although I've seen 3-5 rounders being released as well. Currently, 196 of 589 drafted players have been released in one way or another within three months of the draft, mostly pitchers in the 40-45 potential range. My current tests was with roster limits, but it also happens in a standard 2025 game. As a previous user pointed out, some of these players enter the loop of being signed and released over and over again as well.

This issue has become a real head scratcher for me, seeing as I did not seem to have these problems in OOTP26 before the July patch and in the whole life cycle of OOTP25.

[Déjà Bru]

Originally Posted by Matt Arnold

[*]Added an alternate colorblind-friendly skin option
**This is still a work in progress, please provide feedback

How about fixing this?



It's the same in all skins and it was reported twice last year.

[Rain King]

Originally Posted by Déjà Bru

How about fixing this?

Attachment 1081599

It's the same in all skins and it was reported twice last year.

What is it that you want them to do here? You've put too much information into the view...and you could have put the abbreviated versions of a number of those columns to prevent the issue yourself.

[Déjà Bru]

Originally Posted by Rain King

What is it that you want them to do here? You've put too much information into the view...and you could have put the abbreviated versions of a number of those columns to prevent the issue yourself.

Sorry, I should have been more explicit. This is a report, not a view. Column selection is not available for reports:



The browser version is fine:



All they have to do is insert a single space in the in-game report so that the two columns don't run into each other.

[Rain King]

I imagine that is not a high traffic screen. I'd hope they will eventually fix it but I completely understand it not being high on the priority list.

[jcard]

Originally Posted by Rain King

I imagine that is not a high traffic screen. I'd hope they will eventually fix it but I completely understand it not being high on the priority list.

Given that he / she reported it—twice—last year, I’d hardly say they’re being pushy.

[Déjà Bru]

Originally Posted by jcard

Given that he / she reported it—twice—last year, IÂ’d hardly say they’re being pushy.

Thank you. I don't mean to be pushy but this experience, and the bleeding, overrun headlines on the league newspaper which have been reported for years, is not a good sign.

I did indeed post twice last year about the roster report in the "Cosmetic issues & typos" thread. While I did not expect a direct response from officials, I expected them to do something about it. How hard can it be to insert a space between the two columns?

I am not bothering with that thread this time. Matt invited feedback on the new alternate skin; well, this report (and the bleeding, overrun headlines) are part of that skin and the others. That is my feedback; it's either noticed and acted upon, or it is not.

[jofos]

Game crashes every time I try to load it.

[millhousebc]

Originally Posted by jofos

Game crashes every time I try to load it.

Had this happen. I just re-downloaded the game, and no issues

[shakturi101]

Is there a plan/ETA to release a patch in the coming weeks? Just trying to plan when to start a new save since work got less busy.

[eas9898]

Originally Posted by shakturi101

Is there a plan/ETA to release a patch in the coming weeks? Just trying to plan when to start a new save since work got less busy.

Also would like to know. Thanks!

[Baseballman2K5]

I am not seeing any improvement with drafted players being released immediately after the draft.

I only have roster limits at AAA and AA...could that still be affecting this?

[Baseballman2K5]

Originally Posted by Baseballman2K5

I am not seeing any improvement with drafted players being released immediately after the draft.

I only have roster limits at AAA and AA...could that still be affecting this?

I had AAA and AA at 28 man limits but i just noticed under settings it says "do not set roster limits below 35"...is this new and potentially the reason draftees were released?

[Baseballman2K5]

And another issue...

at the start of the DSL season, the roster is very limited for most teams...and a lot are carrying 1 catcher on opening day. I have removed the 'no foreigners' option due to this

[Baseballman2K5]

Originally Posted by Baseballman2K5

And another issue...

at the start of the DSL season, the roster is very limited for most teams...and a lot are carrying 1 catcher on opening day. I have removed the 'no foreigners' option due to this

DSL teams rostering just 1 catcher and barely any pitchers or bench hitters...don't even sign players...it looks like they keep passing catchers back and forth from ACL and their second DSL team if they have one.

Maddening

[Jor97]

Originally Posted by Baseballman2K5

I had AAA and AA at 28 man limits but i just noticed under settings it says "do not set roster limits below 35"...is this new and potentially the reason draftees were released?

It shouldn't, if I recall correctly the 35-man minimum only applies to the lowest possible minor league level.

I've since went back to OOTP25 which strangely does not have this issue at all and works fine with roster limits imposed.

[Baseballman2K5]

Originally Posted by Baseballman2K5

And another issue...

at the start of the DSL season, the roster is very limited for most teams...and a lot are carrying 1 catcher on opening day. I have removed the 'no foreigners' option due to this

I did some testing and it appears when there are NOT roster limits...the AI does not properly fill DSL/ACL rosters, keeping them in the 20s and sometimes below 20.

When roster limits were put in, at 42 for ACL and DSL...teams started signing players to fill the roster up to 42. It appears the AI wants to max out the roster to the limit...when limits are in place.

[tm1681]

Originally Posted by Baseballman2K5

I had AAA and AA at 28 man limits but i just noticed under settings it says "do not set roster limits below 35"...is this new and potentially the reason draftees were released?

"do not set roster limits below 35" is only recommended for the lowest Minor League level that you have active, not every level.

[johndoe8865]

Originally Posted by Jor97

It shouldn't, if I recall correctly the 35-man minimum only applies to the lowest possible minor league level.

I've since went back to OOTP25 which strangely does not have this issue at all and works fine with roster limits imposed.

Probably one of the most frustrating releases of the single player (meat and potatoes) portion of the game I can remember in at least 5 to 10 years.

It's truly disappointing to have to go back to OOTP 25. If I'd known that, I could've just started there instead of waiting for 26 to resolve the issues that didn't exist in 25.

I know new features were introduced concerning prospects development etc, but the apparent lack of long term single player testing is frustrating as an end user who buys the product and expects it to function well at some point before 7-8 months later.

I'll definitely have to wait and see on 27 to see if either a) 26 is ever fixed or b) patches are out and people confirm that 27 has functional minor league AI like 25 had or, hopefully better.