DQR Wiki Sources and Evidence Policy

Source hierarchy

1. Current first-party surfaces: the Roblox experience, developer-controlled announcements, and current in-game UI.
2. Current gameplay evidence: public videos and complete screenshots that visibly belong to Dungeon Quest Reborn.
3. Independent cross-checks: multiple current publications, captures, or players supporting the same limited claim.
4. Community reports: useful for trackers and research leads, but clearly labeled.
5. Legacy Dungeon Quest material: discovery-only until a current Reborn source confirms the claim.

Publication rules

A source record includes its URL, publisher, evidence label, checked date, supported claims, consuming pages, and a concrete trigger for rechecking it. A publishable source can still support only a narrow claim. For example, a drop video can verify that an item exists and dropped; it cannot automatically verify every stat or drop rate.

Third-party filenames and captions are not trusted without inspecting the actual frame. Several useful public captures have misleading filenames, which is why the ledger describes what is visible rather than repeating the host page’s label.

Current versus legacy

Repeated names are common. We reject exact legacy HP, required levels, item ranges, dungeon tables, and ability percentages unless current Reborn evidence independently supports them. Legacy data may be noted internally as a candidate to investigate, but it does not appear as a verified answer.

Boss-health samples

Boss health is stored as observations with the visible context: maximum HP, difficulty when known, Hardcore state when known, player level when relevant, and source. Unknown context remains null. The database intentionally has no universal hp field for a boss.

Media use

Official Roblox media is preferred for brand context. Public video pages are embedded from YouTube’s privacy-enhanced domain after a click instead of rehosting the video. Third-party screenshots mainly serve as research evidence unless their reuse basis is clear. Attribution alone is not treated as automatic permission.

Freshness

Dynamic pages—codes, Discord, updates, trading, potential, and upcoming content—display a check date. The ledger names the event that should trigger another review, such as a Roblox description change, a new selector capture, or a current item tooltip.