Difference between revisions of "MISSIONS.DAT"
(→Timetable of a mission: off-by-one fixed) |
|||
(29 intermediate revisions by 7 users not shown) | |||
Line 11: | Line 11: | ||
6 alien race of mission | 6 alien race of mission | ||
− | The | + | The race number can be looked up in [[ENGLISH.DAT]] / [[ENGLISH.DAT (TFTD)|(TFTD)]], entries 466-476: |
− | + | EU TFTD | |
− | + | 0 Sectoid Aquatoid | |
− | + | 1 Snakeman Gill Man | |
− | + | 2 Ethereal Lobster Man | |
− | + | 3 Muton Tasoth | |
+ | 4 Floater Calcinite | ||
+ | 5 Celatid Deep One | ||
+ | 6 Silacoid Bio-Drone | ||
+ | 7 Chryssalid Tentaculat | ||
+ | 8 Reaper Triscene | ||
+ | 9 Sectopod Hallucinoid | ||
+ | 10 Cyberdisc Xarquid | ||
==Timetable of a mission== | ==Timetable of a mission== | ||
Line 24: | Line 31: | ||
===Note on the timing=== | ===Note on the timing=== | ||
− | + | Battlescape missions do not affect the scheduling of future UFOs. | |
+ | |||
+ | UFO appearances are established with a base time period to which a random amount of time derived from the base time is added. The effect is that a UFO arrival will be scheduled 50-150% of the base time. When the mission is created, the first UFO in the mission is spawned when the timer reaches zero. Then the mission entry details are set for the next the next UFO in line and the timer begins counting down again. | ||
− | + | Shooting down a UFO will immediately add 24~224 hours (1~9 days) to the timer for the next UFO in that mission. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
A time followed by * denotes an exact non-randomized time of arrival. | A time followed by * denotes an exact non-randomized time of arrival. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===Research=== | ===Research=== | ||
− | |||
− | |||
ufo-c time-c ufo-type | ufo-c time-c ufo-type | ||
− | 0/0 | + | 0/0 ?h s.Scout <i>(start of game Research mission is 2.5h*. This is for later ones)</i> |
− | 1/0 | + | 1/0 150h m.Scout |
− | 2/0 | + | 2/0 130h l.Scout |
− | 2/1 | + | 2/1 150h l.Scout |
===Harvest=== | ===Harvest=== | ||
ufo-c time-c ufo-type | ufo-c time-c ufo-type | ||
− | 0/0 | + | 0/0 ?h s.Scout |
− | 1/0 | + | 1/0 130h s.Scout |
− | 2/0 | + | 2/0 130h m.Scout |
− | 3/0 | + | 3/0 100h l.Scout |
− | 4/0 | + | 4/0 130h l.Scout |
− | 5/0 | + | 5/0 150h Harvester |
− | 6/0 | + | 6/0 50h Harvester |
− | 7/0 | + | 7/0 12.5h Battleship |
− | |||
− | |||
===Abduction=== | ===Abduction=== | ||
ufo-c time-c ufo-type | ufo-c time-c ufo-type | ||
− | 0/0 | + | 0/0 ?h s.Scout |
− | 1/0 | + | 1/0 250h m.Scout |
− | 2/0 | + | 2/0 300h l.Scout |
− | 3/0 | + | 3/0 150h Abductor |
− | 4/0 | + | 4/0 150h Abductor |
− | 4/1 | + | 4/1 1h Abductor |
===Infiltration=== | ===Infiltration=== | ||
ufo-c time-c ufo-type | ufo-c time-c ufo-type | ||
− | 0 | + | 0/0 ?h s.Scout |
− | 1 | + | 1/0 275h m.Scout |
− | 2 | + | 2/0 250h m.Scout |
− | 3 | + | 3/0 230h l.Scout |
− | 4 | + | 4/0 150h l.Scout |
− | 5 1h Terrorship | + | 5/0 1h Terrorship |
− | 6 | + | 6/0 1h Supply |
− | 7 1h | + | 7/0 1h Battleship |
− | + | 7/1 1h Battleship | |
− | |||
− | |||
− | |||
===Base=== | ===Base=== | ||
ufo-c time-c ufo-type | ufo-c time-c ufo-type | ||
− | 0/0 | + | 0/0 ?h s.Scout |
− | 1/0 | + | 1/0 225h m.Scout |
− | 2/0 | + | 2/0 250h l.Scout |
− | 3/0 | + | 3/0 1h Supply |
− | 3/1 | + | 3/1 1h Supply |
− | 4/0 | + | 4/0 1h Battleship |
− | |||
− | |||
− | |||
===Terror=== | ===Terror=== | ||
− | ufo-c time-c ufo-type | + | ufo-c time-c ufo-type |
− | 0 2.5h* m.Scout | + | 0 2.5h* m.Scout |
− | 1 | + | 1 250h l.Scout |
− | 2 | + | 2 160h Terrorship |
− | 3 | + | 3 200h Terrorship |
− | Landing sites of Terrorships are terror missions, not ground assault missions. Your radars don't want to track a Terrorship after it drops off its cargo. | + | Landing sites of Terrorships are terror missions, not ground assault missions. Your radars don't want to track a Terrorship after it drops off its cargo. |
sub-ufo-c is empirically always 0 for Terror acts. | sub-ufo-c is empirically always 0 for Terror acts. | ||
Line 116: | Line 101: | ||
===Retaliation=== | ===Retaliation=== | ||
ufo-c time-c ufo-type | ufo-c time-c ufo-type | ||
− | 0/0 50h | + | 0/0 50h s.Scout |
− | 1/0 | + | 1/0 50h m.Scout |
− | 1/1 | + | 1/1 50h* m.Scout (<i>add 146.5h* if 1/0 shot down at first turning point</i>) |
− | 2/0 | + | 2/0 50h* l.Scout (<i>add 3d if 1/1 shot down at first turning point</i>) |
− | 2/1 | + | 2/1 50h l.Scout |
− | 2/2 | + | 2/2 50h l.Scout (<i>Not always...finally confirmed it could happen, no idea what factors control this one's existence.</i>) |
− | 3/0 | + | 3/0 50h Battleship |
− | 3/1 | + | 3/1 50h Battleship |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | This mission only relates to the aliens attempting to find an unknown XCOM base in a zone. Once the location of a base is known to the aliens, a special routine in the daily activities section generates the battleship that will attack the base. | |
− | + | A retaliation mission is possibly generated after a successful interception. The zone the mission is set will be either the location of the interception or the zone of the base from which the interceptor was launched. The random chance of a mission being generated and the chance of which zone is selected is affected by the difficulty level of the game. | |
− | + | After a certain point in research or after about 9 months of game time, retaliation missions are automatically generated for each zone that contains an XCOM base at the beginning of each game month. | |
==See Also== | ==See Also== | ||
Line 144: | Line 123: | ||
* [[Game Files]] | * [[Game Files]] | ||
[[Category:Game Files]] | [[Category:Game Files]] | ||
+ | [[Category:Enemy Unknown/UFO Defense]] |
Latest revision as of 06:52, 31 August 2019
contains counters and race info on the ongoing acts. At the start of the game (beginner level) research in your home zone and terror in a random zone is initiated. After that each new month you will get two new missions, one of which is a terror mission (beginner level).
Structure of a mission entry
Each mission has 4 words. With 7 acts on 12 zones these are 672 bytes. E.g. infiltration(3) in Europe(4) would have the offset 3*8+4*(7*8)=0xF8.
offset meaning 0 ufo-counter on the ufos within the mission (FFFF, the mission is not active) 2 sub-ufo-counter used for some missions 4 time-counter, 30 minutes to next ufo 6 alien race of mission
The race number can be looked up in ENGLISH.DAT / (TFTD), entries 466-476:
EU TFTD 0 Sectoid Aquatoid 1 Snakeman Gill Man 2 Ethereal Lobster Man 3 Muton Tasoth 4 Floater Calcinite 5 Celatid Deep One 6 Silacoid Bio-Drone 7 Chryssalid Tentaculat 8 Reaper Triscene 9 Sectopod Hallucinoid 10 Cyberdisc Xarquid
Timetable of a mission
When a mission starts, the ufo-counter is set to 0 and the time-counter to some act-depending time. The time-count is reduced every 30 minutes. When 0, an ufo will appear, the ufo-counter (or the sub-counter on some mission) will be increased and a new random time-counter for the new ufo will be set.
Note on the timing
Battlescape missions do not affect the scheduling of future UFOs.
UFO appearances are established with a base time period to which a random amount of time derived from the base time is added. The effect is that a UFO arrival will be scheduled 50-150% of the base time. When the mission is created, the first UFO in the mission is spawned when the timer reaches zero. Then the mission entry details are set for the next the next UFO in line and the timer begins counting down again.
Shooting down a UFO will immediately add 24~224 hours (1~9 days) to the timer for the next UFO in that mission.
A time followed by * denotes an exact non-randomized time of arrival.
Research
ufo-c time-c ufo-type 0/0 ?h s.Scout (start of game Research mission is 2.5h*. This is for later ones) 1/0 150h m.Scout 2/0 130h l.Scout 2/1 150h l.Scout
Harvest
ufo-c time-c ufo-type 0/0 ?h s.Scout 1/0 130h s.Scout 2/0 130h m.Scout 3/0 100h l.Scout 4/0 130h l.Scout 5/0 150h Harvester 6/0 50h Harvester 7/0 12.5h Battleship
Abduction
ufo-c time-c ufo-type 0/0 ?h s.Scout 1/0 250h m.Scout 2/0 300h l.Scout 3/0 150h Abductor 4/0 150h Abductor 4/1 1h Abductor
Infiltration
ufo-c time-c ufo-type 0/0 ?h s.Scout 1/0 275h m.Scout 2/0 250h m.Scout 3/0 230h l.Scout 4/0 150h l.Scout 5/0 1h Terrorship 6/0 1h Supply 7/0 1h Battleship 7/1 1h Battleship
Base
ufo-c time-c ufo-type 0/0 ?h s.Scout 1/0 225h m.Scout 2/0 250h l.Scout 3/0 1h Supply 3/1 1h Supply 4/0 1h Battleship
Terror
ufo-c time-c ufo-type 0 2.5h* m.Scout 1 250h l.Scout 2 160h Terrorship 3 200h Terrorship
Landing sites of Terrorships are terror missions, not ground assault missions. Your radars don't want to track a Terrorship after it drops off its cargo.
sub-ufo-c is empirically always 0 for Terror acts.
Retaliation
ufo-c time-c ufo-type 0/0 50h s.Scout 1/0 50h m.Scout 1/1 50h* m.Scout (add 146.5h* if 1/0 shot down at first turning point) 2/0 50h* l.Scout (add 3d if 1/1 shot down at first turning point) 2/1 50h l.Scout 2/2 50h l.Scout (Not always...finally confirmed it could happen, no idea what factors control this one's existence.) 3/0 50h Battleship 3/1 50h Battleship
This mission only relates to the aliens attempting to find an unknown XCOM base in a zone. Once the location of a base is known to the aliens, a special routine in the daily activities section generates the battleship that will attack the base.
A retaliation mission is possibly generated after a successful interception. The zone the mission is set will be either the location of the interception or the zone of the base from which the interceptor was launched. The random chance of a mission being generated and the chance of which zone is selected is affected by the difficulty level of the game.
After a certain point in research or after about 9 months of game time, retaliation missions are automatically generated for each zone that contains an XCOM base at the beginning of each game month.
See Also
- ACTS.DAT - Contains actions the Aliens will embark on
- ALIEN.DAT - Contains alien activity for graphs
- ZONAL.DAT - Contains priorities for alien activities
- UFO Flight Patterns
- Game Files