Replay dataBPHPLSBDD
yawnletter vs エリンギ戦士
Replay participants and rounds
Participants, characters, controls, outcome, round result codes and available telemetry coverage for one Street Fighter 6 replay.
Replay telemetry
No reportTelemetry is not available for this replay
No readable capture report is saved. Match details may still be available. Open the replay to check capture availability.
Capture details Sampling, timing & omissions
- Report status
- unavailable
- Parser version
- Not available
- Samples parsed
- Not available
- Timing method
- Not available
- Video offset
- Not available
- Report truncated
- Not available
- Omitted health events
- Not available
- Omitted input events
- Not available
- P1 observed health lost
- Not available
- P2 observed health lost
- Not available
The video offset aligns estimated sample times with the recording. A report with no omissions does not establish complete telemetry. Raw frame-by-frame samples are not retained.
Round outcomes
Battle Log- Round 1P1 · yawnletterRound lostP2 · エリンギ戦士Standard victory
- Round 2P1 · yawnletterRound lostP2 · エリンギ戦士Overdrive attack
Match record Identifiers, ratings & round codes
- Replay ID
- BPHPLSBDD
- Replay
- /replays/BPHPLSBDD
- Played at
- Mode
- Ranked
- Player CFN ID
- 3295374816
- Player
- yawnletter
- Selected character
- Mai
- Played character
- Mai
- Controls
- Modern
- Pre-match MR
- 1,808MR points
- Pre-match LP
- 369,602LP points
- Opponent CFN ID
- 2396486924
- Opponent
- エリンギ戦士
- Opponent selected character
- Guile
- Opponent played character
- Guile
- Opponent controls
- Classic
- Opponent pre-match MR
- 1,819MR points
- Opponent pre-match LP
- 568,592LP points
- Result from player perspective
- LW/L/D
- Player round result codes
- 0,0comma-separated codes
- Opponent round result codes
- 1,5comma-separated codes
- Player round outcomes
- Round lost; Round lost
- Opponent round outcomes
- Standard victory; Overdrive attack
Source, coverage & limitations How to read this data
Stored Capcom Battle Log and validated replay capture report when available.
One replay; match date and report capture timestamp are separate.
Last saved update: . Reading this page does not refresh the source.
- Match played
- Report captured
- Not available
- Report availability
- unavailable
- Parser version
- Not available
- Report truncated
- Not available
- Samples parsed
- Not available
- Health events omitted
- Not available
- Input events omitted
- Not available
- Health changes retained
- Not available
- Input transitions retained
- Not available
- Combo candidates retained
- Not available
- Unknown replay codes do not produce fabricated datasets. A report can exist without a stored Battle Log match.
- Telemetry survives video expiry; video availability does not establish telemetry completeness.