Primary Fielding Positions

[Nukester]

Will the AI start a player at a certain position (full time not just a few times) if that position is not the primary one listed? Ive noticed in my imports of 1903 that Willie Keeler has his primary position set to 3B even though he only played 4 games at 3B and 128 games in the OF. Also Dave Fultz has his primary position set to 3B even though he only played 2 games at 3B and 77 in the OF. I stopped looking at players after seeing those two. I even tried exporting the fielding table, sorted by playerid, yearid, and G descending (games played at that position), which put the position with the most games played at the top, but they still imported the same way. It almost seems like it is setting the position with the least amount of games played as the primary position. I dont really mind IF the CPU will play these guys at their other positions.

[Wrathchild]

I think that it will if there is no one else to play that position, though I think it will pick someone with that primary position over someone with it as a secondary position.

[Nukester]

I just imported 1927 and looked at Lloyd Waner. He played 1 game at 2B and 150 in the OF, but he imported as as a 2B.

[Nukester]

Also in 1927 Paul Waner imported as a 1B. He played 14 games at 1B and 143 in the OF. Something is not right

[Nukester]

I just noticed this thread : tm.asp?m=2152092&mpage=1&key=primary&#2152092

Im running 1.76 but it might not be the latest 1.76 patch. Ill download that patch and try again

[Wrathchild]

Is it just based on the field sequence in the database? Maybe it just sets their first position as primary. 

[Nukester]

I installed the 1.76B patch and created a league with the default database (which overwrote my modified database) and the positions look good now. Keeler imported as RF and Fultz imported as a CF. Im reprocessing my modifed database now and am going to create a league using that DB to see if everything is still ok.

[Nukester]

Yup installing 1.76B did the trick