Command & Conquer Is Being Ported to the Atari ST

Some retro projects make you smile. Others make you wonder how anyone even thought to try. A developer going by indyjo is bringing Westwood Studios' 1995 real-time strategy classic Command & Conquer to the Atari ST, and this one belongs in the second category.

For anyone who missed that era, the Atari ST is a 16-bit home computer that first appeared in the 1980s. Command & Conquer is a mid-90s PC game built around base building and big army clashes. Putting the two together sounds like a stretch. The early results suggest otherwise.

Sixteen Colours, Still Recognisable

The port is still a work in progress. It is based on the original MS-DOS version, and the biggest hurdle is the visuals. The DOS release ran on 256-colour VGA displays, while the Atari ST can only show 16 colours at once.

That is a brutal cut. Rather than letting the art turn to mush, indyjo has put a lot of care into precise colour reduction. The tanks, infantry and terrain have been reworked into a limited-palette look that stays surprisingly lively. If you have a soft spot for chunky 16-colour pixel art, this might be the strangest and most charming way to revisit a PC favourite.

Same War, Smaller Machine

Under the new paint, the game itself should feel familiar. You still build and fortify a base, harvest Tiberium, and fight your way to the enemy's front door until nothing is left standing.

Both factions made the trip. You can run a campaign as the Global Defense Initiative (GDI), which is backed by the UN, or side with the shadowy Brotherhood of NOD. That covers the whole experience that helped define the RTS genre in the first place.

The project is also open about how it was made. No AI was used to create any artwork. However, AI was used to port the software itself and to build tools for handling the game's assets.

The RAM Problem

This is where things get tricky. Because it is a port of the DOS version, it inherits hardware demands that go well beyond what a typical 1990 Atari STe could manage.

Right now, you need somewhat exotic kit to run it. That means an Atari STe with an acceleration card, an Atari Falcon, or an emulator such as Hatari. The goal is to lower the requirements until the game runs on something like an Atari Mega STe with 4MB of RAM. The project is not there yet, and cutting down memory use is described as the hardest part of the job.

Still, a good chunk of that work is already underway:

• ST16, a new iconset format, stores terrain tiles in the ST's native 16-colour encoding.
• SHPX, a new shape format, splits image meta-information from the pixel data. Only the meta-information stays in RAM, and pixel data is read from disk when needed. That alone frees up almost 2MB.
• A 256kB interpolation table has been removed.
• The terrain tile cache is gone too, made unnecessary by ST16.
• A new C library, libcmini, trims overhead.

The listed system requirements set the minimum at any Atari ST-compatible computer with at least 4MB of RAM. The recommended setup is a 68020 or better running at 32MHz, 4MB or more of RAM, DMA sound and a Blitter. Given the notes above, that minimum looks more like the target than what the current build can do.

Readers commenting on the original IndieRetroNews report were quick to ask for an Amiga version. One pointed out that an Amiga port called Vanilla Conquer already exists, though it needs Vampire or PiStorm upgrades or emulation. Another suggested the HD remaster for anyone who found the original PC resolution too low.

Our Take

This fits a pattern retro fans will recognise: well-known PC games being squeezed onto older machines by dedicated hobbyists. The Amiga mention in the comments shows how much appetite there is for this kind of thing, and how often these ports lean on upgraded hardware or emulation, at least at first.

What stands out here is the honesty about the limits. The project doesn't pretend a stock ST can handle it yet, and the memory work is laid out in plain detail. The open note about AI use is also worth pointing out, as more developers are likely to face questions about where these tools end up in their work.

The thing to watch is whether the RAM savings keep coming. If a 4MB Mega STe really can run it, this goes from a clever demo to something a lot more ST owners can actually play.