How to Report Pokémon Draft League Results from Showdown Replays
A replay can reduce score-entry mistakes, but a URL should never rewrite league history just because it loads. The safe workflow keeps the scheduled matchup authoritative, checks the replay on the server, asks the reporter to resolve player identities, and still requires a normal reviewed save. This guide explains what a replay can confirm, what it cannot prove, and how DraftCenter keeps that boundary visible.
Start from the scheduled matchup
Open the regular-season match that the replay belongs to. Confirm the week, teams, participants, and current result state before adding a URL. A replay from an exhibition, playoff, different opponent, or unscheduled game should not be forced into the wrong record.
How this works in DraftCenter
Replay analysis is available only to an authenticated member who controls one of the scheduled teams for an eligible regular-season matchup. The server rechecks the membership, team control, schedule state, rate limit, and existing result before returning any facts.
Use exact public replay URLs
Copy the permanent public replay address after the battle is uploaded. Do not paste a live battle room, arbitrary log mirror, shortened redirect chain, or private file. For a best-of series, collect only the games that belong to the scheduled result.
How this works in DraftCenter
DraftCenter accepts one to five exact public Pokémon Showdown replay URLs. The server validates the host, redirects, response size, timeout, replay identity, and duplicate use instead of trusting browser-supplied text.
Map the Showdown players to the scheduled teams
A Showdown display name is not a DraftCenter account identity. Read both player names and deliberately choose which scheduled team each one represents. If the mapping is unclear, stop and confirm it with the opponent before saving.
How this works in DraftCenter
The reporter must map each parsed Showdown player to one of the two scheduled teams. The result editor does not treat a similar display name as proof of account ownership or silently choose the mapping.
Review only the facts the battle supports
A replay can support its canonical identity, format, game type, upload time, players, winner, participating sides, faint or remaining counts, and Pokémon actually revealed in battle. It cannot prove that an unrevealed roster member was brought, and a faint does not always prove which opposing Pokémon earned a knockout.
How this works in DraftCenter
DraftCenter rebuilds its normal result proposal from bounded parsed facts. It does not store raw replay logs, infer knockout attribution, or claim unrevealed Pokémon were part of the battle team.
Save through the normal result editor
Read the proposed score, differential, winner, mappings, and replay list just as carefully as a manual report. If any value is wrong or unsupported, correct the source or use manual entry under the league's rules rather than saving a misleading confirmation.
How this works in DraftCenter
Analyzing replays never writes the league result. The reporter must review the normal editor and press Save. Manual score or differential changes clear the replay-confirmation payload so an edited result cannot keep an incompatible confirmation badge.
Keep every replay unique
A public replay should support one recorded matchup, not several. Reusing the same game across weeks or leagues creates false evidence even if the score happens to match. Preserve the original link beside the result so a future correction can return to the same source.
How this works in DraftCenter
DraftCenter stores canonical replay identities with the confirmed result and rejects reuse. The server locks and revalidates the authoritative scheduled matchup when the result is saved.
Keep manual reporting available
Cartridge games, unavailable replays, malformed logs, private battles, timeouts, and unsupported sources still need the league's ordinary reporting process. A commissioner should publish the fallback before week one so a technical failure does not become a competitive ruling invented after the match.
How this works in DraftCenter
Manual result entry remains available. DraftCenter does not retry a timed-out replay mutation or turn an analysis failure into an automatic score.
Before saving a replay-confirmed result
- The replay belongs to this exact scheduled regular-season matchup.
- Every URL is an exact public Pokémon Showdown replay and appears only once.
- Both Showdown players are deliberately mapped to the correct scheduled teams.
- The winner, score, differential, and revealed Pokémon match the supported facts.
- No knockout attribution or unrevealed Pokémon claim was inferred from the log.
- I reviewed the normal result editor and intentionally chose Save.
How this guide is maintained
DraftCenter reviews this guide against the product's current workflows. See our data methodology and editorial standards, including how to report a correction.