error-message
success-message
saving-message
warning-message
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
This is a snapshot of this object as it looked in the past. | Go to the most recent version
DOS Real-Time Strategy game from SUNGJIN Multi-Media from 1998.
Microforum International
1998
Armored Moon is a real-time strategy (RTS) that combines many elements from its popular predecessors, first and foremost Westwood Studios' classics Dune II: The Building of a Dynasty and Command & Conquer. The core gameplay mechanics are largely similar: you build up a base, pump out units and set off to destroy all hostile presence, fending off waves of enemy attacks from time to time. Presented in isometric perspective, which was becoming trendy in the year of its release, Armored Moon takes place, well, on the moon, which is apparently colonised by humans but an armed conflict breaks out. The palette uses bleak colours, giving the landscapes an appropriately eerie sci-fi look. The game simplifies resource gathering by introducing towns that continuously generate income. Towns may be captured by engineer-like units (cyborgs), and each is surrounded by a limited area of concrete where other structures may be build. Out of these, the most important is the teleporter that brings in new units for your army that appear almost instantly but cannot be ordered in unlimited quantities. Furthermore, units gain experience and level up as they participate in combat, so keeping them alive is very much in the player's interest. Special supplier units will take care of repairing damage. Otherwise, combat is fairly typical of Command & Conquer clones and inevitably boils down to the simple rule that the more numerous your force, the better chances to win. The playable demo of Armored Moon includes one mission, with ten missions in the full game.
Description by MrFlibble
This section tracks other objects or external resources.
The external resources, such as tarballs or Git repositories, are then available as part of the object. Their files can be considered local to the object and usable in scripts or as part of a build process.
For resources that are only to be used as part of the build or runtime of the object, it is best to describe those local to those sections.
This section tracks information useful to describing how to run this object.
AMDEMO.BAT
dos
x86
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
Confirm message?