I need to upgrade the exporter

[CommishJoe]

Turns out I have been exporting the 'scout' values of the ratings the entire time. I just received the e-mail from Markus giving me the information I need to upgrade the exporter to report the "true" ratings. So, here is what I am going to do:

1. Change the exporter to show the actual ratings instead of the scout ratings in the current columns.
2. Add columns at the end of players.csv to show scout level ratings.
3. Add columns at the end of players.csv to show scout level talent(currently only reporting the actual values).

This will have the effect of automatically converting BOSI and CATO to using the actual ratings, while reporting on scout level ratings/talents so I can get BOSI to support scouts in the future.

This should fix some issues I had with the exporter showing wrong rating information from time to time.

[kq76]

While you do that, could you look at doing the following to the finances in teams.csv?

-make payroll #s (TY and LY) show (they only show 0s for me)
-rename the "total" columns (TY and LY) to player expenses, which is what I think those #s reflect now
-maybe create a total revenues (TY and LY) columns (and possibly total expenses columns in the hopes that Markus may add more expenses in the future)
-and reorganize it so all TY columns are together and likewise with the LY columns
-separate $ columns from other finance columns like attendance #s etc

TY = this year
LY = last year

Thanks. Only the payroll column is really important, but the rest would be nice.

(Post 1000)

EDIT: that reminds me, I was going to add team batting pitching and fielding stats to my Excel History, but teams.csv shows 0s for some of those stats and doesn't have columns for others. If you'd like me to list which ones exactly, let me know.

[CommishJoe]

1st -- Not sure what I can do about the payroll figure since it's not stored correctly in the teams.dat. I'll talk with Markus about this to see if I am just pulling from the wrong column. If it is, I'll see what I can do about calculating it (right now, I calculate it inside BOSI using information in the players.csv).

2nd -- I won't re-order any columns in any of the CSVs. CATO and BOSI are using the current .CSVs to import their data. If I changed the order, I would screw up both of their importers.

3rd -- I'll do the rest.

[kq76]

Thanks.

Originally posted by CommishJoe
2nd -- I won't re-order any columns in any of the CSVs. CATO and BOSI are using the current .CSVs to import their data. If I changed the order, I would screw up both of their importers.

Sorry, I think I went off daydreaming of an ideal world. But you're right. When OOTP6 arrives do you think you might totally revamp the exporter then? If so, I'll keep ideas like that for later.

Did you happen to catch my edit before you replied?

[CommishJoe]

Originally posted by kq76
Thanks.
Sorry, I think I went off daydreaming of an ideal world. But you're right. When OOTP6 arrives do you think you might totally revamp the exporter then? If so, I'll keep ideas like that for later.

Unless the importers have to be completely remodeled to support v6, I won't change the order of the CSVs. I know they might become a mess, but I really don't want people to have to re-work their utilities due to a change in format. Also, utilities like BOSI and CATO would have to support 2 different importers for people who don't upgrade to v6. So, at this point, I'd say the chance of a re-design of the CSV format is slim to none.

Originally posted by kq76

Did you happen to catch my edit before you replied?

Nop If a stat is 0 in the exporter, it's because it's not stored in the .dat file. Since the field existed, I exported it in the hopes that Markus would support it in the future. If the stat can be calculated, feel free to list it here and I'll see if I can get the calculations in the next version.