Bloodborne Archipelago downloads (Windows x64)
==============================================

This release offers two launcher downloads. Unzip either one into its own
folder and keep that folder intact. Neither archive includes Bloodborne or
runtime files.

BBLauncher-AP-win-x64.zip is the BBLauncher fork. It combines the existing
BBLauncher settings and mod manager with Archipelago and standalone local
randomization. On the Archipelago page, choose BBPort or shadPS4. For BBPort,
select the port folder, merged game/update folder and save profile. For shadPS4,
select your game and shadPS4 0.18.0. Randomize prepares an inactive mod; Launch
verifies and activates that prepared run before starting the game. Archipelago
mode uses an AP seed/player and client. Standalone uses a seed string and
starts no AP client or server. Enemy randomization is optional; reviewed boss
shuffle runs with Archipelago enemy randomization. Scaling defaults on. The package
contains its frozen backend, native tools, client, and provenance manifest.
On first launch it can import an existing regular BBLauncher setup from nearby
folders or Downloads, preserving the original configuration.

BloodborneAPLauncher-win-x64.zip is the original Archipelago launcher. Run
BloodborneAPLauncher.exe, select BBPort or shadPS4, your AP seed request and
server, save Setup, then use its plan/Doctor and Play flow. BBPort needs its
port folder, merged game/update folder and selected save profile. It remains
available as the alternative to the integrated Qt launcher.

Both downloads use versioned filenames on Peliarch. Windows BBPort acceptance
is recorded for Supermedo windows-v1.8.2 with CUSA03173 01.09. The launchers
accept CUSA03173 and CUSA00900 01.09; evidence for regions and individual forks
is separate at https://peliarch.ca/bb/support.html. Canonical Linux AppImage
game launch and other Windows forks are not established by this release.

Newly prepared BBPort seeds request an ordinary game save after AP rewards.
Allow saving to finish before closing the game; this is not atomic recovery
from termination during a save. Keep only the intended seed and compatible
mods active because BBPort automatically enables new mod folders.

bloodborne.apworld is attached separately for people generating seeds. The
original launcher archive also contains it at worlds\bloodborne.apworld and
can install it into a selected Archipelago installation. Players connecting
to an existing seed do not need to install the apworld themselves.

Keep the previous launcher folder for rollback, and stop the game before
changing launchers or active mods. For the BBLauncher fork's short integration
check, see docs\BBLAUNCHER-NEXT-RUN.md in that archive. For original launcher
setup, see docs\PLAYTESTING.md in its archive.

Release receipts identify the exact compiled source revision separately from
later source-only documentation and publication metadata. Check the download's
SHA-256 against its accompanying checksum and verify the first-party executable
signatures and trusted timestamps for Alaric McKenzie-Boone. The Peliarch
release includes package checks, source bindings and scoped game evidence.
This release does not claim a GitHub Actions provenance attestation.

Keep bb-archipelago-source.zip and its checksum with either Windows launcher
for the exact backend/build source. release-readme-source.zip contains source
and provenance for the release documentation update without changing binaries.

Client source and notices
-------------------------
The client source profile, dependency archives, original notices and build receipt
are in tools/source-client. Its provenance.json identifies the client executable
by SHA-256. Rust standard-library notices are under supplemental/rust-standard-library.

Maintainers build the client and its materials together with
packaging/build_client_materials.py. Install Rust nightly-2026-09-30 for the
x86_64-pc-windows-msvc host first. Supply the resulting material directory as
-ClientMaterials alongside -ClientPath and -ClientRef to build_launcher.ps1.
The builder requires the reviewed packaging/client-ref.txt revision; an
experimental client revision needs a source and notice review before repinning.
