Strike Eagle Eye

The following co-ordinate system is used in this document, with the axes assigned based on the order that co-ordinates are stored in the data files:

In many of the game's data files, 2D coordinates are used, with no Y co-ordinate value specified.

An object consists of a 3D model which can appear at any number of locations on the ground, plus associated attributes and behaviour. The model may appear flat, or consist of a number of visually separate 3D parts, such as a number of unconnected buildings, but still consists of a single 3D model^[1].

Examples of objects include air traffic control towers, patrol boats, oil rigs, SAM radar sites and camels.

There may be multiple instances of each object in the world, each of which:

Each object:

When an object visually consists of separate parts, those parts may be sub-objects which have their own names and which may be destroyed separately; the section called “Object and Sub-Object Data” describes how sub-objects are associated with objects. When the player destroys an object (or part of it if it has sub-objects), the same 3D model is still displayed at the same location, but some parts of the model may be rendered differently to simulate damage (see the section called “Condition Prefix Sub-Element” ).

A world file contains the following information about a theater of war:

The game ships with three world files, DS0.WLD, KO0.WLD and PA0.WLD. Each time a mission is created for a theater (FIXME:xref), a modified version of the .WLD file without the 0 (e.g. DS.WLD) is created^[2]. In these modified versions of the world files, some enemy units are moved, for example SAM sites can appear and disappear (FIXME: or are they moved? does the unit count always stay the same?) and naval units move.

[Friendly] object name destroyed by weapon name

The enemy file is a square bitmap covering the surface of the earth in the theater indicating which parts of the theater are controlled by the enemy. When the user destroys an object, this bitmap is used to determine whether the object is considered "Friendly" or not. This bitmap also determines which of the level 1 tile indices specified in (FIXME: reference .DAT file's enemy SAM/airbase information - specifically assume that this file is used to determine which tile indices referenced in ??0.DAT should be randomly selected from when generating ??.DAT) should "attack" the user (via radar "spikes", launching SAMs or launching aircraft from a runway) and which of the AAA guns specified in the Object placement information for the applicable level 1 tiles should fire on the user; the non-enemy SAM/AAA/airbases are completely passive.

This file is 512 bytes long and can be viewed as a 64 * 64 row-major array of bits covering the theater such that one bit in the array corresponds to a 4 * 4 block of level 1 tiles in the level 0 tile. Each row consists of 8 bytes, for a total of 64 bits, where the most-significant bit of the first byte has index 0 and the least-significant bit of the last byte has index 63. The file consists of 64 such rows, with the first having index 0 and the last having index 63. (FIXME: reference co-ordinates section which says X co-ordinate increases to the east, etc.)

A bit in the array is set to zero if the corresponding 4 * 4 block of level 1 tiles in the level 0 tile is enemy-controlled, and set to one if the block is friendly.

This file contains various information about the theater. As for the .WLD file (see Section I, “World (.WLD) File”), the game ships with three of these files, DS0.DAT, KO0.DAT and PA0.DAT, and each time a mission is created for a theater, a modified version of the file without the 0 (e.g. DS.DAT) is created. However, in the case of the .DAT file, there is some difference in the format of the data in the ??0.DAT and ??.DAT files. This difference applies only to the enemy/home plate data and is described in the section called “Co-ordinates and Tile Indices in Enemy/Home Plate Records”. It appears that it is only in this section that the ??0.DAT and ??.DAT files differ.

[Friendly] object name destroyed by weapon name

Model Palette

This part of the file provides a 256-entry palette specifying the colours/textures to be used when displaying models from any of the .3DX files used in the theater. Tracers from AAA guns are also affected by this palette, but tracers from the player's F-15 and enemy aircraft are not. Single-pixel dots used to represent aircraft and missiles at long distances from the viewer are also not affected by this palette. The colour values used in the sub-elements in the .3DX files are used to index into the array of palette entries. Each palette entry consists of 2 bytes as described in Table 2.11, “Model Palette Entry Interpretation” .

Table 2.11. Model Palette Entry Interpretation

Second byte value	Colour or texture drawn [a]	Use in supplied ??0.DAT files [a]
0xFA	Partially transparent; in most cases, the value of a seems to have no effect, but for some values such as 81 and 153 it results in the cockpit glass appearing to be very dark gray with all shapes in the cockpit appearing dark green	For entries 128 and 145 only, with a always set to 0
0xFB	Completely transparent; a appears to be ignored although all possible values for it have not been tested	For entry 10 only, with a always set to 0xFB as well
0xFC	Dithering of transparency and a	In the DS theater, colour index 28 which is used for the GCI radar antennae is a dithering of transparency and dark green (VGA palette index 175)
0xFD	Transparent, with a used to adjust palette indices of other surfaces viewed through the surface as shown by the following test results where the value of a was set to one of the following values and the cockpit of the player's F-15 was observed: 0: the cockpit glass is completely transparent 2: the shapes in the cockpit are drawn using VGA palette index 62 instead of 60 and the sky texture visible through the cockpit glass appears to be drawn with VGA palette indices 2 greater than before as well 4: the change in the sky is more obvious than with 2, but the shapes in the cockpit still use palette index 62 suggesting that the game is aware of the gradients in the palette and avoids changing the hue when using a to adjust palette indices 64: the hue of the shapes in the cockpit is changed to brown, suggesting that the game only supports a particular range of values for a when attempting to avoid hue changes.	Not used
0xFE	Solid a	Not used
0xFF	Solid a	Approximately 90% of entries are of this type
other	Dithering of a and b	For entries 137 to 143 inclusive as referenced by ??MTNS.3DX in all theaters, although in the KO and PA theaters, most entries use equal values for a and b, causing a solid colour to appear instead of dithering
[a] a and b refer to the first and second bytes in the palette entry respectively.

F-15 cockpit showing use of unmodified palette entry with 0xFA for glass

F-15 cockpit showing use of modified palette entry with 0xFB for glass

GCI radar in DS theater showing use of palette entry with 0xFC

Special Palette Entries

Palette index 146 is handled specially by the game. This special handling occurs when this value is used as the colour for a sub-element in a .3DX file, but not when it appears in a palette entry in the .DAT file or is used in the level 3 tile set in a .WLD file. The contents of the corresponding palette entry are ignored by the game and the behaviour is instead as follows:

1. When used in F15AIR3.3DX, PLANE1.3DX, PLANE2.3DX (i.e. all model files used for aircraft) and .3DX files for weapons and other stores (e.g. FUEL_RW.3DX), the game first draws the corresponding sub-element with VGA palette index 147 (bright red), then with 146 (dark red), then does not draw the element, draws it using palette index 146 again and then repeats the cycle, causing the sub-element to appear as a flashing red light. This .3DX file defines point sub-elements on the leading edges of both wings and on the tip of the starboard vertical stabiliser, causing flashing red lights to appear in these places on the player's F-15 when the player has turned on the running lights using Shift+L.

2. When used in ??[MOB][M].3DX (i.e. all model files used for ground objects), the game behaves as for 1 except that the steps where VGA palette index 146 is used are removed, i.e. the sub-element alternates between bright red and not drawn, and the flashing is of a lower frequency.

3. When used in ??MTNS.3DX, the game always draws the sub-element using VGA palette index 146, i.e. the element does not flash. Note however that the palette entry with index 146 is still ignored.

The range file specifies, for each home plate, the area in the world from which targets can be selected when that home plate is used for a mission. Each area is specified in the form of a bitmap with a resolution of one level 1 tile. These bitmaps always have an X dimension of 256 level 1 tiles but have a variable Z dimension.

Each bitmap can be viewed as a 256 * Z row-major array of bits. Each row consists of 32 bytes, for a total of 256 bits, where the most-significant bit of the first byte has index 0 and the least-significant bit of the last byte has index 255. A bit in the array is set to 1 if the corresponding level 1 tile is within range of the home plate or 0 if it is not. As expected, all tile co-ordinate rows in the level 0 tile that lie outside of the range of Z tile co-ordinates specified in the record are not considered to be within range of the home plate.

The level 1 tiles selected by the bitmaps in this file should correspond to those marked as enemy tiles in the .NMY file (see Section II, “Enemy (.NMY) File”), otherwise the game will select mission objectives which will be treated as friendly when destroyed by the player.

The available missions file lists the available missions for the theater. Each mission entry references a level 1 tile index to which the mission can apply, so if there is for example a “SAM SITE” mission, when generating the mission the game can select from one of many SAM sites in the theater.

The selected missions file lists the three missions selected for the user's current sortie plus additional information about the sortie.

If the level 1 tile index at offset 0x0 occurs many times in the level 0 tile, it will take the game some time to generate the user's mission - this will be observed as a delay entering the mission briefing room.

These files are only created by the game when a player starts a campaign. The base file name consists of the theater designator, e.g. DS, followed by the player's roster index in the range 0 to 7, so if the player with the right-most locker in the roster screen is playing a campaign in the Desert Storm theater, the file names DS7.CMP and DS7.EXP would be used.

Campaign Destroyed Targets (.EXP) File

This file records the objects that the player has destroyed during the campaign, whether or not they were mission objectives. At the end of each mission, the game updates this file to reflect the new targets destroyed during the mission. The number of records stored at offset 0x0 is incremented by the number of targets destroyed and, as documented in the section called “Campaign destroyed targets are overwritten”, the existing records at the start of the file are overwritten with the new data and new records with all fields set to 0 are added to the end of the file.

Table 2.20. Campaign Destroyed Targets (.EXP) File Format

Offset (bytes)	Length (bytes)	Description
0x0	0x2	Number of records n
0x2	0x6 * n	n records of format described in Table 2.21, “Campaign Destroyed Target Record Format”
0x2 + 0x6 * n		End-of-file

Table 2.21. Campaign Destroyed Target Record Format

Offset (bytes)	Length (bytes)	Description
0x0	0x1	X tile co-ordinate within the level 0 tile
0x1	0x1	Z tile co-ordinate within the level 0 tile
0x2	0x2	0-based index into the object list for the level 1 tile referenced by the above co-ordinates
0x4	0x2	Bit list indicating which sub-models of the object were destroyed or 0xFFFF if the object does not have any sub-models. In the case where this is a bit list, it is expected that the most significant 8 bits are all set to 0 as no model supplied with the game has more than 8 sub-models. Each bit number n (with 0 being the LSB) corresponds to the model's conditional magic (FIXME: xref to model information) with value 0x92 + n where the conditional should be set/true if and only if the bit is set to 1. If this field is set to 0xFFFF, the conditional magic with value 0x81 (if it exists) is used instead.

Case Study

In version 4108.03 of the game, during a campaign in the Desert Storm theater, the primary objective for a mission is “AAA EMPLACMENTS (sic) N3449 E4517” . The primary objective information in MISSIONS.F15 reveals that:

• the level 1 tile index containing the objective is 0x37;

• the tile co-ordinates within the level 0 tile of the level 1 tile containing the objective are ( 0x95, 0x28);

• only one mission target record has a 1-based index into the object list which is non-zero and this value is 6 (the last four, unknown bytes of the record are FF000200); and

• the number of targeted objects that must be destroyed is 2.

It can be confirmed that the byte at offset 0x2895 in DS.WLD is equal to 0x37 . In the same file, the object placement information (see the section called “Object placement information” ) for level 1 tile index 0x37 contains the value 27 at index 5. In DS.DAT , the object description for object 27 is “City” . Model index 27 in DS.3DX has 8 buildings, 4 of which appear to have AAA guns on top of them. When set, conditional magic values (FIXME: xref) 0x92 to 0x99 each cause one of these buildings to appear destroyed, with the even-numbered values corresponding to the buildings with AAA guns on them. The object descriptions in DS.DAT for objects 81-88 appear to apply to these sub-models; these descriptions alternate between “AAA Gun” and “Building” .

When the primary objective is attacked using CBU-87 CEM, the following messages appear:

(WSO) City destroyed by CBU87
(WSO) PRIMARY MISSION ACHIEVED!

Inspection of the target area using reverse padlock ( F10 ) view reveals that not all of the buildings appear destroyed although due to the explosion animations it is very difficult to determine exactly how many are destroyed. In the debrief, “Hit AAA Gun” appears 4 times with no other “Hit” messages shown.

Inspection of the DS7.EXP file reveals that the number of records is increased by 1 compared to the state of the file prior to the mission, a new record consisting entirely of 0 s is appended to the file, and the first record in the file contains: ^[5]

• tile co-ordinates within the level 0 tile ( 0x95, 0x28) which match the co-ordinates from MISSIONS.F15;

• 0-based index into the object list for the level 1 tile equal to 5 which is consistent with the object list entry referenced in MISSIONS.F15;^[6] and

• bit list equal to 0x55, equal to 01010101 in binary where bits 0, 2, 4 and 6 are set, which is consistent with the even-numbered conditional magic values for the model corresponding to the buildings which appear to have AAA guns on them and is also consistent with the object descriptions in DS.DAT.

As a result of these values being recorded in the DSP7.EXP file, during the next mission these objects still appear destroyed (without the explosion animations) as shown below:

Destroyed “AAA Guns” in the “City” due to the .EXP file

For comparison, the following figure shows the “City” model with none of the buildings destroyed and with the conditional magic value for each building superimposed over the building:

“City” annotated with conditional magic numbers^[7]

This file contains the animation shown on the monitor in the briefing room when the player is viewing the map in that room. This animation is played in a loop and alternately shows the primary and secondary objectives in black-and-white. The file is generated when the player first selects the map in the briefing room.

This file consists of two 16-frame animations, one animation for each objective, with no file header. Each frame is of size 4060 bytes: 70 pixels wide, 58 pixels high and 8 bits per pixel. The top-left pixel of each frame is drawn at screen location (3, 121) by the game. The palette used for display of the video differs from that used when the player is in the cockpit.

These files are 8kHz 8-bit mono raw PCM wave files with no header information. The .8 files are used in the title animation with one file for each spoken phrase. The F153.BIN file contains all the wave audio used in the game with phrases generated by playing back multiple clips from the file; a separate table containing the offset and length of each word/phrase/phrase part must be present in some other part of the game.

This executable program file appears to be the main executable program that implements the non-simulation part of the game, including the main screen, theater selection, the briefing room and the arming screen.

This file is compressed using FIXME. After decompression using FIXME, the following data can be found in it:

This executable program file appears to be the main executable program that implements the simulation part of the game, i.e. the part where the player is flying the plane.

This file is compressed using FIXME. After decompression using FIXME, the following data can be found in it:

A large number of .3DX files are provided with the game. Each file contains a number of 3D models that can be drawn during the mission. The files containing all aircraft, objects and lights that appear on the ground and mountains are referenced by the data described in the section called “Main .3DX File Names” and the files containing the external stores for the player's aircraft are referenced by the data described in the section called “Stores .3DX File Names”.

Each file begins with a header (see the section called “File Header”) followed by variable-length data for each model (see the section called “Model Data”) and finally a file terminator record (see the section called “File Terminator Record”).

This file format, with some variations, is also used by Microprose F-117A™ Stealth Fighter 2.0.

Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.