Bug report thread

[dward1]

fictional world with leagues with varying financials. teams in the lowest league have built up over $1 million in cash available (player payrolls as low as $65,000) and yet still let their rosters run down to 8 players with none on reserve roster despite 153 pages of free agents at reasonable prices

[Eckstein 4 Prez]

Here's an in-game bug I've noticed for years; I'd somehow thought this one had been fixed a couple versions ago but I just saw it in a game.

This bug can only be seen in the bottom of the ninth (or tenth, eleventh, etc.) with multiple runners on the bases. In my case, it was bases loaded, one out in the 11th. The batter came up and hit a ball into the gap for the walk-off win. No problem there - it's how the game scored it that causes the bug.

The game gave the batter a double, and the home team a 1-0 win - i.e., only one of the three runners on base scored, which is an impossible situation.

I think I know how this bug came to be. In earlier versions of OOTP, batters would routinely hit walk-off doubles and triples, scoring two or three runs. That's not how it happens in real life, where everyone on base just advances as far as they need to on an obvious walk-off hit.

Someone must have pointed that out to the powers that be, so we no longer have "extra" runs scoring on walk-off hits. The problem is that the in-game engine hasn't been adjusted to give the batter credit for a single only in situations such as those that just occurred in my game. So we have a situation where there were three men on base, the batter hits a double, and one run scored. Evidently the extra runner got swallowed up by the earth or something.

I realize this is a long post about a pretty minor bug, but I believe it is symptomatic of how problems get "fixed" with the game. In going for the quick and easy fix to stop "extra" runs from scoring on walk-off hits, no thought was given to the side effects of making that quick and easy fix, so in fixing one problem a new one was created. This is really frustrating. I've been playing OOTP for almost exactly ten years now, and I've seen some pretty amazing advances in the game engine, customization options, tracking of player statistics, etc. However, the attention to detail on an in-game level has simply never been there. If you play out 50-100 games you will see many bugs and errors that just shouldn't be there. It doesn't have to be this way - Diamond Mind was better at the in-game experience 5-10 years ago than OOTP is today. We have this amazing simulation engine with a great player development curve and it's welded to an in-game engine that's frankly pretty weak.

Finally, I don't say these things because I hate the game. I love this game; I've gotten more enjoyment out of OOTP than out of any other consumer item I've ever purchased. But it can be so much better, and it frustrates me that no one seems willing to fix the details, especially in-game details.

[pstrickert]

Bug reports updated to HERE.

[lt2cents]

when I am playing out a game.

On an injury the AI puts another player in the lineup- it should never do this if I am playing out the game-- that is my choice.

Give the incomplete lineup message and leave the spot open.

[CatKnight]

Version 13.3.9

Historical league, 1980 Boston (AL)

Replacing the DH with another DH is fine, but moving the DH to another position (which rightfully brings up a popup that my pitcher will bat for the rest of the game) results in a CTD when I try to finalize my lineup. This has happened twice.

[bjenglert77]

There is a very unrealistic occurrence that happens with every version that I play - hitters throughout the league getting five hits several times a week. In reality that might happen once or twice a season. Obviously must be a bug?

[endgame]

Not a bug post, but bug-related. I haven't had nearly the time available to me I'd have preferred during Markus' hiatus, but wanted to- in addition to my system "thanks" -put in a special thank you to pstrickert for diligently getting all of these concerns put into the appropriate arena for Markus' review for the upcoming patch/patches. Markus has time and again responded to the, "Why was this or that never dealt with?", with merit in inquiring, "Was this ever posted and reported as a bug, logged correctly, and assigned to me?"

Without pstrickert's efforts during this time off, rest assured a very few of your entries would have had a chance of receiving the attention they now- at least according to a system -will when Markus has a chance to review those submissions. So thank you for bringing problems to the forefront, but I huge hats off, pat on the back, attaboy, goes to the special effort by an extremely dedicated individual, determined to provide Markus all the tools he needs to improve the game.

Again, thanks 'strickert! You make a difference.

[pstrickert]

Thanks, eg. I've only done a small part. Other people (including yourself) do more work behind the scenes than the OOTP community realizes. Here's hoping that Markus reciprocates the effort.

[Calvert98]

Originally Posted by endgame

Not a bug post, but bug-related. I haven't had nearly the time available to me I'd have preferred during Markus' hiatus, but wanted to- in addition to my system "thanks" -put in a special thank you to pstrickert for diligently getting all of these concerns put into the appropriate arena for Markus' review for the upcoming patch/patches. Markus has time and again responded to the, "Why was this or that never dealt with?", with merit in inquiring, "Was this ever posted and reported as a bug, logged correctly, and assigned to me?"

Without pstrickert's efforts during this time off, rest assured a very few of your entries would have had a chance of receiving the attention they now- at least according to a system -will when Markus has a chance to review those submissions. So thank you for bringing problems to the forefront, but I huge hats off, pat on the back, attaboy, goes to the special effort by an extremely dedicated individual, determined to provide Markus all the tools he needs to improve the game.

Again, thanks 'strickert! You make a difference.

Good post endgame and agreed.

Cal

[akw4572]

I mentioned a while back, when using the edit schedule function, then analyze schedule, I get an error. I like to use it to see if a schedule is to my liking (it tells you how many games you play against each opponent before a season starts).

Sent from my Desire HD using Tapatalk 2

[JMDurron]

Playing with latest patch, MLB historical league.

I have found some additional detail on an issue discussed in this main forum thread.

Playing game 1 of a doubleheader. I normally play out both games of doubleheaders with no trouble whatsoever, but this time I did something different. I had something come up, and was forced to save the game and exit during game 1 of the doubleheader. This meant that when I opened the game back up, I was in Real Time Simulation Mode, with the scoring updates at the top instead of the normal schedule bar.

As an apparent side effect of RTS Mode, I could not use the Play Menu to Start Game 2 of the doubleheader as I normally do. I could only enter game 2 by going to the League -> Scores and Schedule menu, and selecting Manage. Once I enter the game, OOTP crashes following the first pitch of the game. This has happened twice, so it was not a one-time fluke. It appears that RTS and doubleheaders do not play nicely together when one has to save the game during game 1 of the doubleheader.

[pstrickert]

Originally Posted by bjenglert77

There is a very unrealistic occurrence that happens with every version that I play - hitters throughout the league getting five hits several times a week. In reality that might happen once or twice a season. Obviously must be a bug?

I have a hunch you're right. But do you have hard data? How does it compare with real life? You'll need the data to persuade Markus that a problem exists.

[JMDurron]

Originally Posted by JMDurron

Playing with latest patch, MLB historical league.

I have found some additional detail on an issue discussed in this main forum thread.

Playing game 1 of a doubleheader. I normally play out both games of doubleheaders with no trouble whatsoever, but this time I did something different. I had something come up, and was forced to save the game and exit during game 1 of the doubleheader. This meant that when I opened the game back up, I was in Real Time Simulation Mode, with the scoring updates at the top instead of the normal schedule bar.

As an apparent side effect of RTS Mode, I could not use the Play Menu to Start Game 2 of the doubleheader as I normally do. I could only enter game 2 by going to the League -> Scores and Schedule menu, and selecting Manage. Once I enter the game, OOTP crashes following the first pitch of the game. This has happened twice, so it was not a one-time fluke. It appears that RTS and doubleheaders do not play nicely together when one has to save the game during game 1 of the doubleheader.

I found a workaround to this issue. If you complete the Real Time Simulation for the day via the Play menu, it completes all the rest of the games in the league on that day, and then you can enter Game 2 as per normal. I still don't think that this is working as intended, but at least there's an easy workaround, all you lose is the real time view of other ongoing games during game 2 of the doubleheader.

[Eckstein 4 Prez]

Not a bug exactly, but I think this is probably where this should go.

One of the areas where the game has really improved since the days of OOTP4 (my first version) is the variety of the pbp. I play out a lot of games, so eventually there's little variety, but it now takes quite a while to see everything there is to see. (Here's hoping that we'll continue to add to this, and potentially to customize things further for individual announcers, but that's material for another post.)

However, there are some pbp combinations that really break the continuity of the game. It's always discordant to have that sudden reminder that the game is just sticking these words together at random. For instance, I just saw a fly ball to shallow center field. My pbp message was "[Center Fielder] coming on... and he makes the catch over his shoulder!" In reality, of course, no one catches a shallow fly ball over his shoulder - I don't even know what that would look like. I guess my suggestion is to comb through the pbp stuff a little more carefully to eliminate phrases that are inapplicable to certain situations - e.g., catching shallow fly balls over the shoulder.

[OutS|der]

Theres a bug when adding teams to a template, not sure if it happens other times when adding a team.

You try to add a division and add teams but it will move the teams aready created around.

Have a 2 subleagues, with two 6 team divisions when i try to add a 3rd and add teams it will move the other teams around

[Eckstein 4 Prez]

Another scoring bug - this one has to do with RBI and how they are awarded, as well as how to score things for the batter when there is an error on the play.

Runner at second, one out. Next batter bunts to the pitcher. Pitcher throws the ball away. At the end of the play, the batter is on second base and the runner on second has scored.

This should be scored as a sacrifice bunt plus a two-base error on the pitcher, and no RBI should be credited to the batter. If the play had gone as it should have the batter would have sacrificed the runner to third and would be out himself.

OOTP scores this as an out (not a sacrifice) for the batter, and an RBI for the batter. Both of these are wrong.

[Eckstein 4 Prez]

Originally Posted by Eckstein 4 Prez

Here's an in-game bug I've noticed for years; I'd somehow thought this one had been fixed a couple versions ago but I just saw it in a game.

This bug can only be seen in the bottom of the ninth (or tenth, eleventh, etc.) with multiple runners on the bases. In my case, it was bases loaded, one out in the 11th. The batter came up and hit a ball into the gap for the walk-off win. No problem there - it's how the game scored it that causes the bug.

The game gave the batter a double, and the home team a 1-0 win - i.e., only one of the three runners on base scored, which is an impossible situation.

I think I know how this bug came to be. In earlier versions of OOTP, batters would routinely hit walk-off doubles and triples, scoring two or three runs. That's not how it happens in real life, where everyone on base just advances as far as they need to on an obvious walk-off hit.

Someone must have pointed that out to the powers that be, so we no longer have "extra" runs scoring on walk-off hits. The problem is that the in-game engine hasn't been adjusted to give the batter credit for a single only in situations such as those that just occurred in my game. So we have a situation where there were three men on base, the batter hits a double, and one run scored. Evidently the extra runner got swallowed up by the earth or something.

Just saw a variant of this bug, though a less severe one. Bottom of the 13th inning, first and third, no one out. Batter hits a ball in the gap to end the game. In reality, this would be scored as a single, as the batter would stop and first and the trailing runner at third. OOTP correctly had the trailing runner stop at third, but gave the batter credit for a double.

A good rule of thumb is that the batter is never going to travel more bases than the lead runner on a walk-off hit unless the batter hits a home run. It is possible to have walk-off doubles, but they occur when there is a runner on first or something like that. In such a case, the batter will take the extra base because he wants to be in position to score in case the runner gets thrown out at home. However, obvious game-ending hits (e.g., when the runner is on third) will always be singles unless they are home runs.

[Pedro]

Hi folks,

First time player here, and congrats on a fantastic game.

Has anyone run into a bug where the starting rotation gets all mixed up? This starts to happen in season two or three for me. First time round, the game was starting my #1 pitcher two days in a row at the start of season 2. After a while he had started 19 games to everyone else's 9.

Second time around was with a new game, and it happened at the start of season #3. On opening day it started my #2 guy, and from then on, using strict 5 day rotation, it jumped around from man to man randomly. That wasn't too bad, as it still mostly picked each of the five guys before starting again, but after a few pitching changes it started starting a middle reliever for 4 innings on consecutive days, ignoring my 5 starter completely etc. hugely frustrating.

Changing to a most-rested setting did not help.

This is in a quick start game.

Can I do anything about this? Play with Commissioner mode turned on and force the correct starter?

Thanks in advance!

[zappa1]

I've seen some errors in scoring. In an extra inning game tied with the home team at bat. Bases loaded and batter hits a game ending triple or double. should be credited with only a single as only one run was needed to end the game. In the box score the batter was incorrectly given the extra base hit.
In another game, first and second. Called for a double steal. Catcher throws the ball away at third base for an error. Runner scores from second and runner from first ends up at third. Only the first runner was given credit for a stolen base, not the second runner. When you double steal without the catcher throwing the ball away, both runners ARE given a stolen base. It's only when the catcher throws the ball away that the second runner doesn't get credit for a stolen base.
I know these are minor scoring problems but the first one should be corrected.

[Eckstein 4 Prez]

Another scoring bug, and this one presents even more starkly the sacrifice fly-throwing error bug I've mentioned earlier.

2-2 tie game, bottom of the ninth, bases loaded, nobody out. Batter hits a fly ball to shallow center field. (Location code was 8RS.) Center fielder makes the catch, runner starts for home.

Let's stop here. In reality, this is one of the most exciting plays in baseball: either the runner will be safe at home and the game will end on a walk-off sacrifice fly, or the runner will be out on the double play, the game will continue, and the batter will be credited with a fly out. Those are the only two possibilities left at this point.

If the runner is safe in this situation, it does not matter whether the throw was a bullet to the plate, five feet up the line, or a wild one that ended up in the visiting dugout. It will always be scored the same - sacrifice fly, game over. This is because this is a difficult do-or-die play for the center fielder; it is exactly analogous to a catcher making a throw to second base to catch someone stealing. As long as the base stealer doesn't advance an extra base, the catcher doesn't get an error if the throw is high, off the bag, etc.

(One other nitpick that's fairly minor: in a situation like this where the trailing runners know with 100% certainty that the throw is going to home, they will both be advancing on the fly out as well, so that they will be on second and third if the runner is thrown out at home. The runner going from second to third will do so because they want the winning run 90 feet closer. The guy going from first to second will do so because they want him to stay out of a force out situation.)

Thus, this should be a completely binary situation: sacrifice fly and game over, or fly out and game not over. Instead, the center fielder airmailed the throw and the game scored it as a fly out and an E8, game over. Bizarrely, it also gave the batter an RBI, which is not consistent with that scoring, but of course the proper way to score this is SF, RBI, game over.