No Scroll bar in Team History Batter Registar screen

[lfountain22]

Hello,

If I go to team history screen and view the batting register I cannot scroll down to see the individual player stats. This works for Pitching, but not hitting...so it is pretty strange.

Is there a quick fix for this?

My specific example is in a standard MLB league with the Chicago Cubs. If you wanted to look at career leaders for a team in a hitting statistic thatis outside the top 10 listed under Team History: Batter Leaders.

Thanks!

[Déjà Bru]

Originally Posted by lfountain22

Hello,

If I go to team history screen and view the batting register I cannot scroll down to see the individual player stats. This works for Pitching, but not hitting...so it is pretty strange.

Is there a quick fix for this?

My specific example is in a standard MLB league with the Chicago Cubs. If you wanted to look at career leaders for a team in a hitting statistic thatis outside the top 10 listed under Team History: Batter Leaders.

Thanks!

Yep, you're right. It seems to be one of those "capacity exceeded" things; note how thin the scroll bar is for pitchers and it's missing for batters. There are only 839 pitchers but 1,890 batters, so something is too long or numerous to allow normal scroll bar action on the batters register.

1. You can export these reports to your external browser. At least you will be able to see the entire reports but the player links will not work in your browser.

2. I posted a link to this thread in Markus' "Back to Work!" thread in which he says "If there are any pressing issues you'd like to see fixed, please post here and I'll take a look at it in case it has not been reported & tracked before." We'll see if he notices and can take action on this issue.

[AfWapo]

Originally Posted by Déjà Bru

Yep, you're right. It seems to be one of those "capacity exceeded" things; note how thin the scroll bar is for pitchers and it's missing for batters. There are only 839 pitchers but 1,890 batters, so something is too long or numerous to allow normal scroll bar action on the batters register.

1. You can export these reports to your external browser. At least you will be able to see the entire reports but the player links will not work in your browser.

2. I posted a link to this thread in Markus' "Back to Work!" thread in which he says "If there are any pressing issues you'd like to see fixed, please post here and I'll take a look at it in case it has not been reported & tracked before." We'll see if he notices and can take action on this issue.

How does this problem still exist in the 2025 version of the game. I noticed this many years ago and figured eventually it will get figured out. But, here is a thread from 2012 and the problem still exists in the game. Seems like it should be a pretty easy fix, but here we are.

Any team with history that extends past the main screen's limit loses the scroll bar on the batter register. Any team with less history it works fine.

[Déjà Bru]

Originally Posted by AfWapo

How does this problem still exist in the 2025 version of the game. I noticed this many years ago and figured eventually it will get figured out. But, here is a thread from 2012 and the problem still exists in the game. Seems like it should be a pretty easy fix, but here we are.

Any team with history that extends past the main screen's limit loses the scroll bar on the batter register. Any team with less history it works fine.

This is remarkable. I came here to fish out a complaint that I made about a garbled report that I posted about twice in 2024 and it was never addressed; I see that it's still in the same shape in 2025 (version 26).

And don't get me started on the bleeding headlines in the league newspaper. Not only am I still seeing those, but the same problem now appears periodically on the league home page. How many times has that been reported over the years?

They wear blinders, OOTPD does. Unless something is reported by dozens of people, they pay no attention. And that is only in the past few years. That I am certain about. As to why, I will let you speculate.

Anyway, it's remarkable that you chose my post from 13 years ago for your comments. I am not even going to waste any time looking to see if that issue was ever fixed.