MISSION CONTROL is an interactive fiction game in which you play FLIGHT, the flight director on console at NASA Mission Control in Houston during the launch of a fictional crewed lunar mission. The vehicle is the BURROUGHS stack, fully fuelled and on the pad in Florida; an astronaut sits in the command capsule at the top. Your job is to weigh the calls of four other officers around you and decide whether the count is COMMIT, HOLD or SCRUB.
The game uses standard interactive fiction commands -- "look" to see your surroundings, "examine [object]" to look closer, "north" / "south" / "east" / "west" (or "n" / "s" / "e" / "w") to move between rooms. "inventory" (or "i") lists what you're carrying. "save" and "restore" work as you'd expect.
Game-specific commands you'll need:
* "controllers" (or "crew") -- a summary of the four officers in the room and what each console does. Read this first if the acronyms (FIDO, EECOM, GUIDANCE, RETRO, CAPCOM) aren't familiar.
* "examine [controller]" -- key the loop on that console and hear their current read. Reads change with the situation.
* "ask [controller] about [topic]" -- ask for their take on a specific subject. Topics: "role", "wind", "leak", "steering", "tower". Different controllers have different perspectives on the same topic.
* "tell [controller] about [topic]" -- relay information you have learned to a controller. They may revise their advice.
* "poll" -- run the GO/NO-GO round-robin and commit the count. The clock does not start ticking until you do.
* "commit", "hold", "abort" (or "c", "h", "a") -- decision verbs available when an alarm forces a call.
The status panel above the text is your real-time telemetry. You don't need to memorise every value; the relevant ones are discussed in dialogue when they matter.
Type "controllers" now if the acronyms are unfamiliar.
The game uses standard interactive fiction commands -- "look" to see your surroundings, "examine [object]" to look closer, "north" / "south" / "east" / "west" (or "n" / "s" / "e" / "w") to move between rooms. "inventory" (or "i") lists what you're carrying. "save" and "restore" work as you'd expect.
Game-specific commands you'll need:
* "controllers" (or "crew") -- a summary of the four officers in the room and what each console does. Read this first if the acronyms (FIDO, EECOM, GUIDANCE, RETRO, CAPCOM) aren't familiar.
* "examine [controller]" -- key the loop on that console and hear their current read. Reads change with the situation.
* "ask [controller] about [topic]" -- ask for their take on a specific subject. Topics: "role", "wind", "leak", "steering", "tower". Different controllers have different perspectives on the same topic.
* "tell [controller] about [topic]" -- relay information you have learned to a controller. They may revise their advice.
* "poll" -- run the GO/NO-GO round-robin and commit the count. The clock does not start ticking until you do.
* "commit", "hold", "abort" (or "c", "h", "a") -- decision verbs available when an alarm forces a call.
The status panel above the text is your real-time telemetry. You don't need to memorise every value; the relevant ones are discussed in dialogue when they matter.
Type "controllers" now if the acronyms are unfamiliar.