Summon Night: Craft Sword Monogatari 3
Summon Night: Craft Sword Monogatari - Hajimari no Ishi
OrigenGame Boy Advance
TecnologíaRecompilación Estática (C/C++ nativo)
Disponible paraWindows
Ver proyecto oficialSobre el proyecto
Summon Night: Craft Sword Monogatari - Hajimari no Ishi es un videojuego de rol publicado por Banpresto para Game Boy Advance, lanzado en 2003.
Información oficial del proyecto
Summon Night: Swordcraft Story 3 PC Port
Work-in-progress PC static-recompilation port of Summon Night: Craft Sword Monogatari — Hajimari no Ishi (Game Boy Advance, Japan), using gbarecomp and recomp-ui.
An unofficial fan project intended to celebrate and support the original game and its creators, not an official or endorsed release. This description does not resolve the project's open distribution/asset-permission review.
Play the portable version
The next player package is named Unfinished Alpha - Windows Portable version and is being prepared as a Windows x64 pre-release, not a finished or fully tested port. See alpha preparation and known limits. There is no new public download until an approved release asset is attached.
For a playable download, check the GitHub Releases page for a Windows portable ZIP attached as a release asset. GitHub's automatic Source code (zip/tar.gz) downloads are developer source, not the game. If a release has no portable asset, it does not provide a ready-to-run build.
Extract the entire portable ZIP into a writable folder and start
Swordcraft Story 3.exe, keeping its Runtime folder beside it.
Older portable packages use Swordcraft Story 3 Beta.exe; follow the README
inside the ZIP you actually downloaded.
You do not need a BAT file or development tools to play a portable build.
Supply your own verified Japanese ROM and GBA BIOS. Japanese does not require a translation. English requires a translation revision supported by that specific build; see the README inside your downloaded ZIP. No ROM, BIOS, translation patch, or personal save is supplied by this repository.
Current source and release status
This branch prepares original Japanese and English 1.1.1f test builds. English revisions have separate generated instruction corpora and save paths; a future translation is not automatically compatible. See input identities.
The latest merged scenery work extends Repeat scenery to all 17 standard battle arena descriptors (IDs 0–16), with arena-specific continuations and native fallbacks for unsupported states. See implementation, verification and known limits. This is not certification of every battle, spell, story route, or visual join.
Other existing features include themed launcher/Esc menus, optional Hold Select to Guard, graphics presets and filters, switchable aspect ratios, save-state/rewind tools, and F10 diagnostic capture. These remain beta features; options and compatibility depend on the installed build.
Release-readiness work is in progress. Merging source does not update an already-installed portable. The packaging recipe and player README now target 1.1.1f. The earlier 1.1.0f candidate's results do not certify this update; remaining acceptance gates must be resolved before publishing. See the 1.1.1f compatibility scope. Do not relabel an old ZIP as a new build.
For the preserved October 20 tester ZIP, see the historical beta handoff. It still starts with Current. This alpha source defaults fresh installations to Repeat scenery while preserving existing saved choices. The alpha needs its own build identity and verification; it does not alter the old ZIP. Linux/macOS build preparation is a separate track, not verified playable support.
Build or contribute
Clone the source with its pinned dependencies:
git clone --recurse-submodules https://github.com/Nicktendonick/SummonNightSwordcraftStory3Recomp.git
cd SummonNightSwordcraftStory3Recomp
For an existing clone, run git submodule update --init --recursive.
Both dependency repositories are accessible without the former private-repo
invitation requirement; a fresh recursive clone was checked on October 16, 2026.
- Developer workflow and current build verification
- Developer tool index
- Modding entry points and compatibility boundaries
- Renderer design and investigation handoff — historical observations must be checked against current code.
- Portable packaging recipe — requires a matching clean build record and never publishes automatically.
- Distribution review requirements
Game-specific code belongs here; generic engine changes belong in gbarecomp,
and generic launcher/UI changes in recomp-ui. Keep ROMs, BIOS, patches, saves,
captures, generated game code, and compiled outputs out of commits.
Report a problem
Include the portable/revision name, language and translation version, Windows version, graphics settings, input device, and exact reproduction steps. For a rendering issue, press F10 in the running portable and note the capture folder. Review diagnostics before sharing: do not upload ROMs, BIOS, saves, or raw game-memory captures publicly. Ask which minimal diagnostic files are needed. See the tester guide and report fields and distribution inventory. New documentation and the issue form are local preparation until separately approved for upload.
Historical experiments
Old lake/forest tests, rollback launchers, English-beta wrappers, machine-specific Ghidra shortcuts, and the alpha-packaging shortcut are preserved as reference text, not current launch instructions. See history index. The cleanup does not remove the lake renderer, its tests, useful diagnostic tools, or notices still required by packaging.
