Quote:
Originally Posted by hawk236
I hope you don't mind bu I was looking through the transaction reports of your league and noticed this player who illustrates a similar but different problem: http://www.unitedbaseball.org/ootp20...ayer_6747.html
I thought his transactions looked a little strange being that they were not in chronical order:
<TABLE class=lpo style="MARGIN-BOTTOM: 12px" cellSpacing=0 cellPadding=0 width=911><TBODY><TR><TD class=slg width=80>05-01-2017</TD><TD class=slg width=831>Released by the Pittsburgh organization.</TD></TR><TR><TD class=sl width=80>05-13-2017</TD><TD class=sl width=831>Signed a 1-year minor league contract with the Atlanta Braves organization.</TD></TR><TR><TD class=slg width=80>06-06-2017</TD><TD class=slg width=831>Released by the Atlanta organization.</TD></TR><TR><TD class=sl width=80>05-16-2017</TD><TD class=sl width=831>Signed a 1-year minor league contract with the Atlanta Braves organization.</TD></TR><TR><TD class=slg width=80>06-01-2017</TD><TD class=slg width=831>Released by the Atlanta organization.
</TD></TR></TBODY></TABLE>
Looking at the team transaction report here: http://www.unitedbaseball.org/ootp20...tions_0_0.html
It seems that the 5-13 and 6-6 transactions never happened. Again sorry if I am poking my head in where it isn't wanted but it seems that at the very least the reports are reporting wrong and I thought I should point it out to be looked at.
|
Yeah, thanks. I didn't notice that until I was looking at the waiver claims. I wonder if this is related to the crash while I was generating reports...who knows.
Either way, there are way too many transactions. I am seeing guys get waived like 3-4 times before the break, guys getting signed, cut, signed, cut. It seems like the AI likes to recycle really bad guys.