your league uses the real-life as-played schedule,
you are using a Season Disk for which we have compiled a complete list of real-life transactions or you have compiled your own list of real-life transactions, and
you have made no changes to the team rosters.

If you do choose to use the real-life lineups, you'll also need to use the real-life transactions to ensure that the right players are on the active roster for each game.

You have these options:

If you choose Do not use transactions and lineups, DMB will not change the status of players on the roster as you move through the season. You can make your own roster moves if you like. And if you autoplay games or play games interactively with the computer manager handling one or both teams, the computer manager will choose starting lineups based on the manager profile settings for the teams involved.
If you choose Use real-life transactions, DMB will apply the real-life roster moves (trades, promotions, demotions, disabled list moves, and so on) on the days they happened in real life, but it will not use the real-life lineups. If you autoplay games or play games interactively with the computer manager handling one or both teams, the computer manager will choose starting lineups based on the manager profile settings for the teams involved.
Finally, if you choose Use real-life transactions and lineups, DMB will apply the real-life roster moves and use the same starting lineups for each game as were used in real life.

The real-life transactions and saved lineups are intended for people who enjoy replaying real-life seasons in detail. If you are drafting new rosters or making any other changes to the rosters, the real-life transaction file and the game-by-game lineups won't be in synch with your rosters, so you must choose Do not use transactions and lineups to avoid seeing warnings and error messages.

WARNING! If you use real-life transactions and lineups, you MUST play scheduled games in chronological order. If you play them out of order, the transaction stream will get out of synch. You do not even have to play any part of the game for this problem to arise.

Example: If the first unplayed game is scheduled for 4/7, but you start up a game on 4/10 in order to see what pitcher is scheduled to start in a few days, the game will apply all transactions up through the later date even if you didn't play any part of that game. When you then try to play the game on 4/7, the transaction stream is out of synch and you may receive error messages and/or have to restart your season depending on the severity of the problem.

DMB enables you to create real-life transactions using the View>Transactions command. You can save game-by-game lineups as you progress through a season replay, so they will available for you (and others) who wish to replay that season again.

Saving opening day rosters

In addition to creating a complete set of real-life transactions for a season, you will also need to save the opening day rosters for all teams in your league. This provides a starting point for the application of the transactions that follow.

After you finish playing out a season, you can use the restart a season command from the Tools menu to to reset all statistics, fatigue, and injury information, and to restore your rosters to their opening-day status. If you have not previously saved your opening day rosters, the active/reserve/disabled status of some players might be inconsistent with real-life and with the transactions in the log.

To save the opening day rosters, choose View>Roster / manager profile to display the roster window. Click on the Pre-season radio button on the tool bar in the roster window to indicate that you want to work with the opening day status codes. Then use the menu commands to activate all players who began the season on the active roster. Farm anyone who was not either active or disabled on opening day. Disable anyone that began the season on the DL. When all of these moves have been made, click on the Current radio button to indicate that you are finished working with the pre-season roster status codes. Then right-click on the roster and select Copy status codes > From pre-season to current from the popup menu.

This is a good place to remind you that DMB season disks may have the same player on more than one roster if that player was traded, released, or claimed on waivers during the year. When the game processes one of these transactions, it does not physically move the player from one team to another, because that player already has a record with his stats and ratings for that other team. Instead, it activates the player on the team he's joining and deactivates him on the team he's leaving. So, when you're setting up your opening day rosters, and you have a player who wasn't really on the team on opening day, leave him on the roster but farm him. DO NOT remove him from the roster.

Creating real-life transactions

After you have saved your opening day rosters, you're ready to start creating real-life transactions using the View>Transactions command. You can enter the transactions in any order.

See Transactions for guidance on how to create and modify real-life transactions.

Saving game-by-game lineups

If saved lineups do not already exist for a season disk you wish to use for a detailed replay, you can still enter the lineups from each game using published boxscores.

To do this, choose Game>Scheduled to open the scheduled game window, then double-click on the game in question to begin playing the game. Make sure the manager options are set to Human for starting lineup selection.

When DMB displays the window used to select starting pitchers and lineups, make your selections (both pitchers first, then both lineups). As you finish with each lineup, click on the Other actions button, then select Save this lineup>To real-life lineup log from the popup menu.

You don't need to go ahead and play the game right away. You can quit this game and play it later using the lineups that you just saved.

Converted from CHM to HTML with chm2web Standard 2.85 (unicode)