|
|||||||
|
|
|
|||||
|
|
|||||||
| Main | Tactical Office | Installing Custom Battles | Battle Submission Forms |
| Mission Bugs | Utilities | New Battles and Free Missions | Battle Standards |
| Plotlines | Lucasarts New Levels Rules | IDSF Cheating Policy |
The following are the strict standards that all TIE Fighter Battles/Missions should meet before they are submitted to the Tactical Office.
All battles must include a .TXT detailing the plotline etc. For more information see the section detailing the plotline standards
All battles must be at least 4 missions long but not exceeding 8. Missions can only have 1 Mission. If you have created a campaign over several battles it must be submitted as one battle.
Again each battle must include its own .LFD File. Any battle without this will be rejected.
All battles are to include some Briefing Officer text. You can have as much or as little as you feel. You must also have Briefing Text for when a mission has been failed. Please note that if using one of the original missions as your template you are forbidden to use the original text. It must be replaced with your own.
All missions must have at least some Radio Messages. The minimum requirement for these is for Primary and Secondary Mission Accomplished/Failure
The
mission map doesn’t have to be animated but it has to shown something relevant
to the mission that it is for. It should not crash the game when viewed or
contain any of the original briefing text.
This will crash any version of TIE Fighter other than the Diskette version. It is also completely useless in any version of TIE Fighter.
Please remember that TIE 95 is the base platform. They must all at least work with this version of the platform.
The following are the strict standards that all TIE Fighter Battles/Missions should meet before they are submitted to the Tactical Office.
All battles must include a .TXT detailing the plotline etc. For more information see the section detailing the plotline standards
All battles must be at least 4 missions long but not exceeding 14. Missions can only have 1 Mission. If you have created a campaign over several battles it must be submitted as one battle.
Again each battle must include its own .LST File. These can be Imperial.LST, Rebel.LST or Mission.LST
Imperial.LST
is for Imperial Craft Missions
Rebel.LST
is for Rebel Craft Missions
Mission.LST is for multiplayer missions and must be linked with either Imperial.LST or Rebel.LST
Every Mission must contain some text that is viewable when the mission is chosen on the Mission Selection Screen. You can include as little or as much as you see fit.
All missions must have at least some Radio Messages. The minimum requirement for these is for Primary and Secondary Mission Accomplished/Failure
The
mission map doesn’t have to be animated but it has to shown something relevant
to the mission that it is for. It should not crash the game when viewed or
contain any of the original briefing text.
These are the labels that are displayed next to a mission goal to indicate whether they have been completed, failed or have remained unresolved. Any mission without this may be displayed in a strange fashion
Please remember if you do include any of these that sounds files can take up a large amount of Hard Disk space. For this reason they should be recorded or converted to be a sample rate of 11,205Khz, 8-Bit, Mono at the most.
X-Wing VS TIE Fighter battles must not require the Balance of Power add-on to play. If they do they will be classified as a Balance of Power Battle. Please see the next section for the standards of Balance of Power Battles.
All battles must include a .TXT detailing the plotline etc. For more information see the section detailing the plotline standards
All battles must be at least 4 missions long but not exceeding 14. Missions can only have 1 Mission. If you have created a campaign over several battles it must be submitted as one battle.
Again each battle must include its own .LST File. These can be Imperial.LST, Rebel.LST or Mission.LST
Imperial.LST
is for Imperial Craft Missions
Rebel.LST
is for Rebel Craft Missions
Mission.LST is for multiplayer missions and must be linked with either Imperial.LST or Rebel.LST
Every Mission must contain some text that is viewable when the mission is chosen on the Mission Selection Screen. You can include as little or as much as you see fit.
All missions must have at least some Radio Messages. The minimum requirement for these is for Primary and Secondary Mission Accomplished/Failure
The
mission map doesn’t have to be animated but it has to shown something relevant
to the mission that it is for. It should not crash the game when viewed or
contain any of the original briefing text.
These are the labels that are displayed next to a mission goal to indicate whether they have been completed, failed or have remained unresolved. Any mission without this may be displayed in a strange fashion
Please remember if you do include any of these that sounds files can take up a large amount of Hard Disk space. For this reason they should be recorded or converted to be a sample rate of 11,205Khz, 8-Bit, Mono at the most.
Balance
of Power battles must be playable without the Balance of Power add-on for X-Wing
Vs TIE Fighter. If it doesn’t then it will be classified as a X-Wing Vs TIE
Fighter battle. It must also use some of the structures and Star-Fighters that
are used within the Balance of Power add-on.
All battles must include a .TXT detailing the plotline etc. For more information see the section detailing the plotline standards
All battles must be at least 4 missions long but not exceeding 20. Missions can only have 1 Mission. If you have created a campaign over several battles it must be submitted as one battle.
All mission files must follow the format indicated above. When naming you mission files you must replace the # with the number of the mission, the x can be replaced with any amount of characters you wish for example
1B8M1EmpireStrikesBack.
Again each battle must include its own Mission.LST File. Without this the custom battle will be unplayable.
Every Mission must contain some mission briefing and debriefing text that is relevant to the mission flown. No original text may be used.
All missions must have at least some Radio Messages. The minimum requirement for these is for Primary and Secondary Mission Accomplished/Failure
The
mission map doesn’t have to be animated but it has to shown something relevant
to the mission that it is for. It should not crash the game when viewed or
contain any of the original briefing text.
These are the labels that are displayed next to a mission goal to indicate whether they have been completed, failed or have remained unresolved. Any mission without this may be displayed in a strange fashion
Please remember if you do include any of these that sounds files can take up a large amount of Hard Disk space. For this reason they should be recorded or converted to be a sample rate of 11,205Khz, 8-Bit, Mono at the most.
All
battles/missions must include a blank pilot file to enable others to fly what
you spent many hours creating. To create a fresh pilot file you must start the
game and select the pilot options from the X-Wing Alliance Launcher. Next you
should select Create New Player and call the pilot the same name of the battle
that you have created. If it doesn’t fit you should shorten the name but
remember to still make it similar you your Battle name. Next click done then
exit.
You
will now need to use XWA pilot editor as detailed under Utilities section. This
is to edit the pilot file so it will work with the game. You will need to ensure
that the current mission is selected as [Reserved 1] or [Extra Mission 1].