Catobase and OOTPs 255 earned run limit

[arod23]

I, like many others, ran into the 255 earned run limit issue on OOTP (RBIs and Runs I believe also have this limitation) . So, I used the Career Editor utility to reset those player's stats to 255 earned runs (even though they had more). Since the Career Editor can only be utilized once you "proceed to the next season" (b/c the current season doesn't show up), the adjustments won't be reflected until the following season's files. My question is: Does Catobase readjust the players stats for previous seasons and subsequently for the career boards if the Career Editor is used on the OOTP files? Or (I hope not!), do I have to modify Catobase's data files directly?

[jcato]

CatoBase tries to make this correction. I make some assumptions that may or may not be the best ones, but here's what it does for each pitcher after importing the data:

1. If H <> 1B+2B+3B+HR, then set 1B=H-2B-3B-HR
2. If ER<100 AND IP>300 AND Losses>20, then set ER=ER+256 and RBI=RBI+256
3. If ER>R, then set R=R+256

I may need to revisit that, I'm not sure why I used losses greater than 20, but it seems to pretty much work.

[arod23]

Originally Posted by jcato

CatoBase tries to make this correction. I make some assumptions that may or may not be the best ones, but here's what it does for each pitcher after importing the data:

1. If H <> 1B+2B+3B+HR, then set 1B=H-2B-3B-HR
2. If ER<100 AND IP>300 AND Losses>20, then set ER=ER+256 and RBI=RBI+256
3. If ER>R, then set R=R+256

I may need to revisit that, I'm not sure why I used losses greater than 20, but it seems to pretty much work.

It doesn't seem to be working (I am using 6.0.0). In theory, your fixes would solve 9/10 of the issues. I did some experimenting last night. Using Career Editor on the OOTP files doesn't change past Catobase records during the next import. So, I had to go into the Catobase database file directly and modify each batter and pitcher manually. I then reran the queries to update Career and SeasonHigh and SeasonAvg etc (I wasn't sure if your program re-queries before producing the html files, does it?? If so, that would save a big step). That obviously worked, but your approach above would be ideal.

I realize that this is not your bug but OOTPs and it should decrease in frequency over time. That is, since I am simming historically from 1901, I expect it to occur less often as I progress through time, i.e., no more 4 man rotations, less complete games, relievers, etc. Of course, the 255 limit is compounded by the fact that OOTPs AI will keep using a pitcher that has a high ERA, few wins, 30+ losses (one team had a #2 starter 2-32 with 300+ innings and a 12.30 ERA).