OOTP Wiki - User contributions [en]

OOTP Baseball:Important Game Concepts/Tools, Functions, and Editors/In-Game Editors/League Structure Editor

2025-03-18T21:40:07Z

JudgeGio: Below "Editing the League Structure", four levels are listed, so I changed "you can edit at three different levels" to "you can edit at four different levels".

{{DISPLAYTITLE:{{SUBPAGENAME}}}}The '''League Structure Editor''' can be used to change the core structure of a league, such as the number of subleagues, the number of divisions, the number of teams, or which teams go where. The League Structure Editor is accessed via the League Functions page, either by selecting '''Edit League Structure''' from the Functions action menu, or by selecting the same from the scrolling list on that page.

You must either be playing a solo game, or be the Commissioner of your league, in order to use the League Structure Editor. League structures can only be edited during the offseason or preseason.

''Warning: Editing your league structure is a drastic step! Always, always, always be sure to back up your game before editing the league structure!''

===== Editing the League Structure =====
To edit any league, first select the target league from the '''Select League''' drop-down in the top right corner. In editing your league structure, you can edit at four different levels:

# [[OOTP Baseball:Important Game Concepts/Tools, Functions, and Editors/In-Game Editors/League Structure Editor#Editing Subleagues|Editing Subleagues]]
# [[OOTP Baseball:Important Game Concepts/Tools, Functions, and Editors/In-Game Editors/League Structure Editor#Editing Divisions|Editing Divisions]]
# [[OOTP Baseball:Important Game Concepts/Tools, Functions, and Editors/In-Game Editors/League Structure Editor#Editing Teams|Editing Teams]]
# [[OOTP Baseball:Important Game Concepts/Tools, Functions, and Editors/In-Game Editors/League Structure Editor#Importing Historical Teams|Importing Historical Teams]]

===== Generating Schedules =====
Any time you edit the structure of your league, you typically should generate a new schedule that takes into account the changes you have made. If you fail to do so, it could result in new teams not having any scheduled games, etc. So, unless you are an OOTP schedule guru, and are really confident you know what you are doing, the best idea is to always regenerate a schedule after editing the league. This can be done by clicking on the '''Generate Schedule''' button on this page.

===== Editing Subleagues =====
Since OOTP only allows 1 or 2 subleagues, there aren't that many options for editing subleagues. If you have only one subleague, there will be an option to add a second one.
If you add a new subleague, one division will be created for that subleague automatically. Of course, you must add teams before completing your changes! The name of your subleague can be edited after your changes are done by navigating to '''OOTP Menu | Game Setup | League Setup tab | Names & Affiliations tab'''.

Any time two subleagues exist, there will be an option to delete either of the existing subleagues.
Deleting a subleague will remove the entire subleague, and all divisions and teams in that subleague!

===== Editing Divisions =====
Divisions can be edited in a similar fashion to subleagues, except that you can have many more divisions. Divisions are added to a subleague by clicking the '''Add Division''' button on the same line as the subleague to which you wish to add the division. As long as there are at least 2 divisions in a subleague, each division will have a '''Delete Division option as well.'''

Once you have added a division, you can edit the name of the division in-line just by clicking on the name of the Division. Don't forget to hit Enter when you are done to save your changes!

===== Editing Teams =====
Within a division, you can add, remove, and move teams.

* To add a team, just click the '''Add Team''' button in the same row as the division to which you wish to add the team.
* To remove a team, just click the '''Remove Team''' button next to the teamin the same row as the division to which you wish to add the team. Removing a team deletes the team, and releases all of its players into the free agent pool. It does not delete any affiliated teams. These simply lose their affiliations.
* To move a team, select a destination for the team from the '''Move Team''' drop-down.Once you have added a team, you can edit the team information in-line just by clicking on the appropriate fields and typing. Don't forget to hit Enter when you are done to save your changes!

===== Importing Historical Teams =====
You can also use this screen to import an entire historical team, such as the 1967 Red Sox. To do this, just click the '''Import Hist. Team''' button in the same row as the division you wish to hold the imported team. You will be prompted to find the historical database you wish to use. The default database is in '''data/stats/historical_database.odb''' within your OOTP installation. You will then be presented with historical import options including a list of teams.

If you change the Season Year value, you must hit '''Refresh Teams List''' to get the set of teams from that year. Otherwise, the options on this screen are the same as those described in the Adding Historical Leagues page. When you are done tweaking settings, click on the '''Import Team''' button to proceed.

OOTP Baseball:Customizing OOTP/Schedules/How Schedules Work

2024-11-26T21:33:48Z

JudgeGio: Wiki blank, so I copied and pasted the "How Schedules Work" text from the OOTP24 manual. I made one correction; OOTP checks for schedules in the schedules sub-folder of the data folder, so the data\schedules directory, not the dataschedules directory.

{{DISPLAYTITLE:{{SUBPAGENAME}}}}'''How Schedules Work'''

Scheduling a baseball season is actually a pretty complicated affair. Read on for some more information on how schedules work in OOTP.

'''How does OOTP Assign Schedules?'''

When you create a league, OOTP checks in the '''data\schedules''' directory within your OOTP installation for a schedule that precisely matches the six league settings defined above. If a matching schedule is found, that schedule will be used.

===== How do Schedules Work from Season to Season? =====
If only one schedule matching the league configuration exists, then in subsequent seasons the same schedule will be used, but the precise team matchups will be randomized. In other words, the pattern of games will be identical, but the matchups will be different from season to season. If more than one schedule matching the league configuration exists, then OOTP will cycle through the schedules. This is described a little more in the next section.

===== Linking / Cycling through Multiple Matching Schedules =====
If OOTP finds more than one matching schedule for a given league configuration, it can "link" those schedules and use them across multiple seasons, allowing the user precise control over their schedule year-to-year. When multiple valid schedules exist, OOTP chooses a schedule by reading the values contained in the "comment block" of the schedule file name in alphabetical order. For example, let's say you have created 3 schedules that all match a league you have created. The league has 162 games, interleague play, an unbalanced schedule, and 2 subleagues with 1 division and 8 teams each. You have named your three schedule files as follows:
ILY_BGN_G162_SL1_D1_T8_SL2_D1_T8_c_a.ldsl
ILY_BGN_G162_SL1_D1_T8_SL2_D1_T8_c_b.ldsl
ILY_BGN_G162_SL1_D1_T8_SL2_D1_T8_c_c.ldsl
OOTP will recognize that all three of these files match the league structure, and in Season 1, it will pick the matching schedule with the highest alphabetical value in the comment block - in this case, the first file, because the comment block is "a". In Season 2, it will remember that it already used "a" last season, and will use the file ending in "b". In Season 3, it will use the file ending in "c". Then, in Season 4, it will cycle back to "a" again, and the cycle repeats.
''Note: If you want to make sure that your league uses ONLY these files, it's probably better to use the Saved Game naming convention, so that you don't mistakenly pick up some other schedule files that match your league!''

===== When are Schedules Loaded or Created? =====
Schedules for the first season of a saved game are created upon the creation of the league. Schedules for each new season are created on the first day of the preseason.

===== When can Schedules be Loaded? =====
Day to day schedules can be edited at any time within the in-game Schedule Editor. However, loading a new schedule file can only be done during the offseason or preseason.

===== Schedules and Spring Training/Postseason =====
OOTP schedules generally only have the regular season specifically defined. Even if that is the case, OOTP will automatically handle spring training and postseason scheduling. However, if you wish, you can also build spring training and a postseason schedule into your custom schedule file.

===== OOTP Schedule Generator =====
If you happen to create a league for which no matching schedule file can be found, OOTP actually has a schedule generation engine that will create a schedule for you. However, the schedule generator can only generate balanced schedules, without interleague play. It is theoretically possible that you could devise a league for which OOTP is unable to provide a schedule. In this case, you would have the option of designing your own schedule, or modifying your league structure to match an existing schedule. However, in the four years since we released the scheduling engine, we have not heard any reports of this problem!

===== Schedule Substitution =====
Some schedules can be used for leagues that aren't an exact match for the league description. Any time a league uses a balanced schedule, it can use any schedule that is also balanced, and has the same overall number of teams. So, for example, a league with 10 teams and a balanced schedule could use either of the following leagues:
BGY_ILN_G120_S1_D1_T3_D2_T4_D3_T3
BGY_ILN_G120_S1_D1_T5_D2_T5
The same process can be used for leagues with multiple subleagues, as long as there are no interleague games. You would just use one schedule for each subleague, and schedule them separately..

OOTP Baseball:Customizing OOTP/Schedules/Schedule File Layout

2024-11-21T17:39:50Z

JudgeGio: Since the Wiki of Schedule File Layout was blank, I merely copied and pasted the contents of this page that was in the OOTP24 manual. Since this is my first time working on this Wiki, I hope copying and pasting from past manuals is allowed.

{{DISPLAYTITLE:{{SUBPAGENAME}}}}Alright, now that you've learned a bit about how schedules work, and the file naming conventions, what about the contents of the schedule file itself? Let's go over the layout of a schedule file. OOTP schedule files are XML files, which are simple text files using a special markup language with "tags" similar to those found in HTML. XML files can be opened in any text editor. Here is a sample of the contents of an OOTP schedule file with most of the contents removed:

<?xml version="1.0" encoding="ISO-8859-1"?>

<SCHEDULE type="ILY_BGN_G162_SL1_D1_T5_D2_T5_D3_T4_SL2_D1_T5 _D2_T6_D3_T5_C_" inter_league="1" balanced_games="0" games_per_team="162">

<GAMES>

<GAME day="1" time="1905" away="1" home="8" />

<GAME day="1" time="1905" away="2" home="12" />

<GAME day="1" time="1905" away="3" home="18" />

<GAME day="1" time="1905" away="4" home="13" />

<GAME day="1" time="1905" away="5" home="7" />

(...)

<GAME day="176" time="1305" away="8" home="9" type="0" />

<GAME day="177" time="1305" away="8" home="9" />

<GAME day="178" time="1305" away="8" home="9" />

</GAMES>

</SCHEDULE>

The file is broken up into several components, described below.

===== Declaration =====
The first line of the file (<?xml version="1.0" encoding="ISO-8859-1"?>) is called the '''declaration'''. It defines the XML version (1.0) and the encoding used. In the case of OOTP's schedule files, this should always be exactly as shown above. There is no need to adjust this line.

===== Schedule Element =====
The second line in a schedule file is the '''Schedule Element'''. (Also known as the "root element" in XML terminology.) Here is an example of a Schedule Element line:

<SCHEDULE type="ILY_BGN_G162_SL1_D1_T5_D2_T5_D3_T4_SL2_D1_T5_D2_T6_D3_T5_C_" inter_league="1" balanced_games="0" games_per_team="162">
The Schedule Element has four required attributes, and four optional attributes, as follows:

* '''type''' - Defines the type of schedule, following the code naming convention. The one difference here is that in the "type" attribute, no comment is required as is required in a schedule file name. The type attribute is required.
* '''inter_league''' - Set to "1" if there is interleague play, "0" if not. The inter_league attribute is required.
* '''balanced_games''' - Set to "1" if the schedule is balanced, "0" if not. The balanced_games attribute is required.
* '''games_per_team''' - The number of games per team in the regular season. The games_per_team attribute is required.
* '''start_month''' - The numeric month in which the schedule should begin. Use "1" for January, "2" for February, etc. The start_month attribute is optional. This value can also be set on the Options page.
* '''start_day''' - The day of the month in which the schedule should begin. Use "1" for the 1st of the month, etc. The start_day attribute is optional. (See also the start_day_of_week attribute below.) This value can also be set on the Options page.
* '''start_day_of_week''' - The day of the week in which the schedule should begin. (1=Sun, 2=Mon, 3=Tue, 4=Wed, 5=Thu, 6=Fri, 7=Sat) Use "1" for the 1st of the month, etc. When this attribute is used, the game will start the schedule on the first occurrence of that day of the week on or after the defined start_month and start_day for the current game year. For example, if start_month="4", start_day="1", and start_day_of_week="6", the schedule will start on the first Friday on or after April 1st. The start_day attribute is optional. This value can also be set on the Options page.
* '''allstar_game_day''' - The day from the beginning of the schedule when the All-Star Game will be scheduled. For example, if allstar_game_day="100", the All-Star Game will be held on the 100th day of the schedule, where day 1 is the start_month, start_day, and start_day_of_week as described above. The allstar_game_day attribute is optional.The '''inter_league''', '''balanced_games''', and '''games_per_team''' attributes in the Schedule Element must match the same settings in the league setup within the game, or the schedule will not work. These are defined at the creation of a league on the Options page, or during a later offseason or preseason by going to '''OOTP Menu | Game Setup | League Setup | Options'''. Changes to these settings do not take effect immediately. They only take effect upon the next time you load a schedule, or OOTP attempts to create a new schedule.

''Note: Attribute values must always appear in quotes (" ").''

===== "Auto-Adjust Date if Matching XML Schedule Found" =====
The Options page has an option called "Auto adjust date if matching XML schedule found." If this is enabled, then the settings in the OOTP schedule file will ''override'' any values that were entered in the Options page. If this is not selected, then the values from the Options page will take precedence over those in the schedule file.

===== About All-Star Games =====
If no All-Star Game is defined in the schedule file, and the options to "Hold All-Star Game" and "Automatically Schedule All-Star Game" on the Options page are enabled, then OOTP will pick a point around the middle of the schedule and insert a 3-day break with the All-Star Game in the middle of it. If you have constructed your own schedule file, take care with the "Automatically Schedule All-Star Game" option, because using this delays the start of the second half of the season by three days. This can result in your key weekend series being played instead on a Mon-Tues-Weds.

===== Games Element =====
The bulk of the remainder of a schedule file are individual '''Game Elements''', each of which defines a single game. (These are known as "child elements" in XML terminology.) First comes a container element that looks like this:

<GAMES>
This is immediately followed by one individual Game Element for every game in the entire schedule. Here is an example of a Game Element:
<GAME day="1" time="1905" away="5" home="1" />
The Game Element has four required attributes, as follows:

* '''day''' - The number of the day of the game beginning at 1 with the start date set in the Schedule Element or within the Options page. If day="1", this game would be on the first day of the schedule (Opening Day). The day attribute is required.
* '''time''' - The start time of the game in military time. For example, time="1905" would be a 7:05 pm start time. The time attribute is required.
* '''away''' - The team ID of the visiting team. For example, away="1" would mean team # 1 is the away team. The away attribute is required.
* '''home''' - The team ID of the home team. For example, home="1" would mean team # 1 is the home team. The home attribute is required.
* '''type''' - The type of game. (0=Regular Season, 1=Exhibition, 2=Spring Training, 3=Playoffs, 4=All-Star Game) For example, type="0" would mean a regular season game. The type attribute is optional, and if it is not included, the game is assumed to be a regular season game.
''Note: The ID numbers as set in the schedule apply only to the schedule file, and do not necessarily match up with any specific team identifiers within your OOTP league. The ID numbers for the schedule file should range from 1 to the number of teams in the league. When a schedule is applied to a specific OOTP league, the teams in the league are assigned IDs in alphabetical order by team (city) name within each division, going through divisions from top to bottom, starting in and going through subleague 1, then going through subleague 2 in the same manner. This process is completely invisible to the user.''

===== Syntax Notes =====
XML is particular about formatting. Be sure to follow these rules, or else your file may not work:

* Each Game Element line must end with a closing tag, like this: />.
* The last two lines of the file must be closing tags for the Games and Schedule Elements, like this: </GAMES> </SCHEDULE> The case of these tags must match the case of the opening tags. So, if the file started with "<Schedule..." and the closing tag was "/SCHEDULE>", it would cause the file not to work.