FOF7 - Exported Data -What should be added, changed, fixed?

[Dutch]

Issues/Concerns
- Team Schedules – Pre-Season and Regular Season games do not show up until played
- Player Information – ‘Chosen Team’ links to Team_Id ‘0’ by default. Should be ‘99’ or something else until determined since Team_id = Arizona
- College_id, hometown_id, and state_id information cannot be mapped to a name because name tables don’t exist
- Rookies.csv does not include the Base Grade info

Suggestions/Request
- Display all stage/week information as integers instead of a character variables
- Please add Global Future Ratings (green bars), if there is a feasible/logical way

[Ben E Lou]

Is anyone esle finding that there's a space at the beginning of text fields in the export? Is this just an Excel issue?

[Ben E Lou]

Hmmm..yeah...there's a space there in the raw file. Any ideas on how to deal with this easily?

Player_ID, Last_Name, First_Name, Junior_Flag, Nickname, Position, Player_of_Game_Count, Championship_Rings, Player_of_the_Week_Count, Height, Weight, Hall_of_Fame_Flag, Year_Inducted, Percentage_of_Vote, Chosen_Team, Year_Born, Month_Born, Day_Born, College, Draft_Round, Drafted_Position, Drafted_By,Draft_Year, 4th_Quarter_Comebacks, Quarterback_Wins, Losses, Ties, Home_Town, Home_State, Career_Games_Played, Number_of_Seasons, Season_1_Pointer_to_Player_Year_Data, SP_2, SP_3, SP_4, SP_5, SP_6, SP_7, SP_8, SP_9, SP_10, SP_11, SP_12, SP_13, SP_14, SP_15, SP_16, SP_17, SP_18, SP_19, SP_20, Season_1_Year, SY_2, SY_3, SY_4, SY_5, SY_6, SY_7, SY_8, SY_9, SY_10, SY_11, SY_12, SY_13, SY_14, SY_15, SY_16, SY_17, SY_18, SY_19, SY_20
1, Flynn, Nate, 0, , K, 0, 0, 0, 69, 183, 0, 0, 0, 0, 1978, 7, 20, 153, 28, 6, 30, 2013, 0, 0, 0, 0, 11434, 42, 0, 0, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
2, Chase, Paxton, 0, , P, 0, 0, 0, 74, 217, 0, 0, 0, 0, 1981, 10, 23, 21, 36, 20, 16, 2013, 0, 0, 0, 0, 13409, 49, 0, 0, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

[WheelsVT]

Hmmm..yeah...there's a space there in the raw file. Any ideas on how to deal with this easily?

Player_ID, Last_Name, First_Name, Junior_Flag, Nickname, Position, Player_of_Game_Count, Championship_Rings, Player_of_the_Week_Count, Height, Weight, Hall_of_Fame_Flag, Year_Inducted, Percentage_of_Vote, Chosen_Team, Year_Born, Month_Born, Day_Born, College, Draft_Round, Drafted_Position, Drafted_By,Draft_Year, 4th_Quarter_Comebacks, Quarterback_Wins, Losses, Ties, Home_Town, Home_State, Career_Games_Played, Number_of_Seasons, Season_1_Pointer_to_Player_Year_Data, SP_2, SP_3, SP_4, SP_5, SP_6, SP_7, SP_8, SP_9, SP_10, SP_11, SP_12, SP_13, SP_14, SP_15, SP_16, SP_17, SP_18, SP_19, SP_20, Season_1_Year, SY_2, SY_3, SY_4, SY_5, SY_6, SY_7, SY_8, SY_9, SY_10, SY_11, SY_12, SY_13, SY_14, SY_15, SY_16, SY_17, SY_18, SY_19, SY_20
1, Flynn, Nate, 0, , K, 0, 0, 0, 69, 183, 0, 0, 0, 0, 1978, 7, 20, 153, 28, 6, 30, 2013, 0, 0, 0, 0, 11434, 42, 0, 0, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
2, Chase, Paxton, 0, , P, 0, 0, 0, 74, 217, 0, 0, 0, 0, 1981, 10, 23, 21, 36, 20, 16, 2013, 0, 0, 0, 0, 13409, 49, 0, 0, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

If you are web programming then in php you can run a trim() function to trim off leading and trailing whitespace.

[Dutch]

I'm not sure if this is the right place or not, but I'd like to throw out ideas as I get them here for the exported data. Please let me know if there is a better avenue to articulate these things.



New Field requests...

team_information.conf_id(INT)
team_information.div_id(INT)
team_information.nickname(VARCHAR)
team_information.owner_name(VARCHAR)

[Dutch]

Would it make sense to split the 'universe_info' table? Personally, I'm not very good at deciphering the best way to implement that information as it is.

However, something like this would be very helpful to me.

'game_stage' {stage_id(INT), stage_title(VARCHAR), current_year(INT)}
'current_game_info' {salary_cap(INT), min_salary(INT)}
'draft_order' {round(INT), position(INT), orig_team(INT), cur_team(INT)}

[Ben E Lou]

PoW mentions is there, but PoW wins is not.

[Dutch]

Here is a list of all the stages in FOF7. This will help with updated web-sites. The current stage is identified in the 'universe_info' stage.

stage_id stage_name
1 Pre-Staff Draft
2 Staff Draft
3 Pre-Free Agency
4 FA Stage 1
5 FA Stage 2
6 FA Stage 3
7 FA Stage 4
8 FA Stage 5
9 FA Stage 6
10 FA Stage 7
11 FA Stage 8
12 FA Stage 9
13 FA Stage 10
14 FA Stage 11
15 FA Stage 12
16 Amateur Draft
17 Pre-Late FA Period
18 Late FA Stage 1
19 Late FA Stage 2
20 Late FA Stage 3
21 Late FA Stage 4
22 Late FA Stage 5
23 Pre-Training Camp
24 Ex. Season Week 1
25 Ex. Season Week 2
26 Ex. Season Week 3
27 Ex. Season Week 4
28 Ex. Season Week 5
29 Reg. Season Week 1
30 Reg. Season Week 2
31 Reg. Season Week 3
32 Reg. Season Week 4
33 Reg. Season Week 5
34 Reg. Season Week 6
35 Reg. Season Week 7
36 Reg. Season Week 8
37 Reg. Season Week 9
38 Reg. Season Week 10
39 Reg. Season Week 11
40 Reg. Season Week 12
41 Reg. Season Week 13
42 Reg. Season Week 14
43 Reg. Season Week 15
44 Reg. Season Week 16
45 Reg. Season Week 17
46 Wild Card Round
47 Divisional Round
48 Conference Round
49 Front Office Bowl
50 End of Season

[Dutch]

I've created a single 'player_ratings' database that I will need to import 'player_ratings_season_yyyy' csv's into.

A 'master_record' field that is null would be a nice addition to the 'player_ratings_season_yyyy' files. That way our db's can have a primary_key that auto-increments. Adding a 'year' column would be a plus.

[Dutch]

I don't see team schedules in the exported data...just the completed games. Am I missing that?

[Ben E Lou]

Schedules are not there.

[Dutch]

Ok, thanks for verifying.

[aston217]

Add schedules to the list of 'should be there', on a _yyyy basis.

[Ben E Lou]

No. Schedule results are there. If we could just have the rest of the games--with zeros for results--of the current year included in the one csv, that would be fine (and easier.)

[aston217]

Won't that get replaced every year? How would you display schedule results from previous years?

[WheelsVT]

You don't need a blank field in the csv to have a primary key in the DB that auto-increments. Unless I'm missing something you can just have the field in the DB and when you insert a record the key will be populated on its own.

I've created a single 'player_ratings' database that I will need to import 'player_ratings_season_yyyy' csv's into.

A 'master_record' field that is null would be a nice addition to the 'player_ratings_season_yyyy' files. That way our db's can have a primary_key that auto-increments. Adding a 'year' column would be a plus.

[Ben E Lou]

Won't that get replaced every year? How would you display schedule results from previous years?game_information has results for every game in the league's history with a "year" column. Add the unplayed games for the current season to that list, and that's all that's needed.

[Dutch]

You don't need a blank field in the csv to have a primary key in the DB that auto-increments. Unless I'm missing something you can just have the field in the DB and when you insert a record the key will be populated on its own.

I was getting an error when importing because I created a 'master_record' column in the table. So I had to add an extra column into the yearly record.

I was concerned about duplicate records, but I suppose I could just as easily make a key based on record and year.

[Dutch]

I decided to add a master_record because I kept getting an error with duplicate entries...and with a few of the player_season csv's having corrupt data, it was just easier to make the master_record.

[WheelsVT]

I don't believe the QB Formations attribute is exported in the ratings. I'm having to backfill it with 0s for now in Conscriptor.

[Dutch]

I've consolidated all notes. I plan to send this info to Jim/Ben on wed. If you have anything, please post it here.

[Dutch]

All issues/suggestions raised here have been sent to Solecismic's e-mail support e-mail.

[gstelmack]

If I were to revive Draft Analyzer, it would want:

- Formation information for QBs
- Birthdates (for potential affinity / conflict reporting)
- Bar min/maxes

in the rookie player CSV. I have to double-check, it would be good for the player id to be in there as well (we could then hook all that up so we had correct rookie combines for everyone, and Ben wouldn't have to rename rookies to avoid duplicate names...)

[WheelsVT]

If I were to revive Draft Analyzer, it would want:

- Formation information for QBs
- Birthdates (for potential affinity / conflict reporting)
- Bar min/maxes

in the rookie player CSV. I have to double-check, it would be good for the player id to be in there as well (we could then hook all that up so we had correct rookie combines for everyone, and Ben wouldn't have to rename rookies to avoid duplicate names...)

:+1: for Conscriptor

Though the rookie bar min/maxes are team specific right, just like current players? Perhaps a player_opinion or rookie_opinion file for the bar values matched to player_id to separate out what is fact and opinion of your scouts.

[Dutch]

If I were to revive Draft Analyzer, it would want:

- Formation information for QBs
- Birthdates (for potential affinity / conflict reporting)
- Bar min/maxes

in the rookie player CSV. I have to double-check, it would be good for the player id to be in there as well (we could then hook all that up so we had correct rookie combines for everyone, and Ben wouldn't have to rename rookies to avoid duplicate names...)

Formations for active quarterbacks were added.
PlayerID was added to rookies so we can link to birthdates.

[Dutch]

Player_information.csv has (what I assume is) an error where 'chosen_team' defaults to teamid 0 when a team hasn't actually been chosen for that player. (I believe this is only set when a player is inducted to the Hall Of Fame)

[Dutch]

Columns that identify a college, hometown, or state by an integer don't have a relationship to their respective names.

[WheelsVT]

Columns that identify a college, hometown, or state by an integer don't have a relationship to their respective names.

Good one!
+1

Right now the draft utility just gives a number for the school since I have nothing to reference.

[Dutch]

I tried to use the old college name table but the FOF2k7 had ~600 names and FOF7 has ~700 id's...so it doesn't match up.

[Dutch]

The use of a variable in the 'week' column in game_information is frustrating to say the least.

I've built a stage_info table to help ease the pain (as I've mentioned here before) and really wish this could somehow be incorporated into the export data.

For instance, I am trying to show last week's game results. My counter shows that today is "Ex. Season Week 3" and I would like to show the last stage results which is "Ex. Season Week 2".

In my stage_info table, "Ex. Season Week 3" is stage_id 25...and "Ex. Season Week 2" is stage_id 24....so I need a way to join the tables so I can say, (stage_info=stage_info 25 - 1).

I wish that game_information would have the 48 stages of the game identified by integer so I could do this without additional (and slow...) JOIN statements.

[aston217]

I'm not sure if this is the right place or not, but I'd like to throw out ideas as I get them here for the exported data. Please let me know if there is a better avenue to articulate these things.



New Field requests...

team_information.conf_id(INT)
team_information.div_id(INT)
team_information.nickname(VARCHAR)
team_information.owner_name(VARCHAR)

I see this information still isn't there. The bold seems like extremely critical information. If I'm not mistaken, this is nowhere to be found in export data. What are your guys' solution to this?

Are there more data format changes forthcoming, or is this what we're likely stuck with (for better or for worse) for FOF7? Forgive me, I'm out of the loop.

(edit: I suppose you can pull division, as a text string, from 'standings', but this doesn't include conference and SELECT division FROM team_info, standings where team=team is not a very nice solution.)

[Ben E Lou]

team_information.csv is a *completely* different file--with the same file name--after the season rollover. Not sure yet if that's true for the entire offseason, or just this one stage. In the season, it's similar to fof_teams. But the one I just exported (right after the season rollover) closely mirrors fof_franchise.

[Ben E Lou]

team_information.csv is a *completely* different file--with the same file name--after the season rollover. Not sure yet if that's true for the entire offseason, or just this one stage. In the season, it's similar to fof_teams. But the one I just exported (right after the season rollover) closely mirrors fof_franchise.Unable to reproduce this, but I did copy/paste the field headers of the other file in the FOxL Lounge so I have them. The other version is quite similar to fof_franchise from DBUpdater. It spit out the following fields, for the entire league history:

Team Playoff_Performance Average_Attendance Percent_of_Capacity_(of_1000) TV_Contract_(all_money_is_in_tho​usands) Ticket_Revenue Suite_Revenue Salary_Cost Bonuses Concessions Parking Advertising Staff_Cost Maintenance Stadium_Payments Overall_Performance Franchise_Value Profit Season_Tickets_Sold Capacity Top_Quarterback Top_Rusher Top_Receiver Top_Tackler Coach Quarterback_Passing_Yardage Rusher_Yardage Receiver_Yardage Tackles

No idea how it did it. My best guess is that perhaps there are two files being written in the export routine with the same name, causing one to overwrite the other, which would be why we've never seen the fields I pasted above. But maybe I happened to open the first team_information.csv before the routine had finished, thus preventing the second one from overwriting it.

[gstelmack]

Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) - will tell you what file operations happen (notably opens/closes) and could confirm your theory.

[aston217]

Can anyone confirm for me that they're seeing the same thing?

the first transactions file of the league has this structure:

Stage
Year
Player_ID
Transaction
Team
Position_Group
Money
Years/Original_Position
Original_Team/Destination_Position/Misc.

Subsequent ones...


Stage
Year
Player_ID/Staff_ID/Round
Transaction
Team
Position_Group/Year
Money
Years/Original_Position/Destination_City
Original_Team/Destination_Position/Misc.


Or is it just me?...

[Dutch]

No. Schedule results are there. If we could just have the rest of the games--with zeros for results--of the current year included in the one csv, that would be fine (and easier.)

Please, Jim, please!

This is all we can do in the meantime for our schedule pages...

Team Roster (http://www.replicatednfl.com/team_id_schedule.php?team=15)

[Dutch]

I don't believe the QB Formations attribute is exported in the ratings. I'm having to backfill it with 0s for now in Conscriptor.

This still needs to be added.

[Dutch]

Columns that identify a college, hometown, or state by an integer don't have a relationship to their respective names.

Still need this too. PLEASE!

[Dutch]

Oh, and while we are at it, I'm having a lot of beautiful pages looking rather red since we lost the individual bar futures... :(

They will all look like this now...

RNFL (http://www.replicatednfl.com/player_id.php?ID=32329)

Would love to re-add those green bars underneath to get that nice FOF look. I've got all that code commented out and it's ready...just need the data.

[aston217]

{commiseration intensifies}

[gstelmack]

Can anyone confirm for me that they're seeing the same thing?

the first transactions file of the league has this structure:

Subsequent ones...

Or is it just me?...

The first one doesn't have trades or position switches. In 2k7, the format of individual transactions varied widely depending on the actual transaction itself.

[aston217]

Thanks, greg.

in team_statistics.csv, there's a column for "sacks" and one for "sack_yardage". Does anybody happen to know if that's times sacked and sacked yardage? I'm assuming it is, because the sack yardage usually only comes up elsewhere in the CSV when we're talking about how many yards a QB was sacked for.

[Dutch]

Aston,

Assuming I understand your question, the 'Sacks' and 'Sack_yardage' fields are dependent upon the 'unit' field. Each team has two entries, one for offense and one for defense.

So to answer your question it does stand for "How many times your QB's were sacked and how many yards they were sacked for", but only when unit='offense'.

[aston217]

Ohh, you're right. I forgot about the unit field. Thanks!

[NawlinsFan]

It would be beyond sweet if Jim were to incorporate some of the work you guys are doing into the game. It's just a natural extension of the capability he has buried within his code.

[aston217]

Okay, now I'm confused again.

I had convinced myself that 'offense' and 'defense' translated to 'team' and 'opponent', since for the in-game stats, that switched between the two sets of stats for each team.

Take for example, the row where team_id = 3, unit = defense. Let's say this row has the following data:

rush attempts: 400
hurries: 80
kick returns: 60
penalties: 100

(1) 'unit=defense' actually means 'opponents of team id=3', so opponents made 400 rush attempts on Team 3, recorded 80 hurries on Team 3, 60 returns against Team 3, and 100 penalties against Team 3.

(2) 'unit=defense' literally means 'team id=3 defense', so Team 3's defense faced 400 rush attempts (same), but recorded 80 hurries against opponents (opposite). And kick returns would mean....? But especially, penalties would mean, what?

I hope it's not (2). That seems harder to work with. In (1) all of a team's stats are in one row, and all of the opponents' stats are in the other row. In (2) each row, offense and defense, has a mixture of 'team stats' and 'opponent stats'.

[Dutch]

You're confusing me, now. :)

Let's take the New York Giants (NYG) and your data.

Offense - NYG rushed 400 times
Offense - NYG QB's were hurried 80 times
Offense - NYG returned 80 kicks
Offense - NYG had 80 penalties

Defense - NYG had 400 rushes against
Defense - NYG had 80 QB hurries
Defense - NYG had 80 kicks returned against
Defense - NYG had 80 penalties

Not sure if that helps but that's what I would expect it to mean.

[aston217]

Right, so what confused me was whether "unit: offense/defense" literally means offense/defense, or whether "unit: offense/defense" actually means "stats by this team / stats against this team."

Because your explanation makes sense based on the unit names, BUT Firefly just provided me with the CFL's export data and I tracked down the two rows for my team from last season:

year 2034, team GBY, unit offense
18 "sacked", 100 "hurries"

year 2034, team GBY, unit defense
34 "sacked", 66 "hurries"

I know and can look up that Green Bay's defense recorded 100 hurries and 34 sacks. So it seems offense actually means "by the team" and defense means "against the team". (Side note: I really wish it would be 'sacks' instead of 'sacked' now...)

For what it's worth, while we're here, "RB rushes" and "RB rushing yards" apply only to the "offense" unit; 0's are recorded under 'defense.' You know, we should collectively set about documenting this whole darn thing :(

[Dutch]

How do these numbers line up against the Team Statistics in FOF7, does it all match, at least?

[aston217]

Hm? These two rows are from FOF7 export data's team_statistics.csv, if that's what you are asking?

year 2034, team GBY, unit offense
18 "sacked", 100 "hurries"

year 2034, team GBY, unit defense
34 "sacked", 66 "hurries"

I mean, the stats were recorded during a 2k7 season, but the league has converted now.

[Dutch]

Probably a bad question. :)

So if we look in FOF7 at Team_Statistics...

There is a page for "lineman" and a page for "opposing lineman" with identical columns of information for each.

I think it says the same thing though, right? I mean, if I look under the New York Giants and see "Opposing Lineman-->SckA" as "3" then that means the opposing lineman gave up 3 sacks....but the same is true that the NYG's defense got 3 sacks. Either way, they are credited to the NYG team_id.

[Dutch]

For what it's worth, while we're here, "RB rushes" and "RB rushing yards" apply only to the "offense" unit; 0's are recorded under 'defense.' You know, we should collectively set about documenting this whole darn thing :(

That one is by design, I believe, it's a cool stat, but I believe it's meant for the Adjusted Line Yards and not really "team statistics". That stat only worries about an offense's RB's (exclusively) and there is no need to track the defense's RB ave. so long as the intent is to re-create the Football Outsiders list.

[aston217]

Yes, that's right. But you're talking about the in-game menu here, not the CSV file, right?

What I'm saying is, in the CSV file, you'll have a row where Team=NYG, unit=OFFENSE, and *that* row is going to tell you how many hurries NYG's defense recorded. Which is not what the column name "hurries" makes it sound like.

Though for sacks, it will tell you how many sacks NYG's offense allowed, because that column is called "sacked."

[aston217]

Basically, as best as I can tell,

unit:offense means this row contains a set of stats recorded by TEAM_ID.
unit:defense means this row contains a set of stats recorded by OPPONENTS OF TEAM_ID.

In other words, the whole 'unit' thing is a bit of a misnomer.

[Dutch]

Fair enough, I get what you are saying. I think that was just a way to get all the data into one table.

But I agree, it's a bit confusing. I think the confusion lessens when we realize that it's really just making the tables work for a bunch of data in-game that's already set up to be viewed a certain way. If that makes sense.

[Ben E Lou]

Unable to reproduce this, but I did copy/paste the field headers of the other file in the FOxL Lounge so I have them. The other version is quite similar to fof_franchise from DBUpdater. It spit out the following fields, for the entire league history:

Team Playoff_Performance Average_Attendance Percent_of_Capacity_(of_1000) TV_Contract_(all_money_is_in_tho​usands) Ticket_Revenue Suite_Revenue Salary_Cost Bonuses Concessions Parking Advertising Staff_Cost Maintenance Stadium_Payments Overall_Performance Franchise_Value Profit Season_Tickets_Sold Capacity Top_Quarterback Top_Rusher Top_Receiver Top_Tackler Coach Quarterback_Passing_Yardage Rusher_Yardage Receiver_Yardage Tackles

No idea how it did it. My best guess is that perhaps there are two files being written in the export routine with the same name, causing one to overwrite the other, which would be why we've never seen the fields I pasted above. But maybe I happened to open the first team_information.csv before the routine had finished, thus preventing the second one from overwriting it.This export was added (or perhaps the file and changed so no overwriting) in 7.0b

[Dutch]

Glad that one got sorted out. Mystery solved!

[Dutch]

The private players_personal.csv contains all the fields that I wanted for the player_ratings.csv. (FUT ratings to go along with CUR ratings)

So while that's good stuff, I have to admit I was hoping Jim could figure out a way to give us CUR and FUT ratings for our web-sites. And to know the only way a web-administrator can show the pages correctly is by putting ourselves at a competitive disadvantage is somewhat discouraging.

[aston217]

I suppose what you could do is create logins for all users and allow them to upload their private ratings for use in the website. That sounds kinda exciting, actually!

[Dutch]

Very true. It would take me a while to learn how to do that but I think it's all within my grasp at this stage.

I'll have to add those to my two over-flowing lists I keep called "Things I need to do" and "Things I need to learn in order to do the things I need to do..." :)

[Ben E Lou]

Well, given that scouting is much more inexact from scout to scout, I'm handling by simply using the league scout and running a simple linear function to estimate the "current" of each bar based on the ratio of the current overall to the future overall. If a player's current and future overall ratings are equal, then I just use full red. If they're not, I just use the cur/fut ratio, modify it based on the number of static bars for the position, and then apply that to the league scout's future rating to come up with a pretty good estimate of the current. It's not perfect, but it's certainly close enough to give the information people need from the web site. I don't think anyone needs to know from the league site if their rookie WR is a 24 or a 32 in RR right now.

[Dutch]

Ooooh, I like that CUR/FUT ratio idea, Ben, now that you mention the global scout. That's a solid workaround. I considered something like that briefly, but I was immediately turned off by a lack of accuracy such a method would display...but I didn't take into consideration that the global scout is not an exact science to begin with. You're right, in a quick review...24 instead of 32...who cares?

[gstelmack]

For rookies.csv, it outputs the Adjusted Grade, but not the Base Grade before position weighting was applied (for those who prefer different weights).

[Dutch]

Added to the first post to keep the (small) list of requests consolidated.

[garion333]

I suppose what you could do is create logins for all users and allow them to upload their private ratings for use in the website. That sounds kinda exciting, actually!

God forbid you keep playing or something.

[gstelmack]

Is the Chemistry info ("Fits In", etc) available for rookies anywhere? Maybe it could go in draft_personal?

[Dutch]

I haven't seen the draft_personal file yet, but that's the place it would fit best. No pun intended. :)

[Ben E Lou]

draft_personal fields...


Player_ID
Interviewed
Low_Screen_Passes
Low_Short_Passes
Low_Medium_Passes
Low_Long_Passes
Low_Deep_Passes
Low_Third_Down
Low_Run_Frequency
Low_Future_1
Low_Accuracy
Low_Timing
Low_Sense_Rush
Low_Read_Defense
Low_Two-Minute_Offense
Low_Future_2
Low_Future_3
Low_Future_4
Low_Future_5
Low_Future_6
Low_Speed
Low_Power_Inside
Low_Third-Down_Runs
Low_Hole_Recognition
Low_Elusiveness
Low_Speed_Outside
Low_Blitz_Pickup
Low_Avoid_Drops
Low_Get_Downfield
Low_Route_Running
Low_Third-Down_Receiving
Low_Big_Play_Receiving
Low_Courage
Low_Adjust_to_Ball
Low_Punt_Returns
Low_Kick_Returns
Low_Future_7
Low_Run_Blocking
Low_Pass_Blocking
Low_Blocking_Strength
Low_Punting_Power
Low_Hang_Time
Low_Directional_Punting
Low_Kickoff_Distance
Low_Kickoff_Hang_Time
Low_Kicking_Accuracy
Low_Kicking_Power
Low_Run_Defense
Low_Pass_Rush_Technique
Low_Man-to-Man_Defense
Low_Zone_Defense
Low_Bump-and-Run_Defense
Low_Pass_Rush_Strength
Low_Play_Diagnosis
Low_Punishing_Hitter
Low_Intercepting
Low_Endurance
Low_Special_Teams
Low_Long_Snapping
Low_Kick_Holding
High_Screen_Passes
High_Short_Passes
High_Medium_Passes
High_Long_Passes
High_Deep_Passes
High_Third_Down
High_Run_Frequency
High_Future_1
High_Accuracy
High_Timing
High_Sense_Rush
High_Read_Defense
High_Two-Minute_Offense
High_Future_2
High_Future_3
High_Future_4
High_Future_5
High_Future_6
High_Speed
High_Power_Inside
High_Third-Down_Runs
High_Hole_Recognition
High_Elusiveness
High_Speed_Outside
High_Blitz_Pickup
High_Avoid_Drops
High_Get_Downfield
High_Route_Running
High_Third-Down_Receiving
High_Big_Play_Receiving
High_Courage
High_Adjust_to_Ball
High_Punt_Returns
High_Kick_Returns
High_Future_7
High_Run_Blocking
High_Pass_Blocking
High_Blocking_Strength
High_Punting_Power
High_Hang_Time
High_Directional_Punting
High_Kickoff_Distance
High_Kickoff_Hang_Time
High_Kicking_Accuracy
High_Kicking_Power
High_Run_Defense
High_Pass_Rush_Technique
High_Man-to-Man_Defense
High_Zone_Defense
High_Bump-and-Run_Defense
High_Pass_Rush_Strength
High_Play_Diagnosis
High_Punishing_Hitter
High_Intercepting
High_Endurance
High_Special_Teams
High_Long_Snapping
High_Kick_Holding

[aston217]

What exactly is the active_free_agency table?

[Dutch]

It shows all the free agents that have bids on them (and the overall bids) during the free agency periods.

[gstelmack]

- College_id, hometown_id, and state_id information cannot be mapped to a name because name tables don’t exist

I believe this data is available.

C:\Program Files (x86)\Solecismic Software\Front Office Football Seven\datafile

colleges.txt
city.txt

States are just alphabetical, but I can pull them from the binary if you really need it.

[Dutch]

I believe this data is available.

C:\Program Files (x86)\Solecismic Software\Front Office Football Seven\datafile

colleges.txt
city.txt

States are just alphabetical, but I can pull them from the binary if you really need it.

Cool...hadnt thought of that. I can add that to a table with an ID and that should be perfect. Thanks greg.

[Ben E Lou]

I've just been using fof_colleges. Have there been new ones added or something?

[Ben E Lou]

Ah, I see. At a quick glance, looks like colleges.txt has 41 new ones appended at the end with this version:

691 - Florida Atlantic
692 - Georgia State
693 - UNC - Charlotte
694 - Florida Tech
695 - Berry College
696 - Alderson Broaddus
697 - Hendrix College
698 - Houston Baptist
699 - Mercer
700 - Oklahoma Baptist
701 - Reinhardt
702 - Southwestern
703 - Stetson
704 - Warner
705 - California - Irvine
706 - Incarnate Word
707 - Old Dominion
708 - Texas - San Antonio
709 - Campbell
710 - Stillman
711 - Charleston (WV)
712 - St. Paul's
713 - Shaw
714 - Lamar
715 - South Alabama
716 - Becker
717 - Pacific
718 - Concordia (Ala.)
719 - Ave Maria
720 - Robert Morris
721 - Siena Heights
722 - Stevenson
723 - Concordia (Mich.)
724 - George Fox
725 - Misericordia
726 - Finlandia
727 - Kennesaw State
728 - New Orleans
729 - Castleton State
730 - New Haven
731 - Canada

From spot checking a few at various points in the list, it looks like 1 through 690 are identical to FOF2K7. I guess I should add those last ones (though it's pretty much useless data anyway...)

[gstelmack]

Injuries used to be part of the transaction list in FOF2k7 - is there any other place to find injuries in the exported data?

Can we get the current season added to the universe_info table?

[Dutch]

Injuries used to be part of the transaction list in FOF2k7 - is there any other place to find injuries in the exported data?

Under player_record there is injury_length, health, and injury_type.

Can we get the current season added to the universe_info table?

I just built a table called Current_Game and added one field called cur_year and update that manually.

[gstelmack]

Under player_record there is injury_length, health, and injury_type.

That gives the current injury status, but does not give you an injury history.

[gstelmack]

I just built a table called Current_Game and added one field called cur_year and update that manually.

And for this part, I'm looking at this info for a utility, so I don't want to have to make the user enter it manually if I can avoid it.

[Dutch]

That gives the current injury status, but does not give you an injury history.

Yeah, I'm not sure about that then, I don't think the history exists...at least not in the transactions, player_ratings or player_season files which seem the logical place for it.

And for this part, I'm looking at this info for a utility, so I don't want to have to make the user enter it manually if I can avoid it.

I'm always thinking of myself and web-page support! But it definitely looks like a couple of considerations like this one would work for us all.

[Dutch]

I would love to have the player_ratings CSV populated and distributed from Stage 1 of a season. I think it's stage 28 of the 48 stage season and it still hasn't shown up. Really messes up my web pages.

I know...I know...."fix my web pages"...

[aston217]

When *do* the player_ratings CSV show up?

Do we have an idea of which CSVs get updated for which stage?

[Ben E Lou]

Ratings are updated in the csv at the same times they update in the game, it appears: at TC and after PreWk2.

[Dutch]

Updated list of stage names. (last time I posted, I was counting 48...)

stage_id stage_name
1 Pre-Staff Draft
2 Staff Draft
3 Pre-Free Agency
4 FA Stage 1
5 FA Stage 2
6 FA Stage 3
7 FA Stage 4
8 FA Stage 5
9 FA Stage 6
10 FA Stage 7
11 FA Stage 8
12 FA Stage 9
13 FA Stage 10
14 FA Stage 11
15 FA Stage 12
16 Amateur Draft
17 Pre-Late FA Period
18 Late FA Stage 1
19 Late FA Stage 2
20 Late FA Stage 3
21 Late FA Stage 4
22 Late FA Stage 5
23 Pre-Training Camp
24 Ex. Season Week 1
25 Ex. Season Week 2
26 Ex. Season Week 3
27 Ex. Season Week 4
28 Ex. Season Week 5
29 Reg. Season Week 1
30 Reg. Season Week 2
31 Reg. Season Week 3
32 Reg. Season Week 4
33 Reg. Season Week 5
34 Reg. Season Week 6
35 Reg. Season Week 7
36 Reg. Season Week 8
37 Reg. Season Week 9
38 Reg. Season Week 10
39 Reg. Season Week 11
40 Reg. Season Week 12
41 Reg. Season Week 13
42 Reg. Season Week 14
43 Reg. Season Week 15
44 Reg. Season Week 16
45 Reg. Season Week 17
46 Wild Card Round
47 Divisional Round
48 Conference Round
49 Front Office Bowl
50 End of Season