falcon4:campaign:names
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
falcon4:campaign:names [2007-11-24 11:41] snakeman bit more info |
falcon4:campaign:names [2016-11-01 00:53] (current) snakeman removed obsolete pmctodo. |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Campaign Name Files ====== | ====== Campaign Name Files ====== | ||
| - | Campaign names are the ones that flash in the intel screen and some other places too, also they should appear in TE. Many of the strings are also used throughout in Falcon 4 UI like in setup and so on. All the names seem to be included only in the RV file, where AF and OF only includes some specific rather theater related strings. | + | Campaign names are the ones that flash in the intel screen and some other places too, also they should appear in TE. Many of the strings are also used throughout in Falcon 4 User Interface (UI) like in setup and so on. All the names seem to be included only in the RV file, where AF and OF only includes some specific rather theater related strings. |
| Theater.irc entries over-ride lcktxtrc.irc entries (except on RV). | Theater.irc entries over-ride lcktxtrc.irc entries (except on RV). | ||
| - | The idea was that as new exe features, ui features, aircraft, etc. were implemented, the lcktxtrc.irc file is a continually moving target, necessitating theater's to continually update their own lcktxtrc.irc file to incorporate changes to the one in the master file. | + | The idea was that as new exe features, UI features, aircraft, etc. were implemented, the lcktxtrc.irc file is a continually moving target, necessitating theater's to continually update their own lcktxtrc.irc file to incorporate changes to the one in the master file. |
| In alternate theater, you might want different textual strings for things like "campaign names", "campaign events" and such. | In alternate theater, you might want different textual strings for things like "campaign names", "campaign events" and such. | ||
| Line 11: | Line 11: | ||
| Rather than having to update the entire file for each theater, a smarter move was to create the theater.irc concept that a much smaller "static" sub-set of text strings are needed for the theater, and as such, all entries in the theater.irc file over-ride entries in the lcktxtrc.irc file. The theater.irc concept was introduced in some time between SP1 and SP3. | Rather than having to update the entire file for each theater, a smarter move was to create the theater.irc concept that a much smaller "static" sub-set of text strings are needed for the theater, and as such, all entries in the theater.irc file over-ride entries in the lcktxtrc.irc file. The theater.irc concept was introduced in some time between SP1 and SP3. | ||
| - | These following files are pure text files which you can edit directly from your favourite text editor. | + | These following files are pure text files which you can edit directly from your favorite text editor. |
| **Allied Force** | **Allied Force** | ||
| Line 43: | Line 43: | ||
| | TXT_SCENARIO_ | Campaign selection name | | | TXT_SCENARIO_ | Campaign selection name | | ||
| | TXT_SC_ | Longer description of the campaign situation | | | TXT_SC_ | Longer description of the campaign situation | | ||
| + | |||
| + | See also [[falcon4:ui#campaign_buttons|UI campaign buttons]] | ||
falcon4/campaign/names.1195904510.txt.gz · Last modified: 2007-11-24 11:41 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
