Verified project
milestones

A glimpse of a possible future

The player can change asteroid heading and engine power from the reconstructed control view while the map shows the selected asteroid and its movement vector relative to nearby objects.

The same work also corrected the movement timing of ships, fleets and missiles to match the original game. The screen is therefore more than a visual recreation: its controls really affect the game world.

Players testing the 10 September build reported several problems that had escaped the existing replay and regression coverage. The reports were reproduced, fixed and folded into the next public preview rather than remaining as developer-only observations.

That makes the step from 0.478 to 0.495 the first complete public feedback loop for the project: release → external testing → reported problems → verified fixes → next release.

The map engine can now handle worlds far larger than the original game. A smooth camera and extended zoom make those larger areas practical to navigate, while classic-sized maps continue to work as before.

The larger world is an OpenFA extension rather than a replacement for the original map scale: standard-size games remain valid while custom scenarios can spread asteroids, fleets and colonies across far greater distances.

The clearest examples are the Interceptor Missile, which autonomously engages incoming missiles and can also attack asteroids, and the Decoy Missile, which separates into four harmless targets near its destination to saturate missile defences. Both missiles are delivered as optional .ofapkg extensions instead of being hard-wired into the standard game.

Preview 0.478 ships with 12 .ofapkg packages, including the new missiles, rare asteroid types and extra surface information. It is the first public build where OpenFA extensions are clearly visible during ordinary play.

The planning layer puts useful information directly on the asteroid surface: Screen Generator coverage, building footprints and obstacles, power priorities and the exact reason why a selected building cannot currently be placed.

A separate set of overlays shows construction progress and building condition, while ship health can be seen directly in the inventory. Each display can be enabled independently, and turning it off does not affect gameplay or saved games.

We now know how players joined a session, how one machine coordinated the game, how commands reached every participant and how the game tried to recover when synchronization went wrong. The old connection methods used by the DOS release have also been identified.

This does not mean multiplayer is already playable in OpenFA. It does mean the important rules are now known, so a modern multiplayer implementation can be built without guessing how the original behaved.

Preview 0.370 is explicitly published as an unfinished development snapshot. At this point the mechanics exercised by Fragile Allegiance tutorials 1–6 can be tested end to end, while incomplete systems, regressions and differences from the original are still expected.

The preview requires a locally installed legal copy of the original game and uses First-Run.ps1 to select its assets. The source repository remains private for now; feedback and reproducible bug reports are collected through the public preview project.

Buildings, ships, fleets, missiles, ores, research, trade, personnel and scenarios no longer have to be hard-wired into one fixed version of the game. OpenFA can load their definitions from active packages together with the graphics, animations and on-screen information they need.

Packages are not separate programs running inside the game. They use features already provided by the engine and configure them with data. That makes it possible to add new missiles, surface overlays, industry systems and other ideas while keeping the faithful original game as a separate content set.

The lesson covers building requirements, small craft, hardpoints, build orders, Ship Yard status and order cancellation. It then moves to the Orbital Space Dock for larger designs.

The tutorial uses the same screens and rules as normal play. Nothing is created through shortcuts just to make the recording look correct.

The final section covers tactical placement, protected and affected areas, demolition and insufficient-funds feedback.

Original pointer movement, timing, subtitles and narration are retained. Every building action still uses the same gameplay rules as normal play.

It opens the catalogue, selects a building and returns to the surface. The building is then placed exactly as it would be during normal play, including space, money and construction-time requirements.

The lesson starts on the strategic map, opens the highlighted asteroid and explains the five funds. Budget changes use the recovered left and right drag controls.

Pointer movement, subtitle text and narration timing come directly from the original tutorial data.

OpenFA reads asteroids, factions, buildings, ships, personnel and diplomacy from original saved games. Parts that are not yet understood are preserved so nothing is lost. The colonies shown here therefore come from real saves rather than hand-made demo data.

The asteroid surface, buildable areas and strategic map all use the same world data. What the player sees and clicks therefore matches the reconstructed game state.

Screenshots show how the game should look. The program, its data and saved games help explain why it behaves the way it does.

OpenFA does not redistribute the original graphics, sounds or videos. They are loaded from a legally installed copy of Fragile Allegiance selected by the player.

Even at this early stage, game content is being separated from the engine itself. That idea later grows into the .ofapkg format now used for mods and optional extensions.

AI helps navigate the decompilation. Tests replay asset, save and simulation cases; generated explanations remain hypotheses.