Dead as Disco Gameplay Evidence Intake Template: Claims, Sources, and Review States
Dead as Disco 实机证据入库模板：结论、来源和审核状态
A safe intake template for future Dead as Disco gameplay submissions, turning YouTube clips, screenshots, notes, and source links into reviewable guide evidence without publishing unverified Boss, BPM, reward, unlock, achievement, or score claims.
Evidence status
Partially verifiedThe topic and structure are reliable, but exact values or fight details still need gameplay capture.
Next: attach screenshots, timestamps, result screens, or official notes before final claims.
Use this for
Beginner Guides
Trust level
Partially verified
Reader mode
Read + verify
Editor Brief
This page is written as a working guide, not a finished wiki dump. Use the confirmed notes first, then treat source-pending rows as a checklist for what still needs gameplay proof.
Current source note: This page defines intake workflow only and does not publish Boss moves, song data, rewards, unlocks, achievements, score thresholds, or final route claims.
Media status
No Public Gameplay Embed Yet
This article keeps the media area honest: no fake screenshots, no decorative gameplay claims, and no third-party stills republished as site assets. When a source clip is approved, this block becomes the video player and timestamp map.
Needed
timestamped clip
Needed
claim being tested
Needed
version/platform
One Row Per Claim, Not One Row Per File
A future evidence library should track the exact guide claim being tested. One video can support several review rows, and one claim may need multiple screenshots or clips. The intake row should say what the evidence is trying to prove, which page would change, and which source files support or challenge that claim.
- Claim scope: Boss move, song/BPM, reward, unlock, achievement, result screen, settings behavior, bug report, or platform/store fact.
- Affected page: use exact guide slugs so a claim does not leak into unrelated pages.
- Source bundle: include video timestamps, screenshot filenames, official source links, and reviewer notes in the same row.
Required Intake Fields
Every submitted material should enter the project with enough context for another editor to re-check it later. Missing platform, version, timestamp, or source owner data should keep the row in needs metadata. The public guide should not change until the row reaches approved for publication.
- Minimum fields: proposed claim, source type, source URL or filename, source owner, timestamp range, platform/store, visible version, capture date, spoiler level, affected guide slug, and reviewer status.
- Review states: inbox, needs metadata, needs second source, ready for review, approved for publication, stale after update, rejected, or retired.
- For official/public store facts, keep the source URL and checked date because store pages can change.
When Evidence Changes Public Copy
Evidence should change public copy only when the claim is narrow, the source bundle matches the claim, spoiler placement is correct, and the reviewer status is approved. If the evidence is strong but incomplete, update the internal row first and leave the public article labeled launch placeholder, needs gameplay verification, or source pending.
- Do not turn a single clip into a full route, final build, exact BPM table, or universal fix.
- If an update changes the game version, mark affected rows stale after update before reusing them.
- When public copy changes, record the old status, new status, evidence row, reviewer note, and last checked date.
Evidence desk
Screenshot / Video Evidence Area
Gameplay submissions should be organized as claim-scoped intake rows with source metadata, review status, spoiler level, affected guide slug, and last checked date before public guide copy changes.
This page defines intake workflow only and does not publish Boss moves, song data, rewards, unlocks, achievements, score thresholds, or final route claims.
FAQ
Can I send a large batch of YouTube videos or screenshots later?
Yes. The safest format is a table or folder note that gives each source a URL or filename, timestamp range, claim being tested, platform, visible version, spoiler level, and affected guide slug. Raw files without claim context will stay in the intake queue.
Does an approved evidence row automatically publish gameplay facts?
No. Approval means the row can support a narrow public claim. The public article still needs correct wording, spoiler placement, related links, FAQ updates when needed, and correction-log notes if existing copy changes.