ofp:missions:campaign_design
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
ofp:missions:campaign_design [2007-07-13 03:05] snakeman added data |
ofp:missions:campaign_design [2011-08-15 09:25] snakeman added note about dtaext and global scripts. |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| **Campaign description.ext** | **Campaign description.ext** | ||
| - | When you have decided what sort of campaign you want to have, you must make absolute sure that the campaign description.ext (not the mission!) works perfectly, this can be easily tested with the //endmission// cheat. Just start your campaign and after the briefing when you are ingame, hit endmission cheat and you get to see next mission, or you end up with error that your description.ext is broken. It is essential that this campaign backbone is working before you release your campaign. | + | When you have decided what sort of campaign you want to have, you must make absolute sure that the campaign description.ext (not the mission!) works perfectly, this can be easily tested with the //endmission// cheat. Just start your campaign and after the briefing when you are in-game, hit endmission cheat and you get to see next mission, or you end up with error that your description.ext is broken. It is essential that this campaign backbone is working before you release your campaign. |
| **Triggers** | **Triggers** | ||
| Line 29: | Line 29: | ||
| **Music** | **Music** | ||
| - | Put all music files into the campaign root under its description.ext so they are available on all missions, this way you can have many tracks on all missions with only one sound file download per track. It is stupid to duplicate same music track for two or more missions on their individual mission\music\ dirs. | + | Put all music files into the campaign root under its description.ext so they are available on all missions, this way you can have many tracks on all missions with only one sound file download per track. It is stupid to duplicate same music track for two or more missions on their individual mission\music\ dirs. For more details please read [[ofp:missions:dtaext|DtaExt in campaigns]]. |
| + | |||
| + | **Scripts** | ||
| + | |||
| + | Put all your scripts into campaign root under "Scripts" directory, this way any scripts used in multiple missions, can be read from one dir instead of copying them on each mission dir. | ||
| ====== Design Document ====== | ====== Design Document ====== | ||
| Line 38: | Line 43: | ||
| Another way is to not even touch mission editor, but open a text file and map of the island terrain(s), then start to plan how you want to missions to proceed by looking interesting places on the map or just to see that you cover each city or landmark. You then proceed to write the mission names, dates, times and small descriptions into the text file. Also recently on the **PMC Joint Justice** campaign I wrote the normal text file, but also made 1 jpg image out of each mission showing illustration in the island map of where the units are starting, attacking, defending and where the objectives are etc. It became so easy to afterwards start to build the missions in mission editor, as the complete manuscript / design document was already done. In programming circles its been said that you have to design the program first, then the coding itself goes without a problems. I'd say same applies to campaign creation. | Another way is to not even touch mission editor, but open a text file and map of the island terrain(s), then start to plan how you want to missions to proceed by looking interesting places on the map or just to see that you cover each city or landmark. You then proceed to write the mission names, dates, times and small descriptions into the text file. Also recently on the **PMC Joint Justice** campaign I wrote the normal text file, but also made 1 jpg image out of each mission showing illustration in the island map of where the units are starting, attacking, defending and where the objectives are etc. It became so easy to afterwards start to build the missions in mission editor, as the complete manuscript / design document was already done. In programming circles its been said that you have to design the program first, then the coding itself goes without a problems. I'd say same applies to campaign creation. | ||
| + | |||
| ====== What you should know ====== | ====== What you should know ====== | ||
| Line 45: | Line 51: | ||
| * Make use of root\Scripts\ directory for all your scripts | * Make use of root\Scripts\ directory for all your scripts | ||
| - | ====== Notes ====== | ||
| - | |||
| - | This text is work in progress, more to come, stay tuned... | ||
ofp/missions/campaign_design.txt · Last modified: 2017-10-13 20:07 by snakeman
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
