Updated Garlon/Arod23 DB Available

[arod23]

See Readme Files

*NEW to v.2.0*

- Deleted fielding data (eligibility) for positions where players did not play a significant portion of games

- Deleted UA/PL/FL league players who did not have significant playing time in other leagues
These leagues are considered by experts to be below “major” league levels. If included, these players influence the outcome of league performance in subsequent seasons.

- Created OF eligibility in other OF positions
Based on each player's primary OF position, we adjusted the games played in the other OF positions so OOTP would assign ratings for all OF positions. The reason is that OOTP only gives fielding ratings in OF positions in which a player actually played. So, OOTPs AI will not give a RF player eligibility in LF if they do not have any ratings. This creates situations where a team may have no eligible LF on a team but actually have six OFers. And, the AI may even insert a player that has no OF experience. Realistically, OFers should be able to play in any field, although their effectiveness may not warrant such a move. So, CF now get rated in the corners at roughly half their effectiveness. Corner OFers get rated in the opposite corner at half effectiveness and in CF at 25% effectiveness. Due to the way the two fielding files are setup, this was only done for 1871-1995 OF positions. So, players post-1995 will only have OF eligibility where they have accumulated actual stats. (We are working on ways to address this).

- Fixed zero "errors" in pitching and batting files.
We added 1 BB or 1 SO to a few players who had zeros for BB and SO data, typically players with little playing time. When BB and SO data is zero, OOTP's ratings for Gap, Eye, Ks, Control are out of line with other players (likely due to some ratio equation which doesn't like zero in the numerator or denominator). For example, zero strikeouts in 600 at bats is impressive and should be rewarded with a great K rating, but zero strikeouts in 5 at bats doesn't really warrant the same kind of rating. Also, players with triples and no doubles caused strange gap ratings, so in those cases we gave players one double. Very few players were affected.

- Fixed leap year birthdays.
In some cases, leap year birthdays (February 29th) cause an import error. These birthdays were changed to February 28.

The following files are also included for user preference:

- FieldingOF-actualOF.csv
This is the original OF file based on the actual historical OF data and does not include players having eligibility in other OF positions.

- Master-NoNicknames.csv
Copy of the master file with nicknames removed. Catobase for OOTP6.5 does not do well with nicknames.

[arod23]

A career average DB, based on our DB, is now available for downloading.

1. What is the Career Average DB format?
The Career Average format applies a player's average season statistics to all seasons in which he played.

2. When would I want to use this DB format vs the regular format?
You may want to use this format for importing rookie classes after first creating your league with the regular format DB.
The career average format should produce better results with pitcher development.
For single-season replays in which you are not interested in moving to the next season, the regular format is the better choice.

3. What are the pros and cons to the career average format for hitters?
With the career average format players will import based on their career average rather than their actual rookie stat line.
For a hitter like Ty Cobb, whose career average was .367, he will start out close to being able to hit that .367 mark of his career and he will consistently hit for a high average, but may never hit over .400.
With the regular fomat he may start out as a .315 hitter and gradually get better and may hit .400 a couple times.
However, there is probably a better chance he doesn't reach his full potential with the regular format and ends up as a bust.
Using either format, Cobb's career totals will be very similar, but the career arc will be very subtle with the career average format.
In a nutshell, using the career average format may give you more consistency but limit big single season performances somewhat.
Some players who had very poor rookie seasons but otherwise great careers, i.e. Ed Delahanty and Mike Schmidt, may never develop at all with the regular format but will become the great players they should be with the career average format since they start out stronger.

4. Why is the career average format better for importing rookie pitchers?
With the regular format DB there are alot of one-season rookie-wonder pitchers - meaning pitchers who had a great rookie season an therefore great initial ratings, but poorer potential ratings.
What happens is that many of these rookie wonders steal starting rotation spots away from pitchers who otherwise are much more deserving of a rotation spot.
Great pitchers often end up in the pen or busting because of so many of these types of pitchers filling up starting rotations.
The career average format smooths things out by making great pitchers better as rookies while the rookie wonder pitchers have their talent decreased since it is averaged together with their remaining career performance.
With the regular DB format, many great pitchers import with low endurance ratings which will also relegate them to bullpen duty.
With the career average format their endurance ratings which will be on target.

5. Ok, I like the idea of pitchers turning out better with the career average format, but I'd still rather have my hitters import as rookies in the regular format. Can I do this?
Yes.
In the Career Average folder you will see a file called Batting.csv, rename this file avgBatting.csv or something else.
You will also see a file called "Regular_Batting.csv", rename this file to Batting.csv.
Your hitters will now import in the regular format, while your pitchers will still import in Career Average format.
You now have a hybridized DB.

[arod23]

Some pitchers were still importing as DH, so we have updated the fielding.csv file. Most of these players were pre-1900.

[arod23]

CareerAvg DB update v2.1r available for download