What players are trying to do
This page turns archived discussion into a content backlog. It helps us decide which pages to verify next; it does not pretend that comment frequency equals Google search volume.
Task map
11 player tasks were clustered by the job a player is trying to complete, not by identical wording. 1 already have a verified page route; 4 remain blocked until data is verified.
| Player task | Evidence | Planned route | Status |
|---|---|---|---|
| Choose or clear a dungeon route | 31 | Dungeon hub + route guides | research-clue |
| Find a weapon, ability, cosmetic or item | 18 | Loot hub + entity pages | research-clue |
| Level up and reach leaderboard goals | 17 | Progression hub + leveling guide | research-clue |
| Track updates, new maps and return status | 13 | Update timeline | research-clue |
| Understand whether DQR is official or licensed and who owns it | 11 | Source and identity guide | research-clue |
| Play with friends or get a carry | 9 | Multiplayer guide | research-clue |
| Choose VIP, gold boost or gamepass purchases | 7 | Purchase comparison guide | hold |
| Allocate stats and choose abilities or builds | 6 | Build comparison | hold |
| Find or open Dungeon Quest Reborn | 5 | Access and identity guide | verified-page |
| Trade items or avoid scams | 3 | Safety guide | hold |
| Check console or platform availability | 2 | Platform guide | hold |
How a cluster becomes a page
- Keep the original wording and source URL in the research archive.
- Separate the player task from any factual claim in the discussion.
- Attach the task to one canonical page; merge long-tail wording instead of creating one page per phrase.
- Collect authoritative or timestamped evidence for the exact answer, then mark the page verified.
- Assign an update trigger and re-check the page after game updates or new repeated questions.
Data-source gate
The scraper pass checks whether each source can support a factual page. A source can be useful for discovering demand and still be unfit for proving a mechanic.
| Source | Status | Usable for | Next action |
|---|---|---|---|
| Roblox experience listing | archived | Game identity, place ID, universe ID, developer label and official launch link. | Re-check the listing after each update and retain the retrieval timestamp. |
| Reddit search / public threads | archived | Demand clues, aliases and recurring player problems. | Re-run a rate-limited search window and archive raw responses before clustering. |
| Official Discord | discovered-not-archived | Potential update and community evidence after a human confirms the server and accessible channels. | Human opens the official listing, confirms invite and permission scope, then exports only permitted public announcements. |
| Trello board | not-found | Would support structured maps, items, updates or task status if an official board exists. | Use the official Discord and Delta Quarters OG Roblox group as the current update-source candidates. Re-check those official channels for a newly published board before each major data refresh; do not guess a board ID. |
| Codes | not-found | A codes page only after a current redemption UI and official code strings are verified. | Keep the page as no-code/status draft until an official source or reproducible current UI confirms the feature. |
| Items and loot | discovered-not-archived | Entity pages and filters after names, attributes, acquisition and version are captured. | Create records only from permitted developer data, official announcements or timestamped gameplay evidence with a verifier. |
Video topic map
The YouTube-intel pass classified titles from the archived RblxMaven video list. The archive contains 43 videos, but its saved index has no view counts, channel names or publish dates. Therefore this section identifies formats and page opportunities, not popularity.
| Video topic | Count | Page opportunity | Limit |
|---|---|---|---|
| Progression series | 12 | Build a progression hub and verified leveling route once XP and level rules are sourced. | Series presence does not prove an optimal route or XP rate. |
| Return / update commentary | 13 | Maintain a dated update timeline tied to developer or Roblox evidence. | “Back” or “new” in a title does not prove a patch or ownership claim. |
| Loot and trading | 7 | Create item records and trade-safety guidance only after each fact has a source and version. | Video titles cannot establish drop rates, item stats or a trading system. |
| Co-op and live play | 5 | Add a solo-versus-party decision guide and carry safety notes after mechanics are verified. | Live titles do not prove matchmaking or party rules. |
| Dungeon tutorials | 2 | Produce route pages from timestamped gameplay plus an authoritative dungeon list. | Two titles are too little to estimate demand or difficulty. |
| Scripts / automation | 4 | Exclude these from content and use them only as a risk signal. | Never publish, link to or operationalize exploit instructions. |
Transcript gate
43 videos were checked on 2026-08-27; 33 produced usable local Whisper text and 6 produced no speech segments. These are generated evidence, not human-reviewed transcripts. Available tools: yt-dlp, ffmpeg, openai-whisper-tiny (local venv, MPS).
- Whisper produced no speech segments; requires manual audio review: 6
- Exploit/script/automation videos excluded by policy: 4
Calculator gate
The generic RPG engine is not a source of DQR truth. The damage, XP, attribute and upgrade formulas remain unverified, so the calculator route stays on hold. The development contract is recorded in docs/rpg-calculator-gate.md.
Source record
Full comments and Reddit RSS are retained in the local research archive. The synthesis is recorded in EVD-030-discussion-task-clusters-20260826.md. The archive explicitly records failed subtitle retrieval and Reddit rate-limit events; those gaps are not silently treated as zero demand. The approved dated report index is available at /data/research/index.json.