v0.1.13 - Windows fullscreen and save export

v0.1.13 - Windows Fullscreen And Save Export

Downloads

• SacredStonesRecomp-0.1.13-win64.zip: extract and run the executable at the
  archive root. Keep its DLLs, assets and tools folders together.
• SacredStonesRecomp-0.1.13-android-arm64.apk: Android 9+ and ARM64.
• The corresponding .sha256 assets contain download checksums.

The source-code archives are not playable packages. Neither package includes
the ROM or GBA BIOS; provide your own legally obtained USA ROM and BIOS.

Windows

• Remember fullscreen across restarts, whether changed in the launcher,
  Escape > Display > Fullscreen, or using Alt+Enter.
• Borderless fullscreen is recommended. Windowed and exclusive modes remain
  available; an explicit command-line fullscreen mode overrides startup preferences.
• Preserve the original 3:2 aspect ratio. Side bands on wider displays are normal.
• Exclusive fullscreen explicitly uses the desktop resolution and refresh rate,
  avoiding extra margins from a lower-resolution display mode.
• The executable, launcher and game use the same Eirika icon as Android.
• Add Assist Tools > Export saves, with a native ZIP destination picker.
  Flush the current battery save before exporting and pause gameplay during export.
• Export the battery save, existing state slots 1-9, any suspend snapshot and
  backup manifest, never the ROM, BIOS or settings. Original saves remain intact.
• Use Windows' built-in PowerShell export helper, included under tools/.
  Failed exports preserve an existing destination archive.
• Temporarily switch exclusive fullscreen to windowed for the native picker
  and confirmation, then restore exclusive mode even when export is cancelled.

Android

The release number is aligned with Windows. Android retains the gameplay,
display fitting, modern Back handling and export features validated in 0.1.12.
Its engine and launcher dependencies remain independently pinned; this is not
a Windows runtime migration. The existing production signing key is retained.

Updating

Close the game before updating. On Windows, extract over the existing installation
and retain your saves and settings. On Android, install over the existing app;
do not uninstall or clear its data. Back up saves first and keep the ZIP separately.

Archive import is not implemented. Save-state compatibility across platforms or
runtime versions is not guaranteed. Full-game testing remains incomplete.

Validation

• Regenerated Windows game/BIOS code with the recorded runtime revision;
  generation provenance matches dependency sources and inputs.
• Sixteen isolated runtime scenarios pass, including SRAM reload, save paths,
  locked-save recovery, input, diagnostics, preferences, remembered borderless
  fullscreen, explicit windowed overrides and native-resolution exclusive mode.
• Save-file, launcher-policy and runtime-control test programs pass.
• Windows PowerShell 5.1 export tests cover exact content, unchanged originals,
  state-only archives, slot 9, suspend snapshots, invalid/empty storage and locked ZIPs.
• Package inspection verifies the executable at the ZIP root, current export
  helper and exclusion of private game files and player data.
• Windows resource tests verify that the embedded icon matches the Android PNG
  byte for byte and loads at 16, 32 and 256 pixels.
• Native dialog transition tests cover windowed, borderless and exclusive modes,
  restoration after cancellation and an owner window that is not minimized.
• Android production signature verified; all ARM64 native libraries match 0.1.12.

The maintainer confirmed both fullscreen image sizes and successful save export
in exclusive fullscreen. Cancellation/restoration is covered by the automated
transition test; a separate manual cancellation test has not been reported.
This is not exhaustive start-to-finish gameplay coverage.

v0.1.12 - Android save export and display fixes

v0.1.12 - Android Save Export And Display Fixes

Download

Install SacredStonesRecomp-0.1.12-android-arm64.apk from Assets.
The source-code archives are not playable packages. The .apk.sha256 asset
contains the download checksum. Requires Android 9+ and ARM64.

Windows users should keep using v0.1.10.
This release does not change the Windows runtime or launcher.

Changes

• Export saves from setup or Assist Tools > Export saves in the game.
  Export remains accessible when the setup launcher is skipped.
• Choose a ZIP destination using Android's document picker. The game stays
  paused while exporting; the original saves are not modified.
• Archives include the battery save, existing save-state slots 1-9, automatic
  suspend snapshot, and backup manifest. ROM, BIOS and preferences are excluded.
• Saved games app shortcut opens setup without automatically starting the
  game, on launchers that support shortcuts. Availability varies by launcher.
• Modern Android 13+ Back handling, with legacy support for Android 9-12.
  One press of Ayn Thor's physical Back button now opens the in-game menu.
  Controller Select remains GBA Select; Home remains a system action.
• Larger aspect-correct image: touch-gesture margins no longer shrink the game
  viewport. Display cutouts remain protected, as do the virtual controls' own
  touch-safe margins. Side bands remain necessary on wider-than-3:2 screens.

Updating And Backups

Close the game and install the APK over the existing app. Do not uninstall
or clear app data; those operations remove private saves, states and imports.
The app uses the existing production certificate and signing lineage.

Wait for Saves exported before treating a ZIP as a backup. An export failure
can leave an incomplete destination file. There is no archive import yet, and
save-state compatibility across platforms or runtime versions is not guaranteed.
Keep the original app and its data intact.

Validation

The maintainer confirmed export on Pixel 9 Pro, physical Back on Ayn Thor,
and accepted the display correction after reporting it on Pixel 9 Pro,
Xiaomi Pad 5 and Ayn Thor. Gameplay was already validated on these devices.
This is not exhaustive start-to-finish testing or support for every device.

• Save archives tested for exact bytes, unchanged originals, ROM/BIOS exclusion,
  state-only export, invalid sizes, empty storage and write failure.
• Actual native menu mapper and display branch tested, along with pad geometry,
  touch-coordinate mapping, cutout protection, FE8 transitions and PPU smoke tests.
• Modern Back registration/removal and legacy guards tested with a dispatcher
  test double; actual Ayn Thor button access confirmed by the maintainer.
• Local Android engine patches apply to a fresh pinned checkout with matching hashes.
• APK certificate pinned; signatures verified for Android APIs 28, 31 and 35.
• ARM64/16 KiB native alignment and exclusion of private assets checked.
• Publishes the exact signed APK validated as test build 11 (version code 11).

The APK contains no ROM or BIOS dump. Supply your own legally obtained USA ROM
and GBA BIOS. See the README
for installation and controls.

v0.1.11 - First Android release

v0.1.11 - First Android Release

Download

Install SacredStonesRecomp-0.1.11-android-arm64.apk from Assets.
The source-code archives are not playable packages. The .apk.sha256 asset
contains the download checksum.

Windows users should keep using v0.1.10.
This release adds Android and does not change the Windows runtime or launcher.

Android

• Native ARM64 static recompilation, Android 9 or newer.
• Setup screen imports and verifies your own USA ROM and GBA BIOS.
• Touch controls and physical controller support, including controller-based
  automatic virtual-pad hiding when no manual preference is saved.
• Aspect-correct 3:2 screen fitting and thumb-accessible Start/Select at the bottom.
• In-game settings and Assist Tools: save/load state slots, fast-forward, rewind.
• Internal SRAM save and automatic suspend/resume, separate from save states.
• Eirika launcher icon and dedicated production signature.

The maintainer reports functional gameplay on Google Pixel 9 Pro, Xiaomi Pad 5,
and Ayn Thor, plus successful save/load state testing through the menu.
The Ayn Thor uses one landscape screen; dual-screen support is not included.
The game has not been exhaustively tested from start to finish or on every device.

Updating The Test Builds

Close the game and install the APK over the existing app. Do not uninstall
or clear app data: either operation removes private saves, states, and imports.
The production certificate includes a signing lineage from the project's local
experimental APKs. The Pixel accepted a direct test-6 to production update, and
the maintainer confirmed resuming the previous position and loading the previous
save state afterward. Updates on the other two devices remain to be checked.
If Android refuses an update, report the error instead of uninstalling.

The APK is signed and non-debuggable. GitHub installation can still trigger
unknown-app or Play Protect prompts; signing does not guarantee their removal.
There is no in-app save export yet.

Validation

• Release certificate pinned and signature verified for Android APIs 28, 31, 35.
• APK contains no ROM/BIOS dumps, saves, generated source, or local configuration.
• Native libraries checked for ARM64 and 16 KiB ELF segment alignment.
• Six negative package tests, native screen/touch mapping tests, actual virtual
  pad geometry/hit-region tests, five FE8 transition cases and upstream PPU tests.
• All local engine patches applied with matching hashes on a fresh pinned checkout.
• Windows dependency pins unchanged.

You must supply your own legally obtained ROM and GBA BIOS. No game dump or
BIOS dump is included. Android build/signing instructions and detailed validation
notes are in android/README.md.

v0.1.10 - In-game menu and persistent controls

v0.1.10 - In-game menu and persistent controls

• Open the in-game menu with Escape or the controller Guide button (when available through your driver).
• Select save-state slots 1-9, save/load, adjust fast-forward from 2x to 10x, and enable or disable rewind independently.
• Remember the selected slot, speed multiplier, and Assist Tools/rewind switches in runtime-controls.toml. Active fast-forward and rewind history are not restored on restart.
• Remember launcher dimensions in launcher-window.ini; use a 940x799 default that fits smaller displays. Existing saved dimensions take precedence.
• Improve launcher focus handling and prevent runtime-menu descriptions from overlapping controls.
• Expand the README with current features, shortcuts, configuration locations, and update instructions. The game and launcher remain in English.

Existing BIOS selection, controller preferences, internal saves, rewind, and optimized builds are retained. Internal game saves remain independent of Assist Tools.

Installation and Updates

Download and extract SacredStonesRecomp-0.1.10-win64.zip, then run SacredStonesRecomp.exe at the archive root. Provide your own USA game ROM and GBA BIOS. Neither is included.

Back up and preserve your saves folder and personal configuration files when updating. Save states remain beside the selected ROM as .state1 through .state9; back these up separately. See the included README for details.

The Windows archive contains compiled binaries, launcher assets, configuration, and documentation, not game source or game data. GitHub's automatically generated source archives are not the playable download.

The maintainer validated the launcher and runtime-menu changes in gameplay. A fresh build with dependencies fetched from GitHub passed all thirteen runtime scenarios, three project test programs, and both targeted launcher/runtime-menu tests. Full-game coverage remains incomplete.

v0.1.9 - Optimized builds and launcher fixes

What's changed

• Optimized Release builds for the game and runtime; smooth fast-forward validated in gameplay.
• Selected upstream performance improvements make expensive diagnostics opt-in.
• Play opens the BIOS picker when the BIOS is missing or invalid. Select your BIOS, then press Play again.
• The launcher remembers the selected input device, including on quit. An unavailable preferred controller falls back safely; keyboard input remains available.
• Preserved internal saves, save states, rewind, and safe save-file recovery.
• Pinned runtime and launcher forks, updated project status, and retained the AI-assisted development disclosure.

Download

Download SacredStonesRecomp-0.1.9-win64.zip, extract it, and run SacredStonesRecomp.exe at the archive root. GitHub's automatic Source code archives are not playable builds.

You must provide your own supported USA game ROM and GBA BIOS. Neither is included. Keep your existing saves folder when updating.

Validation and limitations

Built from an isolated clean clone with dependencies fetched from GitHub. All eleven runtime scenarios, four upstream native tests, and project save-file and launcher-policy tests passed. The packaged binaries also passed their isolated pre-publication checks. Gameplay, combat, fast-forward, internal saves, save states, rewind, BIOS selection, and input persistence were validated by the maintainer.

The project is playable and actively developed, not a claim of complete full-game coverage. The maintainer no longer observes the previously reported intro audio artifact in recent releases; its original cause is unconfirmed. Broader upstream launcher and CPU timing changes are deferred.

v0.1.8

Download

Download SacredStonesRecomp-0.1.8-win64.zip below, extract it, and run
SacredStonesRecomp.exe at the archive root. Select your own USA ROM and
GBA BIOS in the launcher. ROM and BIOS files are not included.

When updating an existing installation, keep your saves directory and personal
configuration files.

Fixed

• Preserve the previous SRAM save and its temporary recovery file if replacement
  fails, including when another program locks the save file.
• Honor explicit and relative save paths without migrating or modifying the
  default save.
• Build the generator from the pinned framework and reject outdated generated
  code before runner builds.
• Add static resume coverage for the game, eliminating the missing dispatch
  entries observed in the extended menu-input test.

Validation

The user validated the local v0.1.8 archive. Automated tests passed for boot,
SRAM-file reload, both save-path options, relative filenames, locked-save
recovery, and stale-generation rejection. A 3,600-frame headless input test and
a 1,200-frame windowed replay completed without interpreter or compiler fallback.

These tests do not establish exhaustive gameplay coverage or certify all in-game
save-slot contents. Details are in the
code review.

AI-Assisted Development

SacredStonesRecomp is developed with substantial assistance from OpenAI Codex
for code, debugging, reviews, build tooling, and documentation. The maintainer
directs the work and validates releases through gameplay alongside automated checks.

v0.1.7

Download

Download SacredStonesRecomp-0.1.7-win64.zip below and extract it into a folder.
Run SacredStonesRecomp.exe at the archive root, then select your own USA ROM
and GBA BIOS in the launcher. The archive contains Windows binaries and launcher
assets; ROM and BIOS files are not included.

When updating an existing installation, keep your saves directory and personal
configuration files.

Fixed

• Fix the crash immediately after the Game Boy Advance logo by compiling the BIOS
  with its interrupt-return and resume configuration.
• Require a BIOS for runner builds and default to two parallel build jobs.
• Run isolated startup and SRAM-file reload tests on staged binaries before
  packaging. Diagnostic logs remain in build/validation/ for developers.

Validation and remaining issues

The corrected build passed 1,200 startup frames, 1,200 frames after SRAM-file
reload, and 600 windowed frames without a crash or missing dispatch entries.
The user also confirmed a successful test of the corrected archive.

The code review records remaining save-handling risks, generator/runtime version
alignment, and static-coverage gaps in an extended headless input test. That test
does not establish the same gaps in interactive play. Automated checks do not
certify all gameplay paths or in-game save-slot contents.

See the code review
for details.

v0.1.6-preview

Release Notes

v0.1.6-preview - Proposed

Clean build and packaging reproducibility update for the Windows preview build.

Fixed

• Clean checkouts can now rebuild the launcher runner end to end with scripts/build-runner.ps1.
• The runner build regenerates local BIOS-derived recompilation output from the user-provided BIOS instead of relying on files left in a developer checkout.
• The generated game library is now built with MinGW and linked as libgbarecomp_game.a, removing the previous corrupt .drectve linker warnings caused by mixing MSVC objects with the MinGW runner.
• MinGW runtime DLL staging now follows the configured compiler path instead of assuming C:\msys64.

Verified

• Fresh clone build, package creation, BIOS LLE backend, and SRAM save configuration were validated from F:\git\SacredStonesRecompTemp.

v0.1.5-preview - Proposed

Save handling and launcher BIOS picker hotfix for the Windows preview build.

Fixed

• The launcher exposes the GBA BIOS picker again and persists the selected BIOS
  path beside the executable.
• The runner now forces FE8's SRAM save type at process startup. This keeps the
  interactive launcher path from losing [save].type = "sram" before runtime
  save-chip setup.
• The runner now creates the executable-local saves/ directory before runtime
  startup.
• Existing battery saves are migrated to the stable path
  saves/SacredStonesRecomp.sav when the stable file is missing or still blank.
• Migration checks the prior launcher/runtime conventions: saves/<ROM>.sav,
  a .sav beside the ROM, a .sav beside the executable, and the temporary
  singular save/ folder used during manual testing.
• SRAM 16-bit and 32-bit writes now persist every byte instead of only the low
  byte. This matches BIOS copy routines that write wider words into the 8-bit
  SRAM region.

v0.1.4-preview - Proposed

Save-path hotfix for the Windows preview build.

Fixed

• Battery saves now use an executable-local stable path:
  saves/SacredStonesRecomp.sav.
• The save filename no longer depends on the selected ROM filename, and the
  runtime no longer falls back to writing a .sav beside the ROM when launched
  through the packaged runner.

v0.1.3-preview - Proposed

Third hotfix for the Windows preview build.

Fixed

• The Windows preview now uses a user-provided GBA BIOS instead of forcing the
  incomplete BIOS HLE path. This restores correct boot timing and interrupt
  behavior in the packaged launcher build.
• The executable-local game.toml handling from v0.1.2 is kept, so launcher
  state, ROM cache, BIOS cache, save path derivation, and runtime configuration
  stay anchored to the extracted release folder.

Packaging

• Windows archive remains binary-only and user-facing: executable at archive
  root, runtime DLLs, launcher assets, game.toml, README, and release notes.
• ROM files, BIOS dumps, saves, local picker/config files, caches, diagnostics,
  logs, generated objects, and source archives are not included in the asset.

GitHub Cleanup

• Earlier preview releases v0.1.0-preview, v0.1.1-preview, and v0.1.2-preview
  were withdrawn because their packaged launcher builds were not reliable.

v0.1.2-preview - Proposed

Second hotfix for the Windows preview build.

Fixed

• The launcher now receives the executable-local launch context before it opens.
  This keeps launcher state, ROM cache, save path derivation, and game.toml
  lookup anchored to the extracted release folder.
• game.toml is explicitly exposed to the launcher through launcher_game_config.
• --config <exe>/game.toml and --bios-hle are applied both before and after
  the launcher step so the interactive launch path matches headless tests.

v0.1.1-preview - Proposed

Hotfix for the first Windows preview build.

Fixed

• The runner now resolves game.toml from the executable directory on Windows.
  This keeps BIOS HLE and FE8 SRAM configuration active when launching the
  release from Explorer or another working directory.

Packaging

• Windows archive remains binary-only and user-facing: executable, runtime DLLs,
  launcher assets, game.toml, README, and release notes.
• ROM files, BIOS dumps, saves, local picker/config files, caches, diagnostics,
  logs, generated objects, and source archives are not included in the asset.

v0.1.0-preview - Proposed

First Windows preview build for Fire Emblem: The Sacred Stones (USA).

Highlights

• Integrated recomp-ui launcher with GBA profile and box art.
• ROM selection is cached locally after first launch.
• BIOS HLE is enabled by default; normal users are not asked for a BIOS file.
• SRAM save and load are configured for FE8.
• Save states and rewind are enabled.
• Runtime state is anchored next to the executable for portable extracted builds.
• Build output is quiet: generated/framework warnings are filtered from normal
  project builds.

Known Issues

• Minor intro audio artifact reported at the very beginning of the game.
• Windows packaging only for this preview.
• Mods are intentionally not exposed yet.

Release Artifact Policy

Release archives must not contain:

• ROM files (*.gba).
• BIOS dumps (*.bin).
• Battery saves or save states.
• recomp_cache/ or diagnostic dump files.
• Local picker/config files such as *rom.cfg, *bios.cfg, and
  sacredstonesrecomp.ini.

The expected Windows archive contains the executable, required runtime DLLs,
launcher assets, and game.toml.

v0.1.5-preview

Release Notes

v0.1.5-preview - Proposed

Save handling and launcher BIOS picker hotfix for the Windows preview build.

Fixed

• The launcher exposes the GBA BIOS picker again and persists the selected BIOS
  path beside the executable.
• The runner now forces FE8's SRAM save type at process startup. This keeps the
  interactive launcher path from losing [save].type = "sram" before runtime
  save-chip setup.
• The runner now creates the executable-local saves/ directory before runtime
  startup.
• Existing battery saves are migrated to the stable path
  saves/SacredStonesRecomp.sav when the stable file is missing or still blank.
• Migration checks the prior launcher/runtime conventions: saves/<ROM>.sav,
  a .sav beside the ROM, a .sav beside the executable, and the temporary
  singular save/ folder used during manual testing.
• SRAM 16-bit and 32-bit writes now persist every byte instead of only the low
  byte. This matches BIOS copy routines that write wider words into the 8-bit
  SRAM region.

v0.1.4-preview - Proposed

Save-path hotfix for the Windows preview build.

Fixed

• Battery saves now use an executable-local stable path:
  saves/SacredStonesRecomp.sav.
• The save filename no longer depends on the selected ROM filename, and the
  runtime no longer falls back to writing a .sav beside the ROM when launched
  through the packaged runner.

v0.1.3-preview - Proposed

Third hotfix for the Windows preview build.

Fixed

• The Windows preview now uses a user-provided GBA BIOS instead of forcing the
  incomplete BIOS HLE path. This restores correct boot timing and interrupt
  behavior in the packaged launcher build.
• The executable-local game.toml handling from v0.1.2 is kept, so launcher
  state, ROM cache, BIOS cache, save path derivation, and runtime configuration
  stay anchored to the extracted release folder.

Packaging

• Windows archive remains binary-only and user-facing: executable at archive
  root, runtime DLLs, launcher assets, game.toml, README, and release notes.
• ROM files, BIOS dumps, saves, local picker/config files, caches, diagnostics,
  logs, generated objects, and source archives are not included in the asset.

GitHub Cleanup

• Earlier preview releases v0.1.0-preview, v0.1.1-preview, and v0.1.2-preview
  were withdrawn because their packaged launcher builds were not reliable.

v0.1.2-preview - Proposed

Second hotfix for the Windows preview build.

Fixed

• The launcher now receives the executable-local launch context before it opens.
  This keeps launcher state, ROM cache, save path derivation, and game.toml
  lookup anchored to the extracted release folder.
• game.toml is explicitly exposed to the launcher through launcher_game_config.
• --config <exe>/game.toml and --bios-hle are applied both before and after
  the launcher step so the interactive launch path matches headless tests.

v0.1.1-preview - Proposed

Hotfix for the first Windows preview build.

Fixed

• The runner now resolves game.toml from the executable directory on Windows.
  This keeps BIOS HLE and FE8 SRAM configuration active when launching the
  release from Explorer or another working directory.

Packaging

• Windows archive remains binary-only and user-facing: executable, runtime DLLs,
  launcher assets, game.toml, README, and release notes.
• ROM files, BIOS dumps, saves, local picker/config files, caches, diagnostics,
  logs, generated objects, and source archives are not included in the asset.

v0.1.0-preview - Proposed

First Windows preview build for Fire Emblem: The Sacred Stones (USA).

Highlights

• Integrated recomp-ui launcher with GBA profile and box art.
• ROM selection is cached locally after first launch.
• BIOS HLE is enabled by default; normal users are not asked for a BIOS file.
• SRAM save and load are configured for FE8.
• Save states and rewind are enabled.
• Runtime state is anchored next to the executable for portable extracted builds.
• Build output is quiet: generated/framework warnings are filtered from normal
  project builds.

Known Issues

• Minor intro audio artifact reported at the very beginning of the game.
• Windows packaging only for this preview.
• Mods are intentionally not exposed yet.

Release Artifact Policy

Release archives must not contain:

• ROM files (*.gba).
• BIOS dumps (*.bin).
• Battery saves or save states.
• recomp_cache/ or diagnostic dump files.
• Local picker/config files such as *rom.cfg, *bios.cfg, and
  sacredstonesrecomp.ini.

The expected Windows archive contains the executable, required runtime DLLs,
launcher assets, and game.toml.

v0.1.4 Preview

Save-path hotfix for the Windows preview build.

This build keeps the v0.1.3 behavior requiring the user to provide their own GBA BIOS, and fixes battery-save placement.

Fixed:

• Battery saves now use an executable-local stable path: saves/SacredStonesRecomp.sav
• The save filename no longer depends on the selected ROM filename.
• The packaged runner no longer falls back to writing a .sav beside the ROM.

Use the binary asset below, not GitHub's auto-generated source archives.

Included:

• SacredStonesRecomp.exe at archive root
• Required runtime DLLs
• Launcher assets
• game.toml, README.md, RELEASE_NOTES.md

Not included:

• ROM files
• BIOS dumps
• Saves or save states
• Local picker/cache/config files
• Generated source/build outputs

SHA-256:
82D8F16DFF6CFE02020440EAB9CF21723B09D087FA240A0F5FE1CC010D188AF2