marko10_000
/
openclonk
forked from Mirrors/openclonk
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: fixed spacing of title images to titles

Tobias Zwick 2011-06-29 14:22:23 +02:00
parent 1310bf2090
commit 262d6c5ac1
6 changed files with 60 additions and 60 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/sdk/definition/index.xml
View File

@ -9,63 +9,63 @@
<text>Object definitions are used for all game objects in clonk: fire monsters, the wooden hut, and the clonk himself. An object definition is a group file composed from the following components:</text>
<h id="ObjektdefinitionsKomponentenOCD">Object Definition Components (ocd)</h>
<dl>
<dt><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="definition/defcore.html">DefCore.txt</emlink></dt>
<dt><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="definition/defcore.html">DefCore.txt</emlink></dt>
<dd>
<text>Object properties.</text>
</dd>
<dt id="Graphicspng"><img height="16" src="../../images/icon_image.png" width="16"/>Graphics.png</dt>
<dt id="Graphicspng"><img height="16" src="../../images/icon_image.png" width="16"/> Graphics.png</dt>
<dd>
<text>Graphics of the object. Base graphics, animation phases and a picture for display in menus are stored in a 32 bit picture with transparency channel (PNG format, 32 bit RGBA color, non interlaced).</text>
</dd>
<dt id="Overlaypng"><img height="16" src="../../images/icon_image.png" width="16"/>Overlay.png</dt>
<dt id="Overlaypng"><img height="16" src="../../images/icon_image.png" width="16"/> Overlay.png</dt>
<dd>
<text>The part of the object's graphics which is to be colored in the player color (see ColorByOwner in DefCore.txt) can also be defined using a separate graphics file. In this way you can also use the color blue in the object's graphics for effects other than player color and antialiasing of the player color sections becomes possible. In Overlay.png gray scales should be used instead of blue color.</text>
</dd>
<dt id="Graphicsmesh"><img height="16" src="../../images/icon_ogre_mesh.png" width="16"/><emlink href="definition/meshes.html">Graphics.mesh</emlink></dt>
<dt id="Graphicsmesh"><img height="16" src="../../images/icon_ogre_mesh.png" width="16"/> <emlink href="definition/meshes.html">Graphics.mesh</emlink></dt>
<dd>
<text>Since OC a 3D model can be used as an object's graphics instead of a bitmap in BMP or PNG format. It needs to be provided in OGRE format. There are exporters for most 3D modeling tools. All files that are required by the mesh (especially material scripts, textures and skeletons) need also to be present in the object.</text>
</dd>
<dt id="Graphicsskeleton"><img height="16" src="../../images/icon_ogre_mesh.png" width="16"/>*.skeleton</dt>
<dt id="Graphicsskeleton"><img height="16" src="../../images/icon_ogre_mesh.png" width="16"/> *.skeleton</dt>
<dd>
<text>Skeleton files contain bones and animations for a 3D model. They are usually created by the exporter if bones and/or animations are used for the mesh.</text>
</dd>
<dt id="Graphicsex"><img height="16" src="../../images/icon_image.png" width="16"/>Graphics*.png/Overlay*.png</dt>
<dt id="Graphicsex"><img height="16" src="../../images/icon_image.png" width="16"/> Graphics*.png/Overlay*.png</dt>
<dd>
<text>Objects can also contain alternative sets of graphics which can be selected ingame using the script command <emlink href="script/fn/SetGraphics.html">SetGraphics</emlink>(). The name corresponds to the file name portion following "Graphics". The matching overlay is automatically selected. For more information see <emlink href="script/fn/SetGraphics.html">SetGraphics</emlink>().</text>
</dd>
<dt id="MaterialScripts"><img height="16" src="../../images/icon_ogre_mesh.png" width="16"/><emlink href="definition/meshes.html#MaterialScripts">*.material</emlink></dt>
<dt id="MaterialScripts"><img height="16" src="../../images/icon_ogre_mesh.png" width="16"/> <emlink href="definition/meshes.html#MaterialScripts">*.material</emlink></dt>
<dd>
<text>OGRE material scripts are simple text files which contain information about the material of a 3D model. Each model is assigned a material which specifies how it is rendered. Normally these scripts are being generated by the exporter, but they can also be hand-edited afterwards (using a text editor) to apply additional effects.</text>
</dd>
<dt id="ScriptcScript__c"><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="definition/script.html">Script.c</emlink></dt>
<dt id="ScriptcScript__c"><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="definition/script.html">Script.c</emlink></dt>
<dd>
<text>The object script. See <emlink href="script/index.html">script documentation</emlink> and <emlink href="lang.html">localization</emlink>.</text>
</dd>
<dt><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="definition/actmap.html">ActMap in the Script.c</emlink></dt>
<dt><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="definition/actmap.html">ActMap in the Script.c</emlink></dt>
<dd>
<text>Table for activities.</text>
</dd>
<dt id="Ranktxt"><img height="16" src="../../images/icon_text.png" width="16"/>Rank.txt/Rank*.txt</dt>
<dt id="Ranktxt"><img height="16" src="../../images/icon_text.png" width="16"/> Rank.txt/Rank*.txt</dt>
<dd>
<text>For object definitions defining a clonk type you can specify custom rank names for this clonk type here. The rank names will then also replace rank names of existing crew members of this type. The file should contain a simple text list of names of maximum 30 characters each. For an example see the knight in the Knights pack. By using the approriate language codes you can create language dependent sets of rank names.</text>
</dd>
<dt id="Rankbmppng"><img height="16" src="../../images/icon_image.png" width="16"/>Rank.png</dt>
<dt id="Rankbmppng"><img height="16" src="../../images/icon_image.png" width="16"/> Rank.png</dt>
<dd>
<text>You can also define custom rank symbols for clonk types which are then displayed in the game instead of the standard symbols from Graphics.ocg. A rank symbol should always be square and there should be enough many symbols for all ranks. For ranks exceeding the last symbol, the list is repeated from the front and a star is added to the symbol.</text>
</dd>
<dt id="wav"><img height="16" src="../../images/icon_sound.png" width="16"/>*.wav/*.ogg</dt>
<dt id="wav"><img height="16" src="../../images/icon_sound.png" width="16"/> *.wav/*.ogg</dt>
<dd>
<text>Object local sounds. As these are always loaded and not dynamically unloaded as are scenario sounds you should use these sparingly and with small sound files only.</text>
</dd>
<dt id="ocd"><img height="16" src="../../images/icon_object_definition.png" width="16"/>*.ocd</dt>
<dt id="ocd"><img height="16" src="../../images/icon_object_definition.png" width="16"/> *.ocd</dt>
<dd>
<text>The engine will also search all valid ocd subdirectories for additional object definitions. Object definitions should be grouped by category.</text>
</dd>
<dt id="Infotxt"><img height="16" src="../../images/icon_text.png" width="16"/>Info.txt</dt>
<dt id="Infotxt"><img height="16" src="../../images/icon_text.png" width="16"/> Info.txt</dt>
<dd>
<text>This component is not processed by the engine. Here the author can store additional information he wants to share with other developers.</text>
</dd>
<dt id="Authortxt"><img height="16" src="../../images/icon_text.png" width="16"/>Author.txt</dt>
<dt id="Authortxt"><img height="16" src="../../images/icon_text.png" width="16"/> Author.txt</dt>
<dd>
<text>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 group file is edited by another developer at a later point in time.</text>
</dd>

10
docs/sdk/files.xml
View File

@ -7,23 +7,23 @@
<h id="Spieldaten">Game Data</h>
<text>The game data of clonk is stored in compressed group files which each contain one component or further group files.</text>
<dl>
<dt id="Spielerdateienocp"><img height="16" src="../images/icon_player.png" width="16"/>Player Files (ocp)</dt>
<dt id="Spielerdateienocp"><img height="16" src="../images/icon_player.png" width="16"/> Player Files (ocp)</dt>
<dd>
<text>Player files contain personal settings, gained score and information about the crew. It may also contain a portrait file.</text>
</dd>
<dt id="Szenarienocs"><img height="16" src="../images/icon_scenario.png" width="16"/><emlink href="scenario/index.html">Scenarios (ocs)</emlink></dt>
<dt id="Szenarienocs"><img height="16" src="../images/icon_scenario.png" width="16"/> <emlink href="scenario/index.html">Scenarios (ocs)</emlink></dt>
<dd>
<text>Scenario files consist of an information core and additional components, such as a landscape, title image, description texts, sky graphics, a script, local object definitions, etc.</text>
</dd>
<dt id="Objektdefinitionenocd"><img height="16" src="../images/icon_object_definition.png" width="16"/><emlink href="definition/index.html">Object Definitions (ocd)</emlink></dt>
<dt id="Objektdefinitionenocd"><img height="16" src="../images/icon_object_definition.png" width="16"/> <emlink href="definition/index.html">Object Definitions (ocd)</emlink></dt>
<dd>
<text>Object definitions contain an information core, graphic elements, action tables, script, and descriptive text. Also, <emlink href="particle/index.html">particles</emlink> are stored in object definition folders.</text>
</dd>
<dt id="Rundenordnerocf"><img height="16" src="../images/icon_scenario_folder.png" width="16"/><emlink href="folder/index.html">Scenario Folders (ocf)</emlink></dt>
<dt id="Rundenordnerocf"><img height="16" src="../images/icon_scenario_folder.png" width="16"/> <emlink href="folder/index.html">Scenario Folders (ocf)</emlink></dt>
<dd>
<text>Scenarios are grouped in scenario folders.</text>
</dd>
<dt id="Systemdatenocg"><img height="16" src="../images/icon_system.png" width="16"/>System Data (ocg)</dt>
<dt id="Systemdatenocg"><img height="16" src="../images/icon_system.png" width="16"/> System Data (ocg)</dt>
<dd>
<text>Graphics, sound, and music of the original game are grouped in these folders and should not be modified.</text>
<text>Using the menu system, group files can be edited and/or converted to normal directories. Group file components can then be edited using common applications for text or graphics editing. Menu system and game engine can both load packed group files or unpacked directories directly.</text>

24
docs/sdk/folder/index.xml
View File

@ -9,43 +9,43 @@
<text>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.</text>
<h id="Components">Scenario Components (ocs)</h>
<dl>
<dt id="ocs"><img height="16" src="../../images/icon_scenario.png" width="16"/><emlink href="scenario/index.html">*.ocs</emlink></dt>
<dt id="ocs"><img height="16" src="../../images/icon_scenario.png" width="16"/> <emlink href="scenario/index.html">*.ocs</emlink></dt>
<dd>
<text>Scenario folders can contain any number of scenarios.</text>
</dd>
<dt id="ocf"><img height="16" src="../../images/icon_scenario_folder.png" width="16"/>*.ocf</dt>
<dt id="ocf"><img height="16" src="../../images/icon_scenario_folder.png" width="16"/> *.ocf</dt>
<dd>
<text>Scenario folders can also contain other scenario folders.</text>
</dd>
<dt id="Title"><img height="16" src="../../images/icon_image.png" width="16"/>Title.png/Title.bmp</dt>
<dt id="Title"><img height="16" src="../../images/icon_image.png" width="16"/> Title.png/Title.bmp</dt>
<dd>
<text>The title picture of the scenario folder in png format. Size: 200x150 pixel. The older bmp format with 256 colors is still supported as well.</text>
</dd>
<dt id="Icon"><img height="16" src="../../images/icon_image.png" width="16"/>Icon.bmp/Icon.png</dt>
<dt id="Icon"><img height="16" src="../../images/icon_image.png" width="16"/> Icon.bmp/Icon.png</dt>
<dd>
<text>The icon of a scenario folder which is to be displayed instead of the book icon. BMP format (obsolete): 16x16 pixels, color RGB 255 0 255 (purple) is transparent. PNG format: 24x24 pixels, alpha channel is used for transparency.</text>
</dd>
<dt id="Desc__rtf"><img height="16" src="../../images/icon_text.png" width="16"/>Desc*.rtf</dt>
<dt id="Desc__rtf"><img height="16" src="../../images/icon_text.png" width="16"/> Desc*.rtf</dt>
<dd>
<text>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.</text>
<text>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.</text>
<text>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.</text>
</dd>
<dt id="Titletxt"><img height="16" src="../../images/icon_text.png" width="16"/>Title.txt</dt>
<dt id="Titletxt"><img height="16" src="../../images/icon_text.png" width="16"/> Title.txt</dt>
<dd>
<text>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:</text>
<code>DE:Meine Rundensammlung
US:My scenario collection</code> <text>Important: No quotation marks and special characters should be used.</text>
</dd>
<dt id="FolderMaptxt"><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="folder/foldermap.html">FolderMap.txt</emlink></dt>
<dt id="FolderMaptxt"><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="folder/foldermap.html">FolderMap.txt</emlink></dt>
<dd>
<text>From CR, scenario folders can also contain graphical folder maps for the selection of scenarios.</text>
</dd>
<dt id="Loader"><img height="16" src="../../images/icon_image.png" width="16"/>Loader*.png/Loader*.bmp</dt>
<dt id="Loader"><img height="16" src="../../images/icon_image.png" width="16"/> Loader*.png/Loader*.bmp</dt>
<dd>
<text>Scenario folders can contain local loader screens. Also see <emlink href="scenario/index.html">scenarios</emlink>. The <emlink href="scenario/index.html#UeberladungenOCS">overloading rules</emlink> apply.</text>
</dd>
<dt id="Materialocg"><img height="16" src="../../images/icon_system.png" width="16"/><emlink href="material/index.html">Material.ocg</emlink></dt>
<dt id="Materialocg"><img height="16" src="../../images/icon_system.png" width="16"/> <emlink href="material/index.html">Material.ocg</emlink></dt>
<dd>
<text>Scenario folders can contain local material definitions. Also see <emlink href="scenario/index.html#Materialocg">scenarios</emlink>. The <emlink href="scenario/index.html#UeberladungenOCS">overloading rules</emlink> apply.</text>
</dd>
@ -57,15 +57,15 @@ US:My scenario collection</code> <text>Important: No quotation marks and
<dd>
<text>Scenario folders can contain local music files. Also see <emlink href="scenario/index.html#Musicocg">scenarios</emlink>. The <emlink href="scenario/index.html#UeberladungenOCS">overloading rules</emlink> apply.</text>
</dd>
<dt id="ocd"><img height="16" src="../../images/icon_object_definition.png" width="16"/><emlink href="definition/index.html">*.ocd</emlink></dt>
<dt id="ocd"><img height="16" src="../../images/icon_object_definition.png" width="16"/> <emlink href="definition/index.html">*.ocd</emlink></dt>
<dd>
<text>Scenario folders can contain object definitions, which will then be available in all scenarios contained in the folder.Also see <emlink href="scenario/index.html#ocd">scenarios</emlink>. The <emlink href="scenario/index.html#UeberladungenOCS">overloading rules</emlink> apply.</text>
</dd>
<dt id="Infotxt"><img height="16" src="../../images/icon_text.png" width="16"/>Info.txt</dt>
<dt id="Infotxt"><img height="16" src="../../images/icon_text.png" width="16"/> Info.txt</dt>
<dd>
<text>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.</text>
</dd>
<dt id="Authortxt"><img height="16" src="../../images/icon_text.png" width="16"/>Author.txt</dt>
<dt id="Authortxt"><img height="16" src="../../images/icon_text.png" width="16"/> Author.txt</dt>
<dd>
<text>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. The name stored here is only displayed, however, if the scenario was edited by RedWolf Design. This feature is mainly used for contest scenarios.</text>
</dd>

6
docs/sdk/material/index.xml
View File

@ -9,17 +9,17 @@
<text>Using material definitions you can specify looks and behaviour of the landscape materials.</text>
<h id="MaterialdefinitionsKomponentenMaterialocg">Material Definition Components (Material.ocg)</h>
<dl>
<dt id="TexMaptxt"><img height="16" src="../../images/icon_text.png" width="16"/>TexMap.txt</dt>
<dt id="TexMaptxt"><img height="16" src="../../images/icon_text.png" width="16"/> TexMap.txt</dt>
<dd>
<text>Lookup table for color indices in static and dynamic landscapes. Colors 0-127 are matched to a material-texture-reference. Colors 128-255 are matched to the same list of references only these are marked 'underground'.</text>
<text>The engine will draw materials with a higher index above those with a lower index so that, e.g. using the standard table, rough chunks of earth will overlap water which has a smooth border. Mineral resources have an even higher index so that their rough border overlaps the earth and not the other way around. This is also the reason why there might be differing numbers of total pixels of a given material drawn than you might expect just from calculating the square sizes of the unzoomed map materials.</text>
<text>If a custom map fails with the message 'texture n undefined' you should define the specified texture in the TexMap. You should always use a paint program capable of editing indexed color palettes without modifying the palette (MS Paint is not suited for this).</text>
</dd>
<dt id="ocm"><img height="16" src="../../images/icon_material.png" width="16"/><emlink href="material/ocm.html">*.ocm</emlink></dt>
<dt id="ocm"><img height="16" src="../../images/icon_material.png" width="16"/> <emlink href="material/ocm.html">*.ocm</emlink></dt>
<dd>
<text>The engine will accept up to 125 material definitions at a time. OCM files a simple text files. The materials Vehicle, Tunnel, Water, Snow, Granite, Sand, and Earth must always be available.</text>
</dd>
<dt id="bmp"><img height="16" src="../../images/icon_image.png" width="16"/>*.png/*.bmp</dt>
<dt id="bmp"><img height="16" src="../../images/icon_image.png" width="16"/> *.png/*.bmp</dt>
<dd>
<text>There can be any number of textures in PNG or uncompressed Windows BMP format (with 256 colors) in any material group. Width and height of each bitmap must be powers of 2 (that is 16, 32, 64, 128, 256, etc.) With the old BMP format only the first three colors of the texture bitmap may be used as to these the three material colors are applied.</text>
</dd>

4
docs/sdk/particle/index.xml
View File

@ -11,11 +11,11 @@
<text>Particles are not stored in savegames and are designed for temporary visual effects only.</text>
<h id="PartikelKomponentenOCD">Particle Components (ocd)</h>
<dl>
<dt><img height="16" src="../../images/icon_text.png" width="16"/>Particle.txt</dt>
<dt><img height="16" src="../../images/icon_text.png" width="16"/> Particle.txt</dt>
<dd>
<text>Particle properties.</text>
</dd>
<dt id="Graphicspng"><img height="16" src="../../images/icon_image.png" width="16"/>Graphics.png</dt>
<dt id="Graphicspng"><img height="16" src="../../images/icon_image.png" width="16"/> Graphics.png</dt>
<dd>
<text>Particle graphics.</text>
<text>The particle definition can also contain the known components of <emlink href="definition/index.html">object definitions</emlink> for describing the particle (e.g. Title.png, DescDE/US.txt, etc.)</text>

46
docs/sdk/scenario/index.xml
View File

@ -9,101 +9,101 @@
<text>Scenarios are the playing worlds which the player can select and start from the menu. With their components the scenario designer can adjust freely everything from the landscape, the goals and rules, the available objects and materials to the look in the menu.</text>
<h id="SzenarioKomponentenOCS">Scenario Components (ocs)</h>
<dl>
<dt id="Szenariotxt"><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="scenario/scenario.html">Scenario.txt</emlink></dt>
<dt id="Szenariotxt"><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="scenario/scenario.html">Scenario.txt</emlink></dt>
<dd>
<text>Contains most scenario settings.</text>
</dd>
<dt id="Teamstxt"><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="scenario/Teams.html">Teams.txt</emlink></dt>
<dt id="Teamstxt"><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="scenario/Teams.html">Teams.txt</emlink></dt>
<dd>
<text>Contains the Teamsettings for multiplayer scenarios. Since 4.9.6.0 CR.</text>
</dd>
<dt id="Title"><img height="16" src="../../images/icon_image.png" width="16"/>Title.png</dt>
<dt id="Title"><img height="16" src="../../images/icon_image.png" width="16"/> Title.png</dt>
<dd>
<text>The title picture of the scenario in png format. Size: 200x150 pixel.</text>
</dd>
<dt id="Icon"><img height="16" src="../../images/icon_image.png" width="16"/>Icon.png</dt>
<dt id="Icon"><img height="16" src="../../images/icon_image.png" width="16"/> Icon.png</dt>
<dd>
<text>The icon of the scenario in png format. Size: 24x24 pixel.</text>
</dd>
<dt id="Loader"><img height="16" src="../../images/icon_image.png" width="16"/>Loader*.png</dt>
<dt id="Loader"><img height="16" src="../../images/icon_image.png" width="16"/> Loader*.png</dt>
<dd>
<text>Loader screen to be displayed while the scenario is loading. If multiple files are present (Loader1.png, Loader2.png, Loader3.png...), one is selected randomly. You can optionally specify which loader to use in Scenario.txt. Loader image files located in parent scenario folders are also used.</text>
</dd>
<dt id="Sky"><img height="16" src="../../images/icon_image.png" width="16"/>Sky.png</dt>
<dt id="Sky"><img height="16" src="../../images/icon_image.png" width="16"/> Sky.png</dt>
<dd>
<text>The sky background image. Sky graphics should either be tileable or big enough that it won't even tile if the player zooms out very far.</text>
</dd>
<dt id="Desc__rtf"><img height="16" src="../../images/icon_text.png" width="16"/>Desc*.rtf</dt>
<dt id="Desc__rtf"><img height="16" src="../../images/icon_text.png" width="16"/> Desc*.rtf</dt>
<dd>
<text>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.</text>
<text>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.</text>
<text>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.</text>
</dd>
<dt id="Titletxt"><img height="16" src="../../images/icon_text.png" width="16"/>Title.txt</dt>
<dt id="Titletxt"><img height="16" src="../../images/icon_text.png" width="16"/> Title.txt</dt>
<dd>
<text>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:</text>
<code>DE:Angriff der Killerwipfe
US:Attack of the Killer Wipfs</code> <text>Important: No quotation marks and special characters should be used.</text>
</dd>
<dt id="Scriptc"><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="scenario/script.html">Script.c</emlink></dt>
<dt id="Scriptc"><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="scenario/script.html">Script.c</emlink></dt>
<dd>
<text>The scenario script.</text>
</dd>
<dt id="Landscapebmp"><img height="16" src="../../images/icon_image.png" width="16"/>Map.bmp</dt>
<dt id="Landscapebmp"><img height="16" src="../../images/icon_image.png" width="16"/> Map.bmp</dt>
<dd>
<text>Static landscapes are stretched by factor MapZoom defined in Scenario.txt to the size of the actual landscape in the game. The colors used in Map.bmp correspond to materials and textures as defined in <emlink href="material/index.html#TexMaptxt">TexMap.txt</emlink>.</text>
<text>Exact landscapes represent the actual in-game landscape saved to a bitmap file. The bitmap color indices (128-191 and 192-255, 3 colors per material) correspond directly to the material pixels used in the scenario. The current material list is stored in MatMap.txt.</text>
</dd>
<dt id="Landscapepng"><img height="16" src="../../images/icon_image.png" width="16"/>Landscape.png</dt>
<dt id="Landscapepng"><img height="16" src="../../images/icon_image.png" width="16"/> Landscape.png</dt>
<dd>
<text>Full size map for exact landscapes. This is mainly used in savegames to store the exact terrain including transparent materials and their texture. Exact landscapes consume an extreme amount of memory and should not be used for regularly distributed scenarios.</text>
</dd>
<dt id="Landscapetxt"><img height="16" src="../../images/icon_text.png" width="16"/><emlink href="scenario/MapCreatorS2.html">Landscape.txt</emlink></dt>
<dt id="Landscapetxt"><img height="16" src="../../images/icon_text.png" width="16"/> <emlink href="scenario/MapCreatorS2.html">Landscape.txt</emlink></dt>
<dd>
<text>Advanced scenario designers can use this component to define highly complex, fully random generated dynamic landscapes. This does require certain mathematical skill and some patience, however.</text>
</dd>
<dt id="MatMaptxt"><img height="16" src="../../images/icon_text.png" width="16"/>MatMap.txt</dt>
<dt id="MatMaptxt"><img height="16" src="../../images/icon_text.png" width="16"/> MatMap.txt</dt>
<dd>
<text>Stores the material table used in this scenario. The materials listed here are used by the exact landscape and have to be available in the loaded Material.ocg group.</text>
</dd>
<dt id="Objectstxt"><img height="16" src="../../images/icon_text.png" width="16"/>Objects.txt</dt>
<dt id="Objectstxt"><img height="16" src="../../images/icon_text.png" width="16"/> Objects.txt</dt>
<dd>
<text>This component is generated by the engine and stores runtime object data of a savegame.</text>
</dd>
<dt id="Materialocg"><img height="16" src="../../images/icon_system.png" width="16"/><emlink href="material/index.html">Material.ocg</emlink></dt>
<dt id="Materialocg"><img height="16" src="../../images/icon_system.png" width="16"/> <emlink href="material/index.html">Material.ocg</emlink></dt>
<dd>
<text>Scenarios can contain local material definition groups. See <a href="#UeberladungenOCS">overloading rules</a>.</text>
</dd>
<dt id="Graphicsocg"><img height="16" src="../../images/icon_system.png" width="16"/>Graphics.ocg</dt>
<dt id="Graphicsocg"><img height="16" src="../../images/icon_system.png" width="16"/> Graphics.ocg</dt>
<dd>
<text>Scenarios can overload individual entries of the global Graphics.ocg group. See <a href="#UeberladungenOCS">overloading rules</a>.</text>
</dd>
<dt id="wav"><img height="16" src="../../images/icon_sound.png" width="16"/>*.wav</dt>
<dt id="wav"><img height="16" src="../../images/icon_sound.png" width="16"/> *.wav</dt>
<dd>
<text>Scenarios can contain any number of sound files. These can be played back by script during the game. Scenario local sounds are loaded dynamically on demand which might cause delays with large scenario files.</text>
</dd>
<dt id="mid"><img height="16" src="../../images/icon_music.png" width="16"/>*.mid/*.ogg</dt>
<dt id="mid"><img height="16" src="../../images/icon_music.png" width="16"/> *.mid/*.ogg</dt>
<dd>
<text>If the scenario contains music files, these can be played back during the game in random order. Also see script command <emlink href="script/fn/Music.html">Music</emlink>().</text>
</dd>
<dt id="Musicocg"><img height="16" src="../../images/icon_system.png" width="16"/>Music.ocg</dt>
<dt id="Musicocg"><img height="16" src="../../images/icon_system.png" width="16"/> Music.ocg</dt>
<dd>
<text>Local music files can also be combines in a local music group.</text>
</dd>
<dt id="ocd"><img height="16" src="../../images/icon_object_definition.png" width="16"/><emlink href="definition/index.html">*.ocd</emlink></dt>
<dt id="ocd"><img height="16" src="../../images/icon_object_definition.png" width="16"/> <emlink href="definition/index.html">*.ocd</emlink></dt>
<dd>
<text>Scenarios can contain local object definitions which are then available in that scenario only.</text>
<text>The engine will also search all parent folders (ocf) of the scenario for additional local object definitions. In this way, a scenario folder can contain object definitions which are then available in all its contents scenarios.</text>
</dd>
<dt id="Namestxt"><img height="16" src="../../images/icon_text.png" width="16"/>Names.txt</dt>
<dt id="Namestxt"><img height="16" src="../../images/icon_text.png" width="16"/> Names.txt</dt>
<dd>
<text>These names are used for clonks created in this scenario.</text>
</dd>
<dt id="Infotxt"><img height="16" src="../../images/icon_text.png" width="16"/>Info.txt</dt>
<dt id="Infotxt"><img height="16" src="../../images/icon_text.png" width="16"/> Info.txt</dt>
<dd>
<text>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.</text>
</dd>
<dt id="Authortxt"><img height="16" src="../../images/icon_text.png" width="16"/>Author.txt</dt>
<dt id="Authortxt"><img height="16" src="../../images/icon_text.png" width="16"/> Author.txt</dt>
<dd>
<text>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.</text>
</dd>