OOTP Developments Forums - View Single Post - Using actual lineups from 2013 not completely accurate

M's rule · 12-05-2020, 04:06 PM

Here's the guru.

First, thanks to pstrickert for bringing this to my attention.

There are three things going on here.

Puig is on the roster at the start of the season because the game doesn’t take a player’s debut date into account. Under normal circumstances, a rookie will be available to his team all season, regardless of when his first game was. For the vast majority of rookies, this issue doesn’t drastically affect how much or how often they get used in their first seasons. But in the case of a highly talented rookie like Puig, it leads to an accuracy problem because the AI will use him as a pinch hitter or late-inning replacement as often as it can, even (and especially) before he actually played in a game.

The way to prevent this is to insert a couple of lines in the transactions file so that Puig becomes inactive on 3/31 (Opening Day) and is activated on 6/3. I have done that in the master file, but unfortunately the file isn’t due to be updated in the game again until next year.

orbops, you can accomplish the same thing by editing Puig to take him off the active roster and then bringing him back to active status on June 3.

Fife doesn’t move off the reserve roster because of a bug that occurs with a human-controlled team in a league that uses real lineups and real transactions. If you take control of a team, the AI leaves you essentially responsible for manipulating your roster. A player who starts the season on the reserve roster might remain there all season unless you manually add him to the active roster on or before his actual first appearance. When a player moves off your active roster (from a trade or a release), the AI won’t necessarily bring up a player from the reserve roster to fill that spot.

For comparison, I started a league in 2013 in commissioner mode but did not control a team. In this situation, the AI did move Fife to the active roster for his start on 4/21.

Wall does not join the active roster in mid-April, as he did in real life, because (as pstrickert indicated) the transactions file doesn’t include promotions and demotions. In a league where the team is AI-controlled, his time on the active roster (if any) will be dictated by circumstances. (I just ran through a 2013 league In a league where the team is human-controlled, you’re free to bring him up only for the time of his actual stint, or at any other time you see fit.

Bottom line: Taking control of a team in a real lineups/real transactions league is a high-maintenance responsibility. To be sure that your team has all the active players it should have on any day, you’ll need to visit the Rosters & Transactions screen before every day’s game and move someone off the reserve roster if necessary.

12-05-2020, 04:06 PM	#7
M's rule All Star Reserve Join Date: Jul 2003 Location: Seattle Posts: 925	Here's the guru. First, thanks to pstrickert for bringing this to my attention. There are three things going on here. Puig is on the roster at the start of the season because the game doesn’t take a player’s debut date into account. Under normal circumstances, a rookie will be available to his team all season, regardless of when his first game was. For the vast majority of rookies, this issue doesn’t drastically affect how much or how often they get used in their first seasons. But in the case of a highly talented rookie like Puig, it leads to an accuracy problem because the AI will use him as a pinch hitter or late-inning replacement as often as it can, even (and especially) before he actually played in a game. The way to prevent this is to insert a couple of lines in the transactions file so that Puig becomes inactive on 3/31 (Opening Day) and is activated on 6/3. I have done that in the master file, but unfortunately the file isn’t due to be updated in the game again until next year. orbops, you can accomplish the same thing by editing Puig to take him off the active roster and then bringing him back to active status on June 3. Fife doesn’t move off the reserve roster because of a bug that occurs with a human-controlled team in a league that uses real lineups and real transactions. If you take control of a team, the AI leaves you essentially responsible for manipulating your roster. A player who starts the season on the reserve roster might remain there all season unless you manually add him to the active roster on or before his actual first appearance. When a player moves off your active roster (from a trade or a release), the AI won’t necessarily bring up a player from the reserve roster to fill that spot. For comparison, I started a league in 2013 in commissioner mode but did not control a team. In this situation, the AI did move Fife to the active roster for his start on 4/21. Wall does not join the active roster in mid-April, as he did in real life, because (as pstrickert indicated) the transactions file doesn’t include promotions and demotions. In a league where the team is AI-controlled, his time on the active roster (if any) will be dictated by circumstances. (I just ran through a 2013 league In a league where the team is human-controlled, you’re free to bring him up only for the time of his actual stint, or at any other time you see fit. Bottom line: Taking control of a team in a real lineups/real transactions league is a high-maintenance responsibility. To be sure that your team has all the active players it should have on any day, you’ll need to visit the Rosters & Transactions screen before every day’s game and move someone off the reserve roster if necessary.