
A playable beta now runs the Unlimited Adventures role-playing system across several Motorola 68k computers, with one shared engine doing the heavy lifting behind the scenes. OpenUA takes a practical approach to retro game development. It doesn’t wrap the original software in an emulator, and it isn’t tied to one specific machine. Instead, it rebuilds the 1993 Unlimited Adventures engine so it can run directly on Atari and Amiga hardware based on the Motorola 68k processor family. That’s a difficult job. Atari and Amiga computers may share similar processors, but almost everything around them works differently. Graphics, sound, memory handling, files and user input all need their own solutions. OpenUA deals with those differences through a shared core engine and separate hardware backends for each platform. The current beta is already playable. You can load adventures, create characters, explore maps, fight battles, cast spells and use the built-in design tools. It’s not just a technical preview that boots to a menu. The main systems are there and working.
One game engine, several graphics systems
OpenUA supports the Atari Falcon030, TT030 and ST or STE, as well as Amiga AGA machines, Amigas fitted with RTG graphics cards and standard ECS or OCS models. That range creates a major graphics challenge.
The engine builds each frame in an eight-bit, 256-colour internal buffer. From there, the platform-specific display code converts the image into whatever format the computer can handle. A Falcon can use a direct high-colour display path, while the TT needs its own planar conversion system.
Older Atari ST and STE machines can only display a much smaller palette, so OpenUA reduces the image to 16 colours. Amiga ECS hardware gets 32. The engine uses a median-cut colour quantiser to choose the most useful colours for each scene, while palette changes across different screen areas help squeeze more detail from the available hardware. AGA and RTG systems have fewer restrictions. They can keep the full 256-colour presentation, which gives them a cleaner result and avoids much of the colour reduction work.
Replacing the Macintosh around the game
OpenUA builds on the Motorola 68k Macintosh version of Forgotten Realms: Unlimited Adventures. That gives the project one useful advantage: the original game code already targets the same processor family used by many Atari and Amiga systems. The processor isn’t the main problem. The operating system is.
The original program depended on Apple’s Macintosh Toolbox for memory management, graphics, windows, files, menus, sound and event handling. None of that exists on Atari TOS or AmigaOS. OpenUA has to recreate the services the engine expects, then connect them to each target machine.
The project splits this work into three layers. The game engine sits at the top. A compatibility layer reproduces the Macintosh functions beneath it. The final platform layer talks to Atari or Amiga hardware.
It’s a sensible structure. Combat code doesn’t need to know how an Amiga bitplane works, and the map editor doesn’t need separate logic for every Atari model. Platform differences stay where they belong.
It’s also a complete creation system
OpenUA does more than launch existing adventures. The engine includes first-person exploration, area maps, event chains, shops, taverns, temples, treasure handling and turn-based combat. Equipment changes armour class and damage, characters gain access to spells, and parties can rest, save and continue their progress. The design tools are included too.
Users can work with maps, events, monsters, records and artwork inside the same system. That matters because Unlimited Adventures was always more than a single role-playing game. It was a construction kit for building new ones. OpenUA also includes conversion tools for DOS-format artwork. These handle walls, portraits, sprites, combat graphics and animations, preparing them for the Macintosh-derived engine.
A working beta, but not a finished product
There are still some limits. OpenUA doesn’t ship with commercial game data. You’ll need files from a legally obtained copy, including a Macintosh resource archive required by the engine. Public builds keep copyrighted assets separate from the project itself.
Hardware testing also remains limited. The current Atari and Amiga versions have mainly been tested in emulators, so real machines may expose timing, performance or compatibility issues. Slower systems, especially an 8 MHz Atari ST, may struggle more than modern emulation suggests.
Even so, OpenUA has already passed the proof-of-concept stage. It runs a large RPG engine across several machines that would normally need completely separate ports. That’s the real achievement. One engine handles the game, while each computer gets a display and hardware layer built for its own strengths and limits.














