Platform: Commodore 64
Region: Region Not Set
Publishers(s): Hesware
ReleaseDate: 1985-02-25
Co-op: No
Project Space Station
In the game the player is put in control of NASA and tasked with building and maintaining a space station and generating enough money with commercial contracts to make up for an anemic yearly budget. This can be seen as a discrete set of phases, except that they all proceed simultaneously. The exception is at the beginning of the game where the player has unlimited time in the planning phase before the game clock starts. In the planning phase, the player first allocates the funds they have to various budget items, like crew selection, station modules, and research and development. Then they choose their crew, who have intrinsic task sets (like piloting and physics), and varying levels of competence and compatibility with other potential employees. From there the player purchases equipment like space suits and satellites, and station modules like laboratories and solar arrays. Then they schedule their launches using the two space shuttles available (Atlantis and Discovery, though the initial release used Challenger), and have their budget approved. In the final stage of the planning phase the player can create a simulated station with an unlimited number of parts, and without dealing with the later constrictions of the EVA. The launch phase has the player decide whether launch conditions are stable enough to merit launch. If they give the implicit go-ahead, they engage in a light arcade sequence where the player attempts to keep the shuttle on course throughout its orbital burn. The more successful the player is, the closer the shuttle will be to the station. Once the shuttle is in orbit, the player is tasked to assemble the components they brought up (or to fire off any satellites they have contracts for) in the Extra-Vehicular Activity, or EVA phase. Here the player directly controls an Orbital Construction Pod, a small ship with mechanical arms that an astronaut can use to move large equipment. Being careless here could have consequences as the pod or equipment may become damaged, and it may run out of fuel and become stranded until another pod can rescue it. Consequences were not limited to equipment damage: Stranded astronauts in pods could die when oxygen ran out. Other crew hazards included solar flares, which could kill astronauts on the station or shuttle if precautions (using an emergency module in station design) were not taken. Crew died in reverse alphabetical order from solar flares. The player then transfers crew to and from the space station and assigns them to research tasks. Completing these tasks awards the player with government contracts that supplement NASA's budget. A math bug (or intentional cheat) in the game allowed an infinite supply of money, if the player allocated more than $10,000K to any budget. For example, if $800k is spent, the budget would be recalculated to $19,200K instead of $9,200, as expected. Finally the player lands the shuttle. After determining that landing conditions are adequate, the player again keeps the shuttle on course as it turns from the station and enters its descent. Skill here determines how close the shuttle will be to the optimal point from the runway. After this the player controls the shuttle with a simple landing simulator viewed from the side. The more abrupt or overshot the landing, the more damage will be done to the shuttle and the longer it will need to be repaired before it can venture out on another mission. The game is played using a menu system. Every option can be queried for in-game help, and every major task has a tutorial that simulates that task without the consequences of failure, and sometimes with additional assistance (like being able to pause a landing attempt). Another major feature is the message system that alerts the player when there are changes to mission status, wherever the player might be within the menu system.