Difference between revisions of "Terrorist"
(Wow this page sucked...) |
|||
| Line 1: | Line 1: | ||
| − | + | A potential [[disaster]] that may be initiated by the [[simulators]] is a '''terrorist''' attack on either the [[Hab]] or [[Mission Control]]. This disaster is usually chosen in order to bring a [[Mission]] to a quick end. | |
| − | + | ==Best Practices== | |
| + | The terrorist attack disaster usually involves various imitation firearms, such as nerf or cap guns. | ||
| + | |||
| + | ==Restrictions== | ||
| + | This disaster is restricted to [[Training Missions]] and [[Revenge Missions]] and should not be used during the Main [[Mission]]. In addition, Training Missions should focus more on [[Mutiny and Hijacking Procedures|Hijacking]] rather than on terrorist attacks. | ||
==Terrorist Mission History== | ==Terrorist Mission History== | ||
| Line 7: | Line 11: | ||
The first terrorist mission was the [[revenge mission]] of the [[2005-06]] year. [[Stefan De Young]] took command of the Simulators for that mission. Crewing the mission were the simulators from that year's mission to [[Titan]]. | The first terrorist mission was the [[revenge mission]] of the [[2005-06]] year. [[Stefan De Young]] took command of the Simulators for that mission. Crewing the mission were the simulators from that year's mission to [[Titan]]. | ||
| − | The premise of the mission was that a terrorist group, perhaps affiliated with the Soviet Union, had established a military base and mining operation on | + | The premise of the mission was that a terrorist group, perhaps affiliated with the Soviet Union, had established a military base and mining operation on [[Ceres]]. Unfortunately, due to lack of piloting ability, the crew was unable to land until [[Alpha]] time constraints forced the mission to end. |
| + | |||
| + | The only real terrorist activity carried out during the mission was the clandestine infiltration of [[Mission Control]]. The simulators hoped to give [[Mission Control]] a bit more excitement than they had experienced during [[Prometheus]]. | ||
===Latest Mission=== | ===Latest Mission=== | ||
| Line 13: | Line 19: | ||
==See Also== | ==See Also== | ||
| − | [[Mutiny and Hijacking Procedures]] | + | * [[Mutiny and Hijacking Procedures]] |
Revision as of 13:10, 2 March 2010
A potential disaster that may be initiated by the simulators is a terrorist attack on either the Hab or Mission Control. This disaster is usually chosen in order to bring a Mission to a quick end.
Contents
Best Practices
The terrorist attack disaster usually involves various imitation firearms, such as nerf or cap guns.
Restrictions
This disaster is restricted to Training Missions and Revenge Missions and should not be used during the Main Mission. In addition, Training Missions should focus more on Hijacking rather than on terrorist attacks.
Terrorist Mission History
First Mission=
The first terrorist mission was the revenge mission of the 2005-06 year. Stefan De Young took command of the Simulators for that mission. Crewing the mission were the simulators from that year's mission to Titan.
The premise of the mission was that a terrorist group, perhaps affiliated with the Soviet Union, had established a military base and mining operation on Ceres. Unfortunately, due to lack of piloting ability, the crew was unable to land until Alpha time constraints forced the mission to end.
The only real terrorist activity carried out during the mission was the clandestine infiltration of Mission Control. The simulators hoped to give Mission Control a bit more excitement than they had experienced during Prometheus.
Latest Mission
The latest terrorist mission was Training Mission Beta of the 2006-07 year.
