Frequently Asked Questions

Find the symptom below. If it persists, retain the exact error and occurrence time, then export diagnostics.

Which package should I download?

Most Windows users can use the installer; choose win-x64.zip for portable use. Apple Silicon uses osx-arm64.zip. Linux packages depend on your distribution. See the package table.

Can I reuse files downloaded by the official launcher?

Yes. Select the existing BlueArchive_JP directory during setup or under Settings → Game. The launcher reads manifest.json and game-launcher-config.json. Avoid simultaneous downloads, repairs, or other changes by both launchers.

Downloads are slow

Check unlimited speed → a suitable proxy mode → disk space and write speed → pause and resume. You can also switch sources; repair installed game files afterward to match the new resources.

Restarting can recover a matching task. Explicitly selecting Stop discards its recovery record.

Downloads fail, verification fails, or retries keep repeating

Close the game, confirm directory writability and free space, and check security software for blocked .tmp or game writes. Try another download source and repair if appropriate.

If still failing, record the filename and exact error, increase and save the log level, reproduce, then export. Do not delete unknown temporary files during operations; let the launcher stop and finish cleanup first.

The launcher says the game is running

Close the game and retry. If its window has disappeared, check Task Manager for BlueArchive.exe or xldr_BlueArchiveOnline_JP_loader_x64.exe.

Linux identifies launcher-owned games and external processes mapped to the installation. An inconclusive or timed-out scan also blocks writes. Confirm the game has ended; export logs if detection remains incorrect.

Launch verification reports missing files or size mismatches

Run Repair under Settings → Game. Remote manifest changes the checking reference without repairing files. None can temporarily help isolate verification problems but does not establish file integrity.

How do Official and Cafe sources differ?

Official supplies original Yostar JP resources. Cafe supplies Chinese-localized resources from BlueArchive.Cafe and enables the Resource Panel. Chinese system languages default to Cafe; others default to Official. You can change this in Settings.

Repair after switching to match the new manifest. Resource switches are saved separately for the localization UID; see Resource Panel.

Settings changes did not take effect

Check that you selected Save. Appearance preview does not persist by itself and is restored on discard. Main-window path actions save immediately; path edits inside Settings require Save. Network requests and manual update checks use saved preferences.

Where are motion and color extraction settings?

Motion is under Settings → Appearance → Theme and motion. Extraction algorithm, color variant, and neutrals are in the collapsed Advanced colors section. The extraction option appears only for wallpaper-derived accents. See Appearance.

Video background does not play or has no sound

1. Confirm Windows x64; other platforms use a static fallback.
2. Choose Appearance → Background → Custom and a local .mp4, .mkv, or .webm.
3. Restore a visible window and check whether reduced motion or system animation preferences paused playback.
4. Volume defaults to 0. Raise it and unmute; adjustments while muted change retained volume only.
5. On failure, review the notice and logs, select a playable file, and ensure the complete package's video runtime is present.

Colors use cover art or the first frame and stay stable during playback. Failure and unsupported platforms show the bundled static fallback.

How does the launcher update itself?

Checks run at startup by default, or manually under Settings → About, using the saved update channel.

Windows installed and portable builds show release notes, download, verify against the same release's SHA256SUMS, then Restart to Update. Missing checksums, packages, or updater lead to an explained Open Release Page fallback. macOS and Linux require manual download and installation.

Check failures do not block use. Beta includes prereleases; stable offers stable releases only.

Can Linux launch the game?

The experimental Linux x64 launcher runs the game through separately installed UMU / Proton or Wine. Historical testing includes Arch + UMU 1.4.4 + UMU-Proton 10.0-4 with NTFS3 game files. Anti-cheat compatibility varies with environment and game versions; other combinations are not guaranteed. See runtime settings.

Can the macOS launcher launch the game?

Currently no. The Apple Silicon build installs, updates, and repairs files but does not provide a compatibility layer for launching the Windows game.

How do I view or export logs?

Under Settings → Advanced, View Log browses loaded records, Export Logs creates a ZIP for a time range, and Open Data Directory locates originals. Exports stay local; review paths and UIDs before sharing. See Export logs.

How do I remove everything?

Remove the application, user data, and game directory separately. Check scope and back up first, then follow Uninstall and data. Removing user data also deletes managed compatibility environments inside it.

v1.1.0-beta.5 crashes at startup

This is a historical issue: the initial beta.5 build lacked a concrete WindowFilePickerService registration. Logs contain NoServiceRegistered, Cafe.Launcher.Avalonia.Services.WindowFilePickerService; the affected CommitSha was b33915d.

It was subsequently fixed. Replace that build with a newer complete package from Releases. Separate game files and user settings are preserved. For startup failures in other builds, investigate the actual current error.

I still need help

Follow the feedback guide with version, environment, steps, expected and actual behavior, and a reviewed log ZIP, then open an Issue.