OOTP Database Converter

[DrDoom]

I've merged my database conversion tools into a single program with a simple to use GUI for both Windows and MacOS.

The program is much more straight forward now. Simply select a folder where the files you want to convert are stored and a folder where you'd like the newly created files to be saved and click the appropriate convert button.

User Guides

OOTP Database Converter Guide (Windows)

OOTP Database Converter Guide (MacOS)

Database Converter

OOTP Database Converter (Windows)

OOTP Database Converter (MacOS)

OOTP Database Converter (Source Code)

Feel free to reach out to me if you have any issues running the program.

Note: The OOTP Database Converter currently isn't capable of converting a database from one version of OOTP to another. Databases can only be disassembled and rebuilt for a single version of the game.

Please ALWAYS back up the original databases before replacing them with your modified ones.

[No Pepper]

Thank you Dr. Doom for your work on this! I used your previous version but have yet to reap the benefits of it for a minor league team project I am/was working on.

[DrDoom]

Originally Posted by No Pepper

Thank you Dr. Doom for your work on this! I used your previous version but have yet to reap the benefits of it for a minor league team project I am/was working on.

Thanks for the accolades! I’m a big fan of your uniform files. I should have a version for OOTP 22 in the very near future.

[DrDoom]

Just put the finishing touches on the MacOS version today and it can be downloaded above.

[DrDoom]

Added Database conversion tools for OOTP 22 for both Windows and MacOS. They can be downloaded above in my initial post.

[plannine]

Thank you.

[Ty Cobb]

Thanks for a Mac version. Looking forward to checking this out while virtual box is incapacitated (won't run on Monterey yet).

[DrDoom]

Originally Posted by Ty Cobb

Thanks for a Mac version. Looking forward to checking this out while virtual box is incapacitated (won't run on Monterey yet).

Let me know how it goes and if you run into any issues.

[Ty Cobb]

Will do. I ran it once to create the csv's, and they look pretty good so far. A lot of data to wade through...

[Makonnen]

If this lets me do what I think it will, I owe you a beverage of choice.

* Am I correct that I could use this to, say, enter a few hundred negro league player MLE's year by year, and then have them appear in the game?

A note on the instructions: for me at least, the /stats folder is in the steam/steamapps hierarchy, not under the /[user]/documents group.

Finally, on the .csv files. It looks like the _normalized stats are normalized for ballparks, not for leagues, correct? Does anyone know if the _normalized rows are required?

[Makonnen]

@DrDoom, how long did it take you to do the work to modify this from ootp21 to ootp22? And, how open are you to sharing that work?

My guess is I'm a year, maybe more, from having the complete set of MLEs in final form. I'd prefer not to be locked into ootp22 forever, but the notion of, each year, having to reproduce an updated set of the master, batting, and pitching files would be fine.

[DrDoom]

Originally Posted by Makonnen

* Am I correct that I could use this to, say, enter a few hundred negro league player MLE's year by year, and then have them appear in the game?

Yes but you'll need to be careful with player and team ids. There currently isn't anything in the code that will validate these for you.

Originally Posted by Makonnen

A note on the instructions: for me at least, the /stats folder is in the steam/steamapps hierarchy, not under the /[user]/documents group.

I didn't even consider the different steam installation directories and I'll have to update the guide to reflect it. Just know that you'll need to do all your database editing from the home directory or a directory within the home directory as Apple isn't a fan of anyone doing anything outside the user directories.

Originally Posted by Makonnen

Finally, on the .csv files. It looks like the _normalized stats are normalized for ballparks, not for leagues, correct? Does anyone know if the _normalized rows are required?

I believe you are correct on the stats being park normalized. Not sure if not having them will cause issues. You're given the option to use one or the other for generating ratings when starting a new historical league.

[DrDoom]

Originally Posted by Makonnen

@DrDoom, how long did it take you to do the work to modify this from ootp21 to ootp22? And, how open are you to sharing that work?

My guess is I'm a year, maybe more, from having the complete set of MLEs in final form. I'd prefer not to be locked into ootp22 forever, but the notion of, each year, having to reproduce an updated set of the master, batting, and pitching files would be fine.

I plan on making it open source sometime in the near future. Want to comb the code over one last time before I do. Do you have programming experience? Is it something you'd like to help out with?

[Makonnen]

Man I was sure I had answered this several weeks ago. Yoikes.

I have extensive database/data architecture experience, very outdated web development experience, and minimal formal development language experience. But if I can help, I'd be more than willing to.

[Makonnen]

Originally Posted by Makonnen

Man I was sure I had answered this several weeks ago. Yoikes.

I have extensive database/data architecture experience, very outdated web development experience, and minimal formal development language experience. But if I can help, I'd be more than willing to.

Yeah, somehow my original response got posted as a .... blog???? https://forums.ootpdevelopments.com/blog.php?u=72659

No idea how I managed that ....

[DrDoom]

Originally Posted by Makonnen

Man I was sure I had answered this several weeks ago. Yoikes.

I have extensive database/data architecture experience, very outdated web development experience, and minimal formal development language experience. But if I can help, I'd be more than willing to.

It's written in C# which is far less complicated than C or C++. I'll keep you in the loop when I get around to open sourcing it. Perhaps your database experience can come in handy for expanding the converter's functionality.

[Makonnen]

I assume this is better addressed here than in the blog? You had asked

What issues I was having with the fielding.csv file

They are more issues of comprehension than technical. Summarized as

* As far as I can tell, the fielding ratings in master.csv are meaningless. But I have more testing before I can declare this absolutely.
* My questions for fielding.csv are basically What is the minimum data required to identify a player's position and their rough level of skill?

My testing so far indicates that if you specify a player's info in their first season (that is, the first season for which you have matching data in either batting.csv or pitching.csv), it works well to limit the player to a set of positions for their career. But I have not been able to effectively shape the quality of their defensive contributions.

I am *trying* to figure out how to tell OOTP this guy played all 3 OF positions, and was GG quality in RF or this guy played 3B, horribly with as little data entry as possible.

For the former, I am getting OK-but-not-great results by estimating G for each of the OF positions and doing something like 1.5 for the OF ratings for CF and 1.1 for the OF ratings for LF and RF.

For the latter, I am getting OK-but-not-great results by estimating G and then using .75 for the IF ratings.

Clearly, there can be nuance in making the OFArm 1.8 and the OFError 1.2 for someone who made a bunch of errors but had a great arm.

[DrDoom]

Originally Posted by Makonnen

I assume this is better addressed here than in the blog? You had asked



They are more issues of comprehension than technical. Summarized as

* As far as I can tell, the fielding ratings in master.csv are meaningless. But I have more testing before I can declare this absolutely.
* My questions for fielding.csv are basically What is the minimum data required to identify a player's position and their rough level of skill?

My testing so far indicates that if you specify a player's info in their first season (that is, the first season for which you have matching data in either batting.csv or pitching.csv), it works well to limit the player to a set of positions for their career. But I have not been able to effectively shape the quality of their defensive contributions.

I am *trying* to figure out how to tell OOTP this guy played all 3 OF positions, and was GG quality in RF or this guy played 3B, horribly with as little data entry as possible.

For the former, I am getting OK-but-not-great results by estimating G for each of the OF positions and doing something like 1.5 for the OF ratings for CF and 1.1 for the OF ratings for LF and RF.

For the latter, I am getting OK-but-not-great results by estimating G and then using .75 for the IF ratings.

Clearly, there can be nuance in making the OFArm 1.8 and the OFError 1.2 for someone who made a bunch of errors but had a great arm.

OOTP has always seemed a little wonky in the way it computes defensive ratings for historical players. I was always under the impression OOTP chose a player's defensive position based on where they played the most... I'll have to experiment a bit to confirm though. If you're giving a player stats at multiple positions, it could be throwing OOTP off when it's trying to resolve their position - even if you're giving the player considerably more playing time at a particular position. Not sure what the best work around for that may be... although, I'm pretty sure Spritze and/or Gambo have discussed this very issue in the past. I'll check the forum's and see what I can find.

[actionjackson]

HO. LEE. ****!!!

This is an absolutely ingenious piece of software. Ever since the historical database went on .odb lockdown, I've been looking for a way to fix things that irk me, and now tah-dah!!! Wow!

[actionjackson]

It's great...And yet not so great...My OCD just hit warp speed!