First to third play by play issue

Kelric · 07-01-2007, 01:28 PM

I've played five games in my current solo season and I've seen this bug twice already. I'm sure I've seen it in past leagues, but can't recall. Anyways, the situation has been men on second and third with a ball hit into the outfield. The man on second scores and the throw to the plate is cut off and sent to third base to nail the runner advancing from first. Both times the PBP has used the name of the batter rather than the runner when calling the play at third base and both times the runner has been safe (and the batter advances to second on the throw).

Zeyes · 07-01-2007, 01:42 PM

Do you mean men on first and second, rather than second and third?

Kelric · 07-02-2007, 01:01 PM

Err, yes. First and second. The keyboard must have switched keys on me or something.

battists · 07-11-2007, 04:30 PM

Erk, Kelric, this sounds likely to be an error in the XML file, but it's going to be impossible to track down without someone finding it again, and providing the exact text.

Do you recall, when specifically, is the name wrong? When the player is advancing to third? Or when they're making the call at third base?

For example, it makes a difference whether it's:

"Wrong Player heads for third . . . here's the throw from the catcher . . . Right Player is out!"

compared to

"Right Player heads for third . . . here's the throw from the catcher . . . and Wrong Player is out!"

If you do happen to get this again, PLEASE take a screenshot of the peculiar call!

(Note to self: might be category SAFE_CALL_CLOSE (#198))

Kelric · 07-12-2007, 03:34 PM

"Right player heads for third... throw from the cutoff man... wrong player is safe!"

Here's a better example:

Jose Reyes is on second base, David Wright is on first base, Carlos Delgado is at the plate.

Delgado knocks one into the gap, scoring Reyes. The throw goes home but is cut off and instead goes to third base trying to catch David Wright. When Wright slides into third, the PBP says that Carlos Delgado is safe at third even though when the player images move on the field, he is clearly at second with Wright at third and all further PBP text seems to get it right.

Kelric · 07-20-2007, 06:30 PM

Aha! Proof!

If you notice, it has Bellhorn going into 3rd but Bruce is the one sliding. The first two times I saw this it actually said (for example) 'And Bruce is safe at third!' rather than putting it into two different lines. But, still, it's basically the same bug.

Unfortunately in this situation, I'm the Astros. And my pitcher had just walked in the previous batter to force the run in.

Nutlaw · 07-27-2007, 05:24 PM

Tt 3803

Nutlaw · 08-01-2007, 07:22 PM

This has been claimed fixed for the third patch, as yet unreleased. If you continue to observe this issue after patching, please post as such in Tech Support along with the TT number listed above. Thanks.

07-01-2007, 01:28 PM	#1
Kelric Hall Of Famer Join Date: Mar 2002 Location: Greater Boston Area Posts: 3,992	First to third play by play issue I've played five games in my current solo season and I've seen this bug twice already. I'm sure I've seen it in past leagues, but can't recall. Anyways, the situation has been men on second and third with a ball hit into the outfield. The man on second scores and the throw to the plate is cut off and sent to third base to nail the runner advancing from first. Both times the PBP has used the name of the batter rather than the runner when calling the play at third base and both times the runner has been safe (and the batter advances to second on the throw).

07-01-2007, 01:42 PM	#2
Zeyes All Star Reserve Join Date: Jun 2006 Posts: 818	Do you mean men on first and second, rather than second and third?

07-02-2007, 01:01 PM	#3
Kelric Hall Of Famer Join Date: Mar 2002 Location: Greater Boston Area Posts: 3,992	Err, yes. First and second. The keyboard must have switched keys on me or something.

07-11-2007, 04:30 PM	#4
battists Hall Of Famer Join Date: Jul 2004 Posts: 18,506	Erk, Kelric, this sounds likely to be an error in the XML file, but it's going to be impossible to track down without someone finding it again, and providing the exact text. Do you recall, when specifically, is the name wrong? When the player is advancing to third? Or when they're making the call at third base? For example, it makes a difference whether it's: "Wrong Player heads for third . . . here's the throw from the catcher . . . Right Player is out!" compared to "Right Player heads for third . . . here's the throw from the catcher . . . and Wrong Player is out!" If you do happen to get this again, PLEASE take a screenshot of the peculiar call! (Note to self: might be category SAFE_CALL_CLOSE (#198))

07-12-2007, 03:34 PM	#5
Kelric Hall Of Famer Join Date: Mar 2002 Location: Greater Boston Area Posts: 3,992	"Right player heads for third... throw from the cutoff man... wrong player is safe!" Here's a better example: Jose Reyes is on second base, David Wright is on first base, Carlos Delgado is at the plate. Delgado knocks one into the gap, scoring Reyes. The throw goes home but is cut off and instead goes to third base trying to catch David Wright. When Wright slides into third, the PBP says that Carlos Delgado is safe at third even though when the player images move on the field, he is clearly at second with Wright at third and all further PBP text seems to get it right.

07-20-2007, 06:30 PM	#6
Kelric Hall Of Famer Join Date: Mar 2002 Location: Greater Boston Area Posts: 3,992	Aha! Proof! If you notice, it has Bellhorn going into 3rd but Bruce is the one sliding. The first two times I saw this it actually said (for example) 'And Bruce is safe at third!' rather than putting it into two different lines. But, still, it's basically the same bug. Unfortunately in this situation, I'm the Astros. And my pitcher had just walked in the previous batter to force the run in.

07-27-2007, 05:24 PM	#7
Nutlaw Hall Of Famer Join Date: Apr 2003 Posts: 9,538	Tt 3803

08-01-2007, 07:22 PM	#8
Nutlaw Hall Of Famer Join Date: Apr 2003 Posts: 9,538	This has been claimed fixed for the third patch, as yet unreleased. If you continue to observe this issue after patching, please post as such in Tech Support along with the TT number listed above. Thanks.