Tactical Manual: Creating & submitting battles/missions

In general

There is a high standard for all battles, missions and levels that are to be placed in the Mission Compendium. All battles, missions and levels that are submitted to the Tactical Officer must obey these standards or they will be rejected at the correction stage. The guidelines for each platform can be found below, as well as information on plotlines, medals, and the Review Process. Please follow exactly the submission procedures, or your submission will be simply rejected.

Submission procedure

There are several rules you have to follow, while you submit your battle for EH Mission Compendium:

• A mission creator must have passed the course Mission Creation and Beta Testing Standards (MCBS) from the Imperial Academy
• A mission creator must have passed the misson design course for the platform he is creating for
  • X-Wing Mission Design (XMD)
  • TIE Fighter Mission Creation (TM/3)
  • X-Wing vs. TIE Fighter Mission Design (XTM/1)
  • X-Wing Alliance Mission Design (XAM)
• All text and briefings must be in English
• The battle or mission must be suitable for all ages with no inappropriate content
• The battle or mission must meet standards for its platform (see below)
• The mission creator must have test-flown his missions and provide a pilot file as proof
• The battle must be submitted via an email to the Tactical Officer. You must provide the following information:
  • Battle/Mission Title
  • Game Platform
  • Battle/Mission Type
  • Number of Missions
  • Medal Name - Optional
  • Patches Needed
  • Creator's Name
  • Creator's PIN
  • Creator's E-mail
  • Creator Comments - Optional
  • A zip archive of all required files. (A file too large for email can be uploaded to Google Drive)

All archives must contain the following files:

• Custom battle file
• Mission files
• Pilot file
• Readme.txt
• Optional: patches.txt
• Optional: image of the medal awarded (in .JPG or .PNG or .GIF format)

You can also add storyline to your mission or battle to make it more playable and enjoyable for all members. The Tactical Officer can award you with Commendation of Service for every good storyline you make to your battle. Also, the ratings of your battle may be higher when it contains a storyline.

Battle standards

Every battle submitted to the Mission Compendium must follow the guidelines and regulations of Tactical Office. These guidelines and regulations have been set to help people with their submissions, to make the submission process more efficient and to avoid total chaos with submissions.

Every platform is different, so there are slightly different submission regulations for each platform. You can find the minimum requirements below. These listings are for battles. The same rules apply to free missions, although you only have 1 mission there, there is no medal required, and you can not receive a Commendation of Service for them.

TIE Fighter Battle standards

TIE Fighter is the first and the most popular game of the Emperor's Hammer. There are over 200 TIE Fighter battles and missions and the numbers are still growing. Even with the introduction of new, more advanced gaming platforms like X-Wing Alliance, TIE Fighter is still popular and people still submit battles for it.

The modern mission creation program for TIE Fighter is YOGEME (Ye Olde Galactic Empire Mission Editor). While mission creators are not obliged to use this utility, the use of other tools can create problems when testers or tacticians attempt to open mission files, which can lead to rejection of your battle.

The historically used mission creation program for TIE Fighter is TIE Fighter Workshop by Evan Sabatelli. This the editor explained by the TM/3 university course, but creators may find it difficult to run on current versions of Windows.

All TIE Fighter battles must meet the following standards:

Readme.txt

Every battle must contain this file, with basic information about the battle and its author. It must also contain the disclaimer that is required by LucasArts with ever custom mission (see the bottom of this document). You can find a detailed list of the information expected in a readme file below

Patches.txt

You can include information about required patches (including the EHSP) inside a dedicated file called patches.txt. As the information is required in the readme file, use of this file is optional

Number of missions

Every custom battle must consist of at least 4 missions. Custom battles with more than 8 missions will have to be split across multiple battle files

.LFD file

Every battle must contain a BATTLE1.LFD file which is required to play the battle

Briefings

Animated and officer briefings must be provided for all missions. Providing good debriefings is highly encouraged. The briefings must supply the pilot with enough information to achieve the mission's primary goals (except in certain scenarios)

Radio messages

All missions must utilize the in flight radio messages

TIE95 compatible

TIE95 is the only official TIE version of the Emperor's Hammer. therefore, all EH battles must work with TIE95. You can make it compatible with all TIE versions, but you must consider TIE95 as highest priority. This also means you may NOT use the decoy beam, as this only works in TIE Disk

Updates.txt

This is an optional file, used by Tactical Staff, to list updates made to the battle during the beta testing and correction process.

X-wing vs. TIE Fighter Battle standards

The introduction of X-Wing vs. TIE Fighter was another milestone of the Emperor's Hammer. The game itself had advanced graphic design, much more realistic flying, faster lasers, and even multiplayer ability. Also, the mission creation process was much easier. Pilot files became more advanced and allowed Tactical Officer to limit cheating much more efficiently than in TIE.

The modern mission creation program for X-wing vs. TIE Fighter is YOGEME. While mission creators are not obliged to use this utility, the use of other tools can create problems when testers or tacticians attempt to open mission files, which can lead to rejection of your battle.

The historically used mission creation program for X-Wing vs. TIE Fighter is XvTED by Troy Dangerfield. This the editor explained by the XTM/2 university course, but creators may find it difficult to run on current versions of Windows.

All X-wing vs. TIE Fighter battles must meet the following standards:

Readme.txt

Every battle must contain this file, with basic information about the battle and its author. It must also contain the disclaimer that is required by LucasArts with ever custom mission (see the bottom of this document). You can find a detailed list of the information expected in a readme file below

Patches.txt

You can include information about required patches (including the EHSP) inside a dedicated file called patches.txt. As the information is required in the readme file, use of this file is optional

Number of missions

Every custom battle must consist of at least 4 missions

.LST file

Every battle must contain a IMPERIAL.LST file which is required to play the battle

Briefing and mission introduction text

An animated briefing and a mission introduction text must be provided for all missions. The briefing and mission introduction text must supply the pilot with enough information to achieve the mission goals

Custom goal descriptions

Missions are required to have a 'goals to be completed' and 'goals failed' descriptions for all mission goals (with the exception of the bonus goals) so a pilot will know what to do. All goals (including the bonus goals) must also have custom 'goals completed' messages

Radio messages

All missions must utilize the in flight radio messages

Custom sounds

When included, custom sounds must be recorded at 11kHz, 8-bit mono quality or less, and included in the .WAV format

Balance of Power

XvT battles and missions may not require the Balance of Power addon. If you use ships that are only available in the balance of Power addon, submit your battle as a Balance of Power battle

Updates.txt

This is an optional file, used by Tactical Staff, to list updates made to the battle during the beta testing and correction process.

Balance of Power Battle standards

Balance of Power is add-on to X-Wing vs. TIE Fighter. It upgrades to version 2.0, along with many other good improvements. Ships in BoP can be larger and the graphics engine is more advanced. It has become very popular among EH mission designers.

BoP requirements for battles and free missions are the same as the XvT requirements, with the only difference that the missions must require the Balance of power addon.

X-wing Alliance Battle standards

Although it is over 25 years old, X-Wing Alliance is the newest EH flying simulation. However, with the lack of new games from LucasArts, X-Wing Alliance is the most popular and the most advanced gaming platform of the Emperor's Hammer.

X-Wing Alliance engine offers mission designer the most advanced abilities, not encountered in previous games. Using dynamic goals, four regions and a very high craft limit, it is possible to create outstanding missions with very realistic areas. Also, the craft palette is very large and offers many ships, much more than previous games from the series.

The modern mission creation program for X-wing Alliance is YOGEME. While mission creators are not obliged to use this utility, the use of other tools can create problems when testers or tacticians attempt to open mission files, which can lead to rejection of your battle.

The historically used mission creation program for X-Wing Alliance is AlliED by Troy Dangerfield. This the editor explained by the XAM university course, but creators may find it difficult to run on current versions of Windows.

All X-wing Alliance battles must meet the following standards:

Readme.txt

Every battle must contain this file, with basic information about the battle and its author. It must also contain the disclaimer that is required by LucasArts with ever custom mission (see the bottom of this document). You can find a detailed list of the information expected in a readme file below

Patches.txt

You can include information about required patches (including the EHSP) inside a dedicated file called patches.txt. As the information is required in the readme file, use of this file is optional

Number of missions

Every custom battle must consist of at least 4 missions. Custom battles can have up to 20 missions

.LST file

Every battle must contain a MISSION.LST file which is required to play the battle

Mission file naming standard

Contrary to other games, XWA requires you to name your mission files after a certain standard, or the game will not be able to play them. All mission files must be named 1B8M#---.TIE, where '#' is the mission number, and '---' is extra text (optional)

Briefings and hints

An animated briefing must be provided for all missions. XWA does not give additional briefings, so the animated briefing must supply the pilot with enough information to achieve the mission goals. Providing good mission hints and debriefings is highly encouraged.

Custom goal descriptions

missions are required to have a 'goals to be completed' and 'goals failed' descriptions for all mission goals (with the exception of the bonus goals) so a pilot will know what to do. All goals (including the bonus goals) must also have custom 'goals completed' messages

Radio messages

All missions must utilize the in flight radio messages

Custom sounds

When included, custom sounds must be recorded at 22,050Hz, 16-bit mono quality or less, and included in the .WAV format

Updates.txt

This is an optional file, used by Tactical Staff, to list updates made to the battle during the beta testing and correction process.

TIE Fighter Total Conversion Battle standards

TIE Fighter Total Conversion is a modification to X-Wing Alliance. It changes it to have an Imperial theme, along with many other good improvements. Ships in TFTC are much higher detail and the graphics engine is more advanced.

TFTC requirements for battles and free missions are the same as XWA requirements, with the only differences being that the battles must require the TFTC mod (can not be playable in base XWA) and that the battle are Battle 20, Mission 100.

Empire at War Battle standards

Empire at War is the latest addition to the Compendium. Rules are still somewhat lax and the TAC Office is still learning the mighty power of such a game. Currently the TAC office is accepting only single Skirmish maps (both Space and Land) with plans to add Galactic Conquests in the future.

All Empire at War maps must meet the following standards:

Every battle must contain this file, with basic information about the battle and its author. It must also contain the disclaimer that is required by LucasArts with ever custom mission (see the bottom of this document). You can find a detailed list of the information expected in a readme file below

Planet.txt

Here you write some information about the planet in which the battle will orbit/be on. this doesn't have to be long, just two paragraphs as it is designed to replace the Alderaan loading screen if we ever figure out how

X.ted mission format.
1 map only
EaW Compatible

The map must be playable on Empire at War without the FoC expansion

Readme files

A readme file for a custom battle or mission for any of the flying platforms should follow the following standard. Readme files that do not follow it may be changed by the TAC Office to meet them.

Readme files must include the following information: name of the battle, name of author and PIN, ID line of author (wihtout medal and IWATS information), flying platform, number of missions, medal name, patch information, a description of the battle and disclaimer. Additionally, you can add extra information such as a plotline, notes, etc. Plot information and such can be provided in plain text, but you may also use other formats such as Word, HTML or .PDF.

You can download a sample file here

Subgroup battles

By default, most missions will be made for the TIE Corps, and as such become TC battles. Sometimes however, your battle may be more fitting in another subgroup. For instance if you have a 7 mission battle in wich the pilot flies only rebel fighters, you might consider making it an Infiltrator Wing (IW) battle. In the past, subgroup battles required the permission of the subgroup commander. This is no longer necessary. The only exceptions are:

• Combined Arms Battles (CAB): These are large battles, usually involving more than one subgroup. These can only be created after prior approval by the Tactical Officer. To get approval, e-mail a detailed plotline with all needed information to the Tactical Officer.
• Fleet Commander's Honor Guard (FCHG): Fleet Commander's Honor Guard battles are selected battles which have won a FCHG mission creation competition. These competitions can be held by the Tactical Office for the Fleet Commander's and Emperor's Hammer'sbirthday. These battles must follow high quality standards and must have a plotline following the general Emperor's Hammer timeline. The Tactical Officer has final say on the selection of these FCHG Battles.

Platform conversions

Platform Conversions battles are created by converting an existing battle on the Mission Compendium to be played on another platform than it was originally designed for. These should only be done by the original creator of the battle, or with the original creators consent, and are generally discouraged because of the problems arising when doing a conversion.

Problems arise because the AI is different, as well as the available craft. briefings almost never convert properly. Any platform conversion MUST be approved by the Tactical Officer before you begin.

Medals

Battle Medals are awarded to pilots who complete EH Battles on the Mission Compendium. The Battle Medal is awarded after the pilot's BSF has been processed. The battle author suggests the name of the Battle Medal that is to be awarded upon completing their battle. New Battle Medal names cannot conflict with existing medal names. The Tactical Officer approves and has final say on new Battle Medal names.

Battle Medals are listed on the Mission Compendium and on a pilot's Combat Profile. Battle Medals are not displayed on uniforms.

LucasArts New Level Rules

LucasArts has devised a set of rules to which all custom battles and missions must adhere. These rules are absolute and no deviation is allowed. When there is doubt whether a EH rule conflicts with a LucasArts rule, the LucasArts rule applies. The LucasArts rules are:

• New Levels must work only with the retail version of the Software, and may not work with any demo or OEM versions of the Software;
• New Levels may not modify COM, EXE, DLL or other executable files (as such, the Emperor's Hammer will not distribute custom .COM, .EXE, or .DLL files bundled with its missions. The Emperor's Hammer does not and will not distribute modified LucasArts .COM, .EXE, or .DLL files, but does distribute patch programs for these files);
• New Levels must not contain any illegal, scandalous, illicit, defamatory, libelous, or objectionable material (as may be determined by LEC in its sole discretion), or any material that infringes any trademarks, copyrights, protected works, publicity, proprietary, or other rights of any third party or of LEC; (as such, the Emperor's Hammer also enforces that all new missions and battles must comply with the Articles of War and Emperor's Hammer Bylaws.)
• New Levels may not include any LEC sound effects or music files or portions thereof;
• New Levels must identify in every description file, on-line description, readme, and in comments in the New Level code:
  • The name, address, and an e-mail address of the level's creators, and
  • The following disclaimer: "THIS LEVEL IS NOT MADE, DISTRIBUTED, OR SUPPORTED BY LUCASARTS ENTERTAINMENT COMPANY, ELEMENTS TM & (C) LUCASARTS ENTERTAINMENT COMPANY.";
  • Despite what this says, you are NOT required or asked to put your real name or home address in custom missions! In fact, we discourage this practice, especially if you're under the age of 18. Only your Emperor's Hammer ID Line and e-mail address to identify you as the creator are required. The disclaimer is required as well.
• New Levels may not be sold, bartered, or distributed with any other product for which any charge is made (other than incidental charges for time spent online), but rather must be distributed free of charge;
• By distributing or permitting the distribution of any New Levels, all creators or owners of any trademark, copyright, or other right, title or interest therein grant to LEC an irrevocable, perpetual, royalty-free, sub licensable right to distribute the New Level by any means (whether now known or hereafter invented) derivative works thereof, and to charge for the distribution of such New Level or derivative work, with no obligation to account to any of the creators or owners of the New Level in any manner.