Reliever credited with Hold despite getting no outs

Zeyes · 07-17-2006, 07:40 PM

As previously mentioned in the other Hold-related thread...OOTP gives out Holds to relievers, even if they failed to get anybody out before the next guy comes in. Granted, Holds aren't part of the official rulebook, but MLB does say that at least one out is necessary on its Rules and Regulations Miscellany page, and looking at MLB box scores, they do apply that rule, see e.g. ARI @ ATL, June 3rd - Arizona's Mulholland did not receive a Hold, even though he came on in a Save situation (10-7, one on), and did not surrender the lead (he did give up a two-run homer

).

Anyway, a bunch of screenshots (three of 'em pasted together) to show that OOTP is consistently doing it wrong:

battists · 07-21-2006, 01:47 PM

Logged as TT #2370.

Thanks,

Steve

battists · 08-21-2006, 08:31 AM

Markus has claimed that this issue will be fixed in 1.0.3. However, we have not yet received a test version of 1.0.3 with which to verify.

Thanks very much,

Steve

07-17-2006, 07:40 PM	#1
Zeyes All Star Reserve Join Date: Jun 2006 Posts: 818	Reliever credited with Hold despite getting no outs As previously mentioned in the other Hold-related thread...OOTP gives out Holds to relievers, even if they failed to get anybody out before the next guy comes in. Granted, Holds aren't part of the official rulebook, but MLB does say that at least one out is necessary on its Rules and Regulations Miscellany page, and looking at MLB box scores, they do apply that rule, see e.g. ARI @ ATL, June 3rd - Arizona's Mulholland did not receive a Hold, even though he came on in a Save situation (10-7, one on), and did not surrender the lead (he did give up a two-run homer ). Anyway, a bunch of screenshots (three of 'em pasted together) to show that OOTP is consistently doing it wrong:

07-21-2006, 01:47 PM	#2
battists Hall Of Famer Join Date: Jul 2004 Posts: 18,506	Logged as TT #2370. Thanks, Steve

08-21-2006, 08:31 AM	#3
battists Hall Of Famer Join Date: Jul 2004 Posts: 18,506	Markus has claimed that this issue will be fixed in 1.0.3. However, we have not yet received a test version of 1.0.3 with which to verify. Thanks very much, Steve