Dead as Disco BPM Tracker Template: How Rhythm Data Will Be Verified
Dead as Disco BPM 追踪模板：节奏数据如何验证
A verification template for future Dead as Disco BPM entries, offset notes, rhythm windows, evidence screenshots, and video timestamps without publishing guessed values.
Evidence status
Needs in-game checkThis page is a useful template or planning note, not a final gameplay claim.
Next: capture gameplay footage before publishing moves, BPM, rewards, unlocks, or rank thresholds.
Use this for
Songs & Stages
Trust level
Needs in-game check
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: It defines the verification standard that future BPM rows must meet.
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
Minimum Evidence For A BPM Row
A future BPM row should not be published as final unless the site can point to repeatable evidence. Acceptable evidence can include an official source, a current-build in-game display, a documented measurement process, or a video timestamp that clearly supports the value.
- Record the game version and platform with every value.
- Attach the screenshot filename or video URL plus timestamp.
- Mark uncertain rows as needs gameplay verification instead of rounding into certainty.
Offset And Rhythm Window Notes
BPM alone does not prove how combat feels. Future rows should separate music BPM, perceived hit timing, input offset, audio setup, and whether the note is about an official song or a My Music custom track.
- Do not treat custom-track behavior as official soundtrack behavior.
- Do not publish exact timing windows until they are repeatably tested.
- Keep audio hardware notes separate from game mechanics notes.
Template Row
Use this row shape later: song title, source type, BPM, confidence, evidence URL or filename, timestamp, game version, platform, audio setup, My Music or official song, checked by, checked date, and update note. Leave unknown fields as source pending.
Current BPM Evidence Rows
YT-002 shows a calibration-style workflow candidate, while YT-015 is only a double-BPM behavior example candidate. These rows can help reviewers decide what to measure later, but they are not enough to publish exact BPM values, timing-window numbers, offset advice, or custom-track recommendations.
Evidence desk
Screenshot / Video Evidence Area
No final BPM values are published in this template.
It defines the verification standard that future BPM rows must meet.
YT-002 and YT-015 are source-pending review anchors for BPM/calibration behavior, not final BPM data.
Use them to plan measurement, not to publish exact values, offset guidance, or rules.
FAQ
Why not publish approximate BPM values now?
Approximate values can mislead players tuning offset or custom tracks. The tracker should prefer source pending over false precision.
Can YouTube videos be used as BPM evidence?
Yes, if the timestamp clearly supports the claim and the row records the URL, timestamp, channel, upload date, platform, and game version when visible.