# Scenario Folder

Scenario Folder
Scenario folders are used to group a number of scenarios. Scenario folders are displayed with a book icon in the startup screen which can then be opened to list contained scenarios.
Scenario Components (ocs)

*.ocs
  Scenario folders can contain any number of scenarios.
*.ocf
  Scenario folders can also contain other scenario folders.
Title.png
  The title picture of the scenario folder in png format. Size: 200x150 pixel.
Icon.png
  The icon of a scenario folder which is to be displayed instead of the book icon. 24x24 pixels, alpha channel is used for transparency.
Desc*.rtf
  The description text of the scenario in rich text format (rtf). '__' is to be replaced by the two digit language code, e.g. DE for German and US for American English. Multiple descriptions for several languages can be contained in a scenario file of which the game will automatically load the one appropriate for the configured language.
  The font of the description text is set internally on display. The character size in the file should be 10pt for headings and 8pt for text. Images or other rtf tags are ignored.
  It is recommended to edit this file using a small scale rtf editor such as WordPad.exe in Windows and not a full-blown word processor such as Word as these will stuff kilobytes of unneeded extra information into the rtf file.
Title.txt
  By default, the title of a scenario is set when renaming the scenario in the menu system and stored in section [Head] of Scenario.txt. The file name of the scenario group file may differ. For language dependent titles you should create a Title.txt component with the appropriate contents:
  `DE:Meine Rundensammlung US:My scenario collection` Important: No quotation marks and special characters should be used.
FolderMap.txt
  Scenario folders can also contain graphical folder maps for the selection of scenarios.
Loader*.png
  Scenario folders can contain local loader screens. Also see scenarios. The overloading rules apply.
Material.ocg
  Scenario folders can contain local material definitions. Also see scenarios. The overloading rules apply.
Graphics.ocg
  Scenario folders can overload individual entries of the global Graphics.ocg group. See overloading rules.
Music.ocg
  Scenario folders can contain local music files. Also see scenarios. The overloading rules apply.
*.ocd
  Scenario folders can contain object definitions, which will then be available in all scenarios contained in the folder.Also see scenarios. The overloading rules apply.
Info.txt
  Here an author can store additional information about the development of his scenario, his email address, or other information he wants to share with other developers.
Author.txt
  Should contain the name of the author in format "Firstname Lastname (Nick)" and is used to maintain the name of the original author, if the scenario group file is edited by another developer at a later point in time.

Sven2
2006-09