|
||||
|
|
OOTP 20 - General Discussions Everything about the newest version of Out of the Park Baseball - officially licensed by MLB.com and the MLBPA. |
|
Thread Tools |
10-15-2019, 06:20 PM | #1 |
All Star Reserve
Join Date: Jul 2011
Posts: 598
|
Importing Old Saves
I really wish that there was an easier way to import old saves. I wonder if the team could make a program to convert old saves into the latest version. Having to download and import to every version until the current version is rather tedious. I keep putting off importing an old OOTP 16 save into 20. E.g. I would have to download and import to 16, 17, 18, and 19 before importing to 20.
|
10-16-2019, 11:05 AM | #2 |
Hall Of Famer
Join Date: Jul 2003
Location: Somerville, MA, USA Bats: Right Throws: Left
Posts: 3,621
|
Because of all the new features that are added, you'd probably find a lot of incompatible data when trying to import information from many moons ago into a new DB. The import tool is probably not equipped to handle unnamed tables.
You're talking about an hour or two of your time to import into the old saves through the demo of the previous versions. |
10-16-2019, 01:07 PM | #3 |
Hall Of Famer
Join Date: Apr 2015
Posts: 7,167
|
you could use spreadsheets to more simply convert the stats and player exports... then, re-use playerid's. that's a simply process, but could be intimidating for some. you'd lose all the news stories and anything else not contained in the stats history and player list.
you have to make sure enough playerIDs exist. you'd have to create them, which could be hundreds of thousands in some cases. not sure of that type of scale.. could bring about more obstacles to overcome. anyway, on top of enough player id's it'd be best to have the same exact structure... ensure the team ids are the same, if not, keep existing. as long as same names/city and league structure, it will be in the same order at minimum. anyway,a1-cell on output sheet "=sheet1.a1" type links to a cell on next worksheet, fill across and down. you can have the playerid's coming from one imported data-linked sheet, and ratings and correct info coming from a 2nd data-linked spreadheet (to the respective exported files) if team ids are wrong, go fix those rows -- just pull from correct worksheet and fill across. once you set this up one time (assuming all ML rosters are equally full -- about teamid row being in correct repetitive sequence etc), it will work th emoment you re-link those other worksheets to the new exported files. may have to adjust size of the output table, but if you used the 'fill' function with the formulas and such, then it auto-increments and you simply fill further down. basically, you pull the bits you re-use from the destination league's exports, then dump all the other data from the source league. using formulas in the cells of third "output" worksheet makes it re-useable. just save that 'output' worksheet as a csv file; delimited as the source files were. The other kicker, as mentioned, is that some stuff is new. if it doesn't exist in your '16 league, you have to either put zeros, or 1/2 scale or random data into those cells. all easily accomplished with a spreadsheet too. blanket data is a simple copy/paste with successively doubling blocks. a randome function with min/max could be a simple fill after you type out one formula into 1 cell. you have to match the format of the newest exported file, of course. you can highlight and move sections of the table, if needed. becareful, there are ways to move/cut things that automatically change your cell formulas, and there are ways to move/cut things that keep them the same as you change its location. ctrl-z and ctrl-y are your friends. *e.g. you move a portion of the table 2 rows over to accomodate for two new columns in the newer game, you can either change all those cells to reference the wrong cell, 2 rows over, or it can stay the same depending on how you do it. Last edited by NoOne; 10-16-2019 at 01:10 PM. |
Bookmarks |
|
|