Bloodborne Archipelago - report a bug

Security problems do not go here. If you have found something that affects other people's machines, use the private channel in SECURITY.md rather than a public issue.

1. Release tag

The launcher window title says it, and so does line 3 of client.log. "I built it from main on Tuesday" is a fine answer — say that instead.

2. What happened, and what you expected

Where you were, what you picked up or fought, what the game or the client did, and what you thought it would do instead.

3. Does it happen again?

A bug that reproduces is a bug that gets fixed this week.

Yes, every time Sometimes Once only Have not tried

4. Your yaml

The options block you generated with, in full. Half of it is not enough: the option that matters is usually not the one you would have quoted.

5. Session folder

This is the important one. Zip the newest folder under %LOCALAPPDATA%\BloodborneArchipelago\sessions\<id>\ and attach the zip to the GitHub issue — do not paste it here, it is far too big and this page cannot upload it. The launcher's Open Diagnostics button opens the folder for you. What is in it, and what each file answers:

client.log — what the client thought it was doing

delivery-diagnostics.jsonl — every grant attempt and its outcome

ledger.json — what the seed believes you have received and sent

rescue-diagnostics.json — present if the rescue console ran

6. Launcher Doctor output

Click Doctor in the launcher and paste the whole thing, PASS lines included. A PASS line is evidence too: it rules a cause out.

7. shadPS4

Which version, and whether you run it as administrator. Elevation changes where the emulator writes and what the client can see.

8. Was the DLC in play?

The include_dlc value from your yaml. It changes which checks exist at all, so a "missing check" means two different things depending on it.

Yes No Not sure

9. Other mods

The two that actually collide with this one.

rainmakerv3 BB_Launcher is installed and active

CUSA03173-mods-user is not empty

10. Spoiler log (optional)

If the question is "should this item have been here", the spoiler log answers it in one line. Attach it to the issue rather than pasting it.

Send it

The issue opens with everything above already filled in, under the same headings as the repository's playtest-report template. Attach the session zip in that window — a browser cannot attach a file to an issue for you.