Recovery and bug reports

A launch failed

Keep the private state directory and app log. Inspect /v1/launch/request?request_id=... or the saved launch-requests/<id>/status.json; preserve started:false, true or null exactly. Earlier successful edits/settings can remain after a later failure. Do not overwrite the request or reuse its ID to force a retry.

If Start is indeterminate or its HTTP response was lost, inspect the same /v1/commands/{id} plus lifecycle/native state before deciding anything. A new Start identity can create a duplicate match. A compatibility pass is static preflight, not a guarantee of live success.

The app or broker disconnected

Keep the exact state, match/run IDs, request and command receipts. Closing a broker normally leaves its child game open. An attached replacement broker does not inherit ownership of that child; owned-stop may be unavailable. Attach for observation/recovery only with an explicitly verified PID and the matching state:

.\OpenHoops.cmd api --pid VERIFIED_GAME_PID --state "C:\MyDynasty\sessions\game001" --port 27614

Never select a process solely by its name and terminate it. Preserve any final delivery already stored; independent consumers can recover it after the game exits. An abandoned or review-required match needs explicit app/user attention. No mid-game save/resume feature is claimed.

ACK or import failed

Recover from the app's committed inbox. ACK only a revision actually stored. Repeated delivery/ACK must not duplicate totals. A later result revision replaces/reconciles prior totals. The same revision with different bytes is an integrity failure, not a new delivery. Keep both evidence and state for diagnosis.

Installation refused

Close the game, verify the supported EXE and retain unknown loaders/configurations. Use the older package's rollback if its backup exists. Do not delete receipts or force-copy a DLL over another loader. Save import copies into a new directory only; resolve missing valid profile/settings in your own game first.

Report safely

Include team build version, dinput8.dll SHA-256, Windows version, API capabilities, exact steps, sanitized request/receipt, error code and whether the failure was static/preparing/Start/gameplay/final delivery. Include roster/asset hashes and counts, not somebody else's assets. Remove API tokens, private file paths, personal account data and credentials. State clearly when evidence came from a synthetic scenario. Keep original failed evidence; a later pass should not rewrite its history.