A deep evidence map of what is being reported, inferred or theorised about Grounded 2 — where each claim came from, how the theory evolved, what actually supports it, what weakens it, and what would finally settle it.
Governed research cut: 25 September 2026 · 40 core claims fully analysed · first-party freshness checked 25 September 2026
Popularity, repetition, file presence and community wish lists are not independent corroboration. The register deliberately separates reporting, inference, developer aspiration, datamine signals and demand from established fact.
The register tracks propositions through time. It does not turn discussion volume into confidence, or retrospectively rewrite old rumours as if they were confirmed when first reported.
“Hypothesis”, “reported” and “unsupported” describe evidence state, not betting odds.
Reddit → creator video → fan article is still one theory chain unless a new source adds independent evidence.
Many players asking for weather or a Scorpion Buggy measures demand, not developer intent.
A reported file can show that an idea existed in some form; it does not prove that the feature will ship or survive iteration.
The public page centres on 40 high-value unresolved claims. A collapsed research appendix retains lower-signal requests, datamine leads and historical propositions for traceability without giving them equal editorial weight.
These are not “most likely” predictions. They are the unresolved questions whose resolution would materially change Grounded 2’s story, immediate update picture or release outlook.
The fifth-kid connection has several independent continuity clues, but none identifies the Stranger. It is a strong hypothesis, not a reveal.
The Masked Stranger controlled Wendell during the ceremonyWendell being controlled is established, and the Stranger controls O.R.C. creatures. The missing step is evidence that she controlled Wendell or that O.R.C. can control humans.
The Masked Stranger caused the ceremony explosion and re-shrinkingThe Stranger has motive and technical capability for sabotage, but the ceremony explosion and re-shrinking remain unattributed. This theory has no direct causal evidence.
The Fall update will be version 0.60.6 is the neatest version-sequence inference, but Obsidian has only called this the Fall update. Until an official version or PTB appears, 0.6 should not be treated as its confirmed version.
The Fall update is officially called “Rot and Ruin”The naming vote is first-party and the located reports consistently say “Rot and Ruin” won, so the report is credible. The missing piece is a retained first-party winner announcement; it should not yet be called official.
The concealed Fall creature is a centipedeCentipede is a coherent community theory built from the hidden creature slot, the Rotting Wood Pile/Termites theme and naming clues. No first-party evidence currently names the species.
Winter’s concealed park area is the SandboxSandbox is one of the stronger map guesses because the park geography and series history make it plausible, but the concealed Winter area remains unnamed.
Grounded 2 reaches 1.0 in 20272027 is a reasonable editorial/community forecast based on scope and roadmap pace, but Obsidian has not announced a year. It remains a forecast.
Grounded 2 deliberately leaves several identity and causality gaps open. The strongest theories combine real continuity clues; the weakest fill those gaps with family relationships or true names that the game has not established.
The theory predates launch and strengthened when players connected Grounded 1’s fifth-person trail with Grounded 2’s unknown masked antagonist and later Subject V wording.
The fifth-kid connection has several independent continuity clues, but none identifies the Stranger. It is a strong hypothesis, not a reveal.
Multiple evidence strands exist, but there is no independent identity confirmation. Community discussion and later creator coverage are not additional proof.
An explicit identity reveal, matching Ominent record or unique object/dialogue bridge would resolve it.
A reported preview label “Mystery Character Subject V” prompted immediate V = 5 interpretation; current Obsidian issue wording independently preserves Subject V/V terminology.
Subject V is genuine first-party implementation terminology; reading V as “five” is still interpretation. The clue strengthens the fifth-kid theory without proving it.
The current label is independently first-party; the fifth-kid interpretation is not.
A first-party definition of Subject V would resolve the wordplay claim.
Launch-era identity speculation revived when Into the Abyss added heavily redacted Employee 555 material.
The overlap is thematic, but the current records fit two separate people at least as well as one. A simple Employee 555 = Stranger identity is not supported.
Community theory only; no independent identity corroboration.
A personnel/identity record or explicit story reveal linking—or separating—the two would resolve it.
Post-launch interpretation combines the ceremony control message with the Stranger’s established O.R.C. network.
Wendell being controlled is established, and the Stranger controls O.R.C. creatures. The missing step is evidence that she controlled Wendell or that O.R.C. can control humans.
The underlying clues are separate; the causal connection remains interpretation.
A story reveal naming the controller or explaining the ceremony control mechanism would resolve it.
Players connect the Stranger’s sabotage role and antagonist positioning to the still-unexplained ceremony disaster.
The Stranger has motive and technical capability for sabotage, but the ceremony explosion and re-shrinking remain unattributed. This theory has no direct causal evidence.
No independent evidence identifies the actor or mechanism.
An explicit account of the ceremony failure and re-shrinking would resolve the claim.
The theory appears in March 2026 discussion and recurs later as players connect Sloane’s monitoring of a redacted female subject with the Stranger.
Sloane’s role and the redacted female subject explain why the theory exists, but there is no family evidence. Parentage remains speculation.
A community parentage theory built from Sloane’s role and the redacted subject; no independent family evidence has been located.
A parentage reveal, personnel/family record or explicit dialogue identifying the Stranger’s family.
An April 2026 community theory connected the Stranger to Schmector through O.R.C., Ominent history and perceived resemblance.
O.R.C. and Ominent links make Schmector thematically relevant, but no family record, dialogue or identity clue connects him to the Stranger.
Thematic association plus visual interpretation; no independent family evidence.
An explicit identity/family record, dialogue or developer confirmation.
Into the Abyss-era discussion increasingly separates Employee 555 from the Stranger and asks whether their anti-Ominent roles could instead intersect.
Separating Employee 555 and the Stranger avoids the identity problems of the simpler theory, but collaboration is still unsupported because no contact between them is shown.
A reaction to the weaknesses in the simpler 555 = Stranger theory; it is a distinct hypothesis, not corroboration of either identity claim.
A direct interaction, message chain, personnel record or story reveal linking 555 and the Stranger.
An August 2026 theory interprets the Stranger’s sabotage, SPAC.R imagery and anti-Ominent behaviour as an attempt to turn shrinking technology back on the corporation.
The anti-Ominent motive and shrinking technology make the idea narratively coherent, but no released source states that shrinking Ominent is the Stranger’s objective.
Thematic interpretation of established sabotage and shrinking motifs; no direct objective statement.
The Stranger states or demonstrates a plan to shrink Ominent personnel/infrastructure, or the story establishes a different objective.
“Violet” emerges as community shorthand from the official/implementation-facing V or Subject V terminology.
“Subject V” is real first-party terminology; “Violet” is not. The name is community completion of an initial or codename, with no canonical support.
Official V label → community completion of the initial into a plausible name. Repetition does not create name evidence.
An explicit first-party true-name reveal.
Version number, title, creature identity, boss status, PTB timing and release timing are independent questions. Evidence for one must not be allowed to confirm another.
Community extrapolation follows the major-version sequence 0.2 → 0.3 → 0.4 → 0.5.
The major-version sequence still makes 0.6 an understandable guess, but Patch 0.5.1 reinforces why arithmetic version extrapolation is not confirmation. Obsidian has only called this the Fall update.
Widespread repetition is mostly the same version-sequence inference, not independent corroboration.
The first official PTB or update version number will settle it.
Obsidian ran an official naming vote. Community and Steam discussion identify “Rot and Ruin” and “The Long Crawl” as options, and a 15 September post reports Rot and Ruin won.
The naming vote is first-party and the located reports consistently say “Rot and Ruin” won, so the report is credible. The missing piece is a retained first-party winner announcement; it should not yet be called official.
Vote → community/Steam discussion → reported winner. Later repetition does not create a second result source.
Official PTB/update/social/Discord material using the winning title would resolve it.
Centipede requests predate the current roadmap; explicit Fall-link theories became prominent after the Year 2 roadmap and naming vote.
Centipede is a coherent community theory built from the hidden creature slot, the Rotting Wood Pile/Termites theme and naming clues. No first-party evidence currently names the species.
Community theory → creator/article amplification. Those derivative pieces do not independently corroborate the species.
Creature reveal, PTB or live build.
A second layer of speculation adds “boss” to the centipede hypothesis, partly from earlier update patterns.
This is a second-order theory: centipede is unconfirmed, and boss status adds another assumption. Winter—not Fall—is the roadmap milestone explicitly labelled with a new story boss.
Derivative of the centipede theory; not independent species or boss evidence.
A Fall reveal naming the creature and encounter type.
Immediate roadmap interpretation connects Rotting Wood Pile, Termites and the concealed creature.
The termite theme makes a royal termite easy to imagine, but the roadmap confirms Termites rather than a King or Queen boss. There is no boss evidence beyond thematic fit.
Thematic fit only; no independent corroboration.
Official creature/boss reveal.
Players combine the official Fall window with prior update cadence.
September or October is plausible timing inside the Fall window, but the official window is broader and no exact release date has been published.
Multiple predictions share the same seasonal-window/cadence logic rather than independent schedule evidence.
An official date or narrower release window.
The claim extrapolates from earlier 0.2/0.3/0.4/0.4.1 PTB usage.
Past major updates often used Public Test Builds, so late September is a cadence guess only. No Fall PTB has been announced.
No independent schedule source located.
Official PTB announcement.
The theory observes that AXL and King Dozer appeared between larger map-expansion milestones and assumes the pattern will repeat.
Earlier cycles make another intermediate boss plausible, but pattern repetition is not a roadmap promise and Fall’s concealed creature is not labelled as a boss.
Boss variants of the centipede/termite theories derive from the same cadence argument.
Fall ships with or without an additional boss encounter.
The roadmap establishes that hidden areas exist. Visual geography, old OCR guesses and Grounded 1 nostalgia can make a hypothesis attractive without revealing the actual biome.
Year 2 roadmap discussion linked the hidden Winter area to the large inaccessible south-west sector.
Sandbox is one of the stronger map guesses because the park geography and series history make it plausible, but the concealed Winter area remains unnamed.
No independent first-party identification.
Winter area reveal.
The same roadmap-mapping discussion attempts to assign the undated concealed future area to an inaccessible map sector.
The unexplained space south/east of the Pond is a real geographical clue. Calling it the next expansion still assumes that visible unused space maps to roadmap order.
Map-reading hypothesis; no first-party corroboration.
Future area reveal or map-boundary expansion.
Story/map analysis interprets the remaining park geography as a likely next land biome.
A Playground/Sandbox land biome fits Brookhollow’s setting and community map reading, but no first-party source identifies it as the next major story biome.
Community map analysis only.
Official map/story reveal.
Players connect remaining sandy park space, Grounded franchise Antlions and community Sandpit concepts.
Antlions and a Sandpit are a coherent franchise/community concept, not a disclosed plan. No current roadmap label or primary source commits to either.
Community concepts and map interpretation; no independent developer support.
Official sand/playground biome or Antlion reveal.
This is where semantic drift is most common: a broad roadmap word becomes a specific feature, or a generic promise of new Buggy families becomes a named species prediction.
Flying-mount requests became common; Chris Parker later addressed the idea directly.
Developer interest in flying mounts or traversal is real, but Parker framed it as something the team would like to explore rather than a committed Buggy.
The aspiration is primary developer evidence; community posts are demand signals, not corroboration of a plan.
Roadmap entry, prototype/PTB or update reveal.
Weather and seasons have been recurring player requests since before launch.
Weather is a persistent player request, not a current plan. No roadmap or developer statement reviewed establishes dynamic weather or seasons for Grounded 2.
Many independent requests corroborate demand only—not that weather is planned.
A first-party roadmap, developer statement, PTB or live system.
The item appeared on earlier roadmap versions and is absent from the current Year 2 roadmap.
New Archetypes disappeared from the current roadmap, but disappearance does not establish cancellation. Its disposition is unknown.
The cancellation wording is inference, not a developer statement.
Explicit clarification, reappearance or a shipped replacement.
An earlier roadmap item is absent from the current roadmap.
Active Mutations 2.0 is no longer on the current roadmap, but there is no cancellation statement. Treat it as unresolved, not scrapped.
Cancellation claims derive from absence alone.
Developer clarification, reappearance or identifiable delivery.
The item appeared on an earlier roadmap and later disappeared.
Smoothies 2.0 disappeared from later roadmap revisions, but there is no first-party cancellation statement. “Scrapped” overstates the evidence.
Secondary/community shorthand, not a first-party disposition.
First-party disposition or identifiable delivery.
Players read the roadmap’s plural wording literally and ask whether Winter contains more than one new mount.
The plural wording is real, but Grounded 2 roadmaps have previously used plural or generic labels that later resolved to one named implementation. Quantity remains unconfirmed.
No independent quantity confirmation.
Winter reveal lists one or multiple distinct new Buggies.
Spider-mount requests predate the current roadmap and intensified around the “New Buggies” slot.
New Buggy families are genuinely planned; Wolf Spider is a community-selected species. Nothing first-party currently links that species to a future Buggy.
Multiple community concepts corroborate demand, not a shipping plan.
Official art, roadmap, PTB, egg/item data or explicit developer reveal.
Players have requested transmog/hide-armour features and later connected those requests to the broad roadmap word “Customization”.
Customization is a real roadmap label and transmog is a real player request, but the roadmap does not define the feature. Equating the two is over-interpretation.
Request → roadmap word association; not independent evidence of the feature identity.
Obsidian explicitly defines Customization as equipment appearance/transmog—or as another system.
A rapid-frame promo image was interpreted as rain; later discussion claims Founder’s art-book material hints at storms.
The rain or storm reading depends on ambiguous visual material and community memory. There is no retained first-party weather plan behind it.
Visual interpretation + community memory; no independent first-party weather plan.
Explicit weather roadmap, developer statement, PTB or live update.
A Steam user says developers discussed this on video, but the thread provides no current Grounded 2 source; another user points to a 2020 Grounded 1 discussion.
No weather plan is public, but “never” is supported only by second-hand recollection of older discussion. That cannot establish a permanent Grounded 2 decision.
Second-hand recollection only; no independent Grounded 2 verification.
A current Grounded 2 developer explicitly rules weather out—or announces it.
Players propose gliders and aerial traversal; Chris Parker also references a glider mod while discussing traversal problems and possible future directions.
Traversal ideas, including a glider reference, have appeared in developer discussion. They remain brainstorming rather than a roadmap commitment.
Developer exploration and community requests overlap, but neither is a shipping commitment.
Roadmap entry, prototype reveal, PTB, live implementation or explicit rejection.
Scorpion mounts appear in Buggy wish lists from August 2025 and remain active in later community concepts.
Scorpion is a recurring fan Buggy idea layered onto the real promise of more Buggies. The species itself has no first-party support.
Generic first-party “new Buggies” intent + repeated community species requests; the species choice remains entirely community-supplied.
Official Buggy reveal, egg/item evidence, PTB, roadmap species label or explicit rejection.
Praying Mantis Buggy concepts become highly visible by May 2026 and recur in mount-role discussion.
Praying Mantis is another popular combat-Buggy concept. Existing creature presence and generic new-Buggy plans do not establish tameability.
Community species concept layered on top of generic first-party new-Buggy intent; no independent species evidence.
Official Buggy reveal, PTB, item/egg data or explicit developer statement.
Grounded 2 has developer-described completion criteria but no official 1.0 date. Version arithmetic, seasonal geography and the original game’s cadence can inform forecasts, not establish them.
Community forecasts commonly place 1.0 in 2027; GamesRadar has editorially described 2027 as expected.
2027 is a reasonable editorial/community forecast based on scope and roadmap pace, but Obsidian has not announced a year. It remains a forecast.
Community forecasting and derivative reporting; no official year confirmation.
An official 1.0 year/date/window.
Players turn Parker’s “mathematically” 50%-of-the-journey framing into literal completion percentages.
Parker’s “mathematically 50%” phrasing is real, but it describes the version/journey framing—not a measured 50% of story, map, labour or time remaining.
A real quote is being over-expanded beyond what it measures.
No special reveal is required: the stronger percentage claim is already unsupported by the quoted framing.
Forecasts treat version increments as evenly sized units of work and extrapolate forward.
Version numbers are not units of calendar time or work. The observed cadence cannot reliably produce a 1.0 date.
Arithmetic extrapolation, not release evidence.
Only an official 1.0 window/date can resolve timing.
After the Year 2 roadmap, players inferred that Winter’s area, story boss and Tier IV progression might complete enough of the park for 1.0.
Winter is a large milestone, but the roadmap still shows undated Future Plans and Parker has not tied Winter to 1.0. The forecast has no official timing support.
Map arithmetic and community forecasting; no independent official timing support.
Obsidian announces Winter as 1.0—or confirms another milestone.
A community comment made the fixed-count claim and was immediately challenged for evidence.
The fixed count has no evidential basis. Current roadmap buckets do not define exactly five remaining seasonal updates.
No corroboration of the underlying update count.
An explicit first-party statement defining the remaining update count.
The most useful question is often not “how many people repeat this?” but “what new evidence entered the chain?” These nine chains show where a real clue ends and community amplification begins.
The chain gets longer without adding independent species evidence. A thematic fit is not a creature reveal.
The arithmetic is tidy, but no first-party version number closes the chain.
Unlike most rumours, this chain contains several independent narrative clues. It is therefore a stronger hypothesis—but still lacks the identity bridge.
This is a misinformation-risk chain: memory of the first game is contaminating claims about the sequel.
The weak link is quantity. Earlier generic plural wording (“Watery Buggies”) ultimately resolved to the singular Toe Biter Buggy.
No first-party source closes the semantic gap between broad customization and armour appearance override.
The detailed concept work is creative elaboration, not additional corroboration.
The main counterweight is the undated Future Plans column, including another hidden area and Abyss expansion.
Only the generic future-Buggy premise is first-party-backed. The species choices remain community design.
Many popular claims have lots of repetition but no independent primary corroboration. This matrix makes that distinction explicit for the highest-interest rumours.
| Claim | Independent primary corroboration? | Secondary corroboration? | Main weakness |
|---|---|---|---|
| Stranger = fifth kid | No identity confirmation | many derivative discussions | missing identity bridge |
| Subject V = fifth kid | No | no independent identity source | wordplay |
| Stranger = Sloane daughter | No | no | no family evidence |
| Stranger = Schmector child | No | no | no family evidence |
| 555 = Stranger | No | no | thematic overlap |
| Stranger controlled Wendell | No | no | controller unnamed |
| Fall = 0.6 | No | repetition only | version extrapolation |
| Rot and Ruin won | No retained winner artifact | consistent community reporting | missing primary result |
| Centipede | No | creator/article repeat same clues | thematic inference |
| Centipede boss | No | derivative | boss status additionally inferred |
| Winter = Sandbox | No | community agreement | hidden area |
| Future = Explosion area | No | community mapping | hidden area |
| Flying Buggy | Developer aspiration only | community demand | aspiration ≠ commitment |
| Weather planned | No | requests only | no roadmap plan |
| New Archetypes cancelled | No | secondary interpretation | disappearance ≠ cancellation |
| 1.0 in 2027 | No | GamesRadar expectation + community | no official year |
| 0.5 = exact halfway | ambiguous developer framing | community estimates | category error |
| Multiple Winter Buggies | roadmap plural only | community speculation | grammar ≠ quantity commitment |
| Wolf Spider Buggy | No | concept/request threads | no named species commitment |
| Armour transmog | No | request threads only | “Customization” is broader |
| Promo/art-book weather clue | No retained direct proof | community visual interpretation | concept/promo ambiguity |
| Scorpion Buggy | No | recurring requests/concepts | no species commitment |
| Mantis Buggy | No | popular concept threads | existing creature ≠ mount plan |
| Sandpit + Antlions | No | forum concept + map speculation | hidden area identity unknown |
| Winter = 1.0 | No | community forecast | Future Plans remain beyond Winter |
| Exactly five updates remain | No | challenged Reddit claim | no first-party count |
| Weather permanently ruled out | No current G2 source | second-hand Steam claim | cited discussion is Grounded 1-era |
These are the future announcements or story reveals that would settle several high-interest claims at once. They are not predictions about what will happen next.
Resolution does not rewrite the past. A datamined idea that later ships was still unconfirmed when first reported; a broad concept can be vindicated while the specific implementation is disproved.
Early implementation was described as bare-bones; file assets do not prove shipping.
RH-DM-001Current roadmap says broad Customization but does not define skins/transmog.
RH-DM-003Datamine cannot prove readiness/intent at that date.
RH-DM-004Early files did not establish final feature scope.
RH-DM-005Could be inherited scaffold rather than production-ready feature.
RH-DM-006No exact final set established from file names.
RH-DM-007Later actual Buggy mutation/progression implementation may differ.
RH-DM-009Later releases introduced Buggy progression mechanics; absence in early files is weak negative evidence.
RH-DM-010Text recovery was uncertain.
RH-DM-012Could have encompassed broader Tang/candy systems.
RH-DM-013Into the Abyss delivered Toe Biter as amphibious Buggy instead; Water Strider could still appear separately.
RH-DM-014Early asset maturity did not predict release timing.
RH-DM-021File presence can reflect prototypes, ported assets, testing variants or cut content.
RH-DM-023File presence can reflect prototypes, ported assets, testing variants or cut content.
RH-DM-024File presence can reflect prototypes, ported assets, testing variants or cut content.
RH-DM-049File presence can reflect prototypes, ported assets, testing variants or cut content.
RH-DM-087File presence can reflect prototypes, ported assets, testing variants or cut content.
RH-DM-088Partial assets are weak commitment evidence.
RH-DM-108Optional deep reference behind the 40-claim core. It preserves datamine reports, requests, forecasts and lower-signal hypotheses without promoting them into established rumours.
The annex includes request-only concepts, duplicate parent claims and one-source file strings. Its value is historical matching: if Obsidian later reveals a feature, Sourceborne can see whether an old signal was genuinely predictive, merely adjacent, or completely wrong.
| Signal | Class | Current state | Evidence context | What resolves it |
|---|---|---|---|---|
| RH-DM-001A base-moving system existed in early game files. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER ROADMAP-CORROBORATED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: UI/logic blueprints reportedly iterated across connected structures and relocated them. Limits: Early implementation was described as bare-bones; file assets do not prove shipping. | Current roadmap already lists Base Moving; live implementation would fully resolve. |
| RH-DM-002New Game+ infrastructure/assets existed in Grounded 2 files at launch. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported Playgrounds and New Game+ widgets/teleporters/RNG trinket infrastructure. Limits: Could be scaffold/ported code from Grounded 1; NG+ is not a current public Grounded 2 feature. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-003Grounded 2 would get player/Buggy selectable skins/customisation. | REPORTED_DATAMINE | REPORTED_DATAMINE — PARTIALLY ROADMAP-CORROBORATED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported UI blueprints that sounded like selectable player/Buggy skins. Limits: Current roadmap says broad Customization but does not define skins/transmog. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-004Ziplines were substantially implemented long before release. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported system looked complete and building pieces referenced zipline interaction. Limits: Datamine cannot prove readiness/intent at that date. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-005PEEP.R 2.0 implementation work existed at launch. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported PEEP.R-related files. Limits: Early files did not establish final feature scope. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-006Coziness infrastructure was already present before its roadmap delivery. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported building/player files resembling the Grounded 1 coziness framework. Limits: Could be inherited scaffold rather than production-ready feature. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-007Expanded base-defense/turret assets existed before roadmap delivery. | REPORTED_DATAMINE | REPORTED_DATAMINE — PARTIALLY DELIVERED/EVOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported a slew of turrets/base-defense objects. Limits: No exact final set established from file names. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-008Active Mutations 2.0 was only a triggered-mutation reliability rework. | REPORTED_DATAMINE | REPORTED_DATAMINE_INTERPRETATION — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer interpreted available files as not supporting dramatic physical mutation. Limits: Interpretation of absent rigging is not proof of design; roadmap item later disappeared. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-009Buggy Mutations would be player-equipped mutations that affect the Buggy. | REPORTED_DATAMINE | REPORTED_DATAMINE_INTERPRETATION — PARTLY SUPERSEDED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer inferred this from current Buggy/player blueprint architecture. Limits: Later actual Buggy mutation/progression implementation may differ. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-010Buggy Progression would not use a talent tree. | REPORTED_DATAMINE | REPORTED_DATAMINE_INTERPRETATION — WEAKENED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer saw no precursor structure for a talent tree. Limits: Later releases introduced Buggy progression mechanics; absence in early files is weak negative evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-011The hidden Winter roadmap area was 'The Playground ...'. | REPORTED_DATAMINE | REPORTED_DATAMINE_OCR HYPOTHESIS — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer attempted redaction reconstruction and matched visible letter forms/assets. Limits: OCR/reconstruction was explicitly uncertain; later roadmap restructuring makes this historical guess non-authoritative. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-012The hidden Summer roadmap area was 'The Pond ...'. | REPORTED_DATAMINE | REPORTED_DATAMINE_OCR HYPOTHESIS — BROADLY RESOLVED BY POND/ABYSS | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reconstructed visible letter forms and water-theme context. Limits: Text recovery was uncertain. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-013Sour 2.0 meant a Sour status-effect implementation. | REPORTED_DATAMINE | REPORTED_DATAMINE_INTERPRETATION — PARTLY SUPERSEDED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer inferred from roadmap wording and file state. Limits: Could have encompassed broader Tang/candy systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-014Water Strider was intended as the original water Buggy. | REPORTED_DATAMINE | REPORTED_DATAMINE_IMPLEMENTATION HYPOTHESIS — CONTRADICTED AS DELIVERED WATER BUGGY | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Specific Water Strider files plus roadmap water-Buggy context led dataminer to this conclusion. Limits: Into the Abyss delivered Toe Biter as amphibious Buggy instead; Water Strider could still appear separately. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-015A unique early T4 weapon asset foreshadowed a Summer creature/update. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer saw one uniquely designated weapon tied to a likely future creature. Limits: Asset identity was not specified and cannot be reliably mapped now. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-016Launch files reportedly referenced Rust Beetle Armor through item/equipment assets. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: armor files referenced an unimplemented Rust Beetle Limits: Unused/placeholder/ported assets are possible; item is not a first-party release commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-017Launch files reportedly referenced Potato Bug Armor through item/equipment assets. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: armor files referenced an unimplemented Potato Bug Limits: Unused/placeholder/ported assets are possible; item is not a first-party release commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-018Launch files reportedly referenced Killer Bee Armor through item/equipment assets. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: separate armor set from standard Bee Armor Limits: Unused/placeholder/ported assets are possible; item is not a first-party release commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-019Launch files reportedly referenced Silverfish Shield through item/equipment assets. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: shield file referenced otherwise-unimplemented Silverfish Limits: Unused/placeholder/ported assets are possible; item is not a first-party release commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-020Launch files reportedly contained development assets for Mosquito Buggy/saddle. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer found a Mosquito Saddle icon. Limits: Icon alone does not prove a functioning or scheduled Buggy. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-021Launch files reportedly contained development assets for Ladybug Buggy/saddle. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer found Ladybug Saddle icon; roadmap independently listed Ladybug Buggy. Limits: Early asset maturity did not predict release timing. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-022Launch files reportedly contained development assets for Wolf Spider Buggy/saddle. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer found Wolf Spider saddle/material refs and Buggy animation/behaviour sets. Limits: Could be prototype/test scaffold; no current first-party Wolf Spider Buggy plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-023Launch files were reported to contain substantial assets for Black Ant Worker. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED/CONFIRMED IN SOME FORM | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Black Ant Worker. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-024Launch files were reported to contain substantial assets for Black Ant Soldier. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED/CONFIRMED IN SOME FORM | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Black Ant Soldier. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-025Launch files were reported to contain substantial assets for Red Ant Soldier O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Red Ant Soldier O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-026Launch files were reported to contain substantial assets for Fire Ant Worker. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Fire Ant Worker. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-027Launch files were reported to contain substantial assets for Fire Ant Soldier. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Fire Ant Soldier. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-028Launch files were reported to contain substantial assets for Fire Ant Soldier O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Fire Ant Soldier O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-029Launch files were reported to contain substantial assets for Antlion (Pit). | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Antlion (Pit). Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-030Launch files were reported to contain substantial assets for Antlion (Roamer). | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Antlion (Roamer). Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-031Launch files were reported to contain substantial assets for Bee. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Bee. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-032Launch files were reported to contain substantial assets for Bee O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Bee O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-033Launch files were reported to contain substantial assets for Black Ox Beetle. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Black Ox Beetle. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-034Launch files were reported to contain substantial assets for Black Ox Beetle O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Black Ox Beetle O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-035Launch files were reported to contain substantial assets for Blue Butterfly. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Blue Butterfly. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-036Launch files were reported to contain substantial assets for Blue Butterfly O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Blue Butterfly O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-037Launch files were reported to contain substantial assets for Bombardier Beetle. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Bombardier Beetle. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-038Launch files were reported to contain substantial assets for Bombardier Beetle O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Bombardier Beetle O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-039Launch files were reported to contain substantial assets for Caterpillar. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Caterpillar. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-040Launch files were reported to contain substantial assets for Cockroach Nymph. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Cockroach Nymph. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-041Launch files were reported to contain substantial assets for Cockroach Nymph O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Cockroach Nymph O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-042Launch files were reported to contain substantial assets for Cockroach. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Cockroach. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-043Launch files were reported to contain substantial assets for Cockroach O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Cockroach O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-044Launch files were reported to contain substantial assets for Scarab Beetle. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Scarab Beetle. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-045Launch files were reported to contain substantial assets for Diving Bell Spider. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Diving Bell Spider. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-046Launch files were reported to contain substantial assets for Fly. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Fly. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-047Launch files were reported to contain substantial assets for Infected Gnat. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Infected Gnat. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-048Launch files were reported to contain substantial assets for Big/Giant Gnat. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Big/Giant Gnat. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-049Launch files were reported to contain substantial assets for Ladybug. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED/CONFIRMED IN SOME FORM | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Ladybug. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-050Launch files were reported to contain substantial assets for Ladybug O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Ladybug O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-051Launch files were reported to contain substantial assets for Infected Ladybug. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Infected Ladybug. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-052Launch files were reported to contain substantial assets for Larva. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Larva. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-053Launch files were reported to contain substantial assets for Larva O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Larva O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-054Launch files were reported to contain substantial assets for Ladybird Larva. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Ladybird Larva. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-055Launch files were reported to contain substantial assets for Leech. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Leech. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-056Launch files were reported to contain substantial assets for Green Mantis. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Green Mantis. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-057Launch files were reported to contain substantial assets for Praying Mantis. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Praying Mantis. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-058Launch files were reported to contain substantial assets for Praying Mantis O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Praying Mantis O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-059Launch files were reported to contain substantial assets for Dust Mite. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Dust Mite. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-060Launch files were reported to contain substantial assets for Tick. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Tick. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-061Launch files were reported to contain substantial assets for Mosquito. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Mosquito. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-062Launch files were reported to contain substantial assets for Mosquito O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Mosquito O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-063Launch files were reported to contain substantial assets for Tiger Mosquito. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Tiger Mosquito. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-064Launch files were reported to contain substantial assets for Moth. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Moth. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-065Launch files were reported to contain substantial assets for Roly Poly. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Roly Poly. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-066Launch files were reported to contain substantial assets for Sickly Roly Poly. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Sickly Roly Poly. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-067Launch files were reported to contain substantial assets for Scorpling. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Scorpling. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-068Launch files were reported to contain substantial assets for Scorpling O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Scorpling O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-069Launch files were reported to contain substantial assets for Scorpion Jr. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Scorpion Jr. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-070Launch files were reported to contain substantial assets for Scorpion Jr O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Scorpion Jr O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-071Launch files were reported to contain substantial assets for Scorpion O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Scorpion O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-072Launch files were reported to contain substantial assets for Northern Scorpion. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Northern Scorpion. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-073Launch files were reported to contain substantial assets for Northern Scorpion Jr. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Northern Scorpion Jr. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-074Launch files were reported to contain substantial assets for Snail. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Snail. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-075Launch files were reported to contain substantial assets for Spiderling. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Spiderling. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-076Launch files were reported to contain substantial assets for Spiderling O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Spiderling O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-077Launch files were reported to contain substantial assets for Black Widow. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Black Widow. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-078Launch files were reported to contain substantial assets for Infected Wolf Spider. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Infected Wolf Spider. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-079Launch files were reported to contain substantial assets for Wolf Spider O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Wolf Spider O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-080Launch files were reported to contain substantial assets for Orb Weaver Jr O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Orb Weaver Jr O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-081Launch files were reported to contain substantial assets for Orb Weaver O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Orb Weaver O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-082Launch files were reported to contain substantial assets for Stinkbug O.R.C.. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Stinkbug O.R.C.. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-083Launch files were reported to contain substantial assets for Green Shield Bug. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Green Shield Bug. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-084Launch files were reported to contain substantial assets for Tadpole. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Tadpole. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-085Launch files were reported to contain substantial assets for Taz-T ARC-R variant. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Taz-T ARC-R variant. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-086Launch files were reported to contain substantial assets for Taz-T TAZ-R variant. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Taz-T TAZ-R variant. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-087Launch files were reported to contain substantial assets for Termite Soldier. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED/CONFIRMED IN SOME FORM | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Termite Soldier. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-088Launch files were reported to contain substantial assets for Termite Worker. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED/CONFIRMED IN SOME FORM | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Termite Worker. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-089Launch files were reported to contain substantial assets for Wasp. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Wasp. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-090Launch files were reported to contain substantial assets for Water Boatman. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Water Boatman. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-091Launch files were reported to contain substantial assets for Water Flea. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Water Flea. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-092Launch files were reported to contain substantial assets for Upper Yard Water Flea. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Upper Yard Water Flea. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-093Launch files were reported to contain substantial assets for Water Strider. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Water Strider. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-094Launch files were reported to contain substantial assets for Infected Weevil. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported complete or substantial blueprint/animation/material assets for Infected Weevil. Limits: File presence can reflect prototypes, ported assets, testing variants or cut content. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-095Launch files were reported to contain boss/special assets for Fire Ant Queen boss. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Fire Ant Queen boss. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-096Launch files were reported to contain boss/special assets for Cockroach Queen boss. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Cockroach Queen boss. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-097Launch files were reported to contain boss/special assets for O.R.C. Cockroach Queen boss. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for O.R.C. Cockroach Queen boss. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-098Launch files were reported to contain boss/special assets for ARC-R MKII boss. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for ARC-R MKII boss. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-099Launch files were reported to contain boss/special assets for Mant. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Mant. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-100Launch files were reported to contain boss/special assets for Wasp Queen. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Wasp Queen. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-101Launch files were reported to contain boss/special assets for Termite King. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED; FALL TERMITES NOW OFFICIAL BUT KING NOT CONFIRMED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Termite King. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-102Launch files were reported to contain boss/special assets for Red Ant Queen ambient event. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Red Ant Queen ambient event. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-103Launch files were reported to contain boss/special assets for Black Ant Queen ambient event. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Black Ant Queen ambient event. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-104Launch files were reported to contain boss/special assets for Crow ambient creature. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Crow ambient creature. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-105Launch files were reported to contain boss/special assets for Koi Fish ambient/colossus-like creature. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Koi Fish ambient/colossus-like creature. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-106Launch files were reported to contain boss/special assets for Lizard Boss / 'Limerick'. | REPORTED_DATAMINE | REPORTED_DATAMINE — BROADLY CORROBORATED BY LATER HORNED-LIZARD BOSS; EXACT CODENAME MAPPING UNPROVEN | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Lizard Boss / 'Limerick'. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-107Launch files were reported to contain boss/special assets for Broodmother/Test01. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED/ASSET MAY BE UNUSED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported boss/special spawn/drop/logic assets for Broodmother/Test01. Limits: File-derived boss labels can be placeholders, tests or inherited systems. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-108Unimplemented Earwig assets signalled eventual Earwig content. | REPORTED_DATAMINE | REPORTED_DATAMINE — LATER DELIVERED/CONFIRMED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported partial assets or equipment references for Earwig. Limits: Partial assets are weak commitment evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-109Unimplemented Rust Beetle assets signalled eventual Rust Beetle content. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported partial assets or equipment references for Rust Beetle. Limits: Partial assets are weak commitment evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-110Unimplemented Potato Bug assets signalled eventual Potato Bug content. | REPORTED_DATAMINE | REPORTED_DATAMINE — POTATO FAMILY NOW ROADMAP-CORROBORATED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported partial assets or equipment references for Potato Bug. Limits: Partial assets are weak commitment evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-111Unimplemented Killer Bee assets signalled eventual Killer Bee content. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported partial assets or equipment references for Killer Bee. Limits: Partial assets are weak commitment evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-DM-112Unimplemented Silverfish assets signalled eventual Silverfish content. | REPORTED_DATAMINE | REPORTED_DATAMINE — UNRESOLVED | Origin: DM01 — 30 Jul 2025 early file-structure/datamine post Support: Dataminer reported partial assets or equipment references for Silverfish. Limits: Partial assets are weak commitment evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| Signal | Class | Current state | Evidence context | What resolves it |
|---|---|---|---|---|
| RH-CR-001Grasshopper | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-002Locust | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-003Jumping Spider | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-004Daddy Long Legs | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-005Trapdoor Spider | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-006House Centipede | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-007Brown Centipede boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-008Mouse | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-009Rat boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-010Hornet | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-011Monarch Butterfly | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-012Squirrel colossus/non-killable | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-013House Finch colossus/non-killable | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-014Frog | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-015Toad boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-016Catfish colossus/non-killable | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-017Dragonfly | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-018Venus Fly Trap | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-019Hercules Beetle boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-020Stag Beetle | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-021Crab Spider | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-022Huntsman Spider | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-023Brown Recluse Spider | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-024Minnow | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-025Flea | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-026Stick Bug | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-027Black Scorpion boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-028Salamander | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-029Generic Beetle | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-030Pink-Spotted Lady Beetle | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-031Earthworm | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-032Maggots | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR01 — 13 Nov 2025 Obsidian Feedback 'New bugs and creatures for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-033Leaf-cutter Ant | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-034Horse Fly boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-035Kissing Bug | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-036Rhino Beetle | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-037Dung Beetle | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-038Cicada mini-boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-039Dart Frog boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-040Tarantula Hawk mega-boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-041Broken Sprinkler/rain location | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-042Lice as resource creature | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR02 — Obsidian Feedback 'My Suggestions for Grounded 2 content' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-043Spiny Orb Weaver Broodmother variant | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR03 — 25 Aug 2025 Obsidian Feedback 'More bugs for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-044Golden Silk Orb Weaver Broodmother variant | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR03 — 25 Aug 2025 Obsidian Feedback 'More bugs for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-045Seven-Spotted Ladybug boss 'Lady Liberty' | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR03 — 25 Aug 2025 Obsidian Feedback 'More bugs for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-046O.R.C. Yellow Jacket boss 'Sargent Buzzerker' | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR03 — 25 Aug 2025 Obsidian Feedback 'More bugs for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-047Fountain area expansion | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR03 — 25 Aug 2025 Obsidian Feedback 'More bugs for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-048Brown Centipede log boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR04 — Feb 2026 Obsidian Feedback 'New Bosses for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-049Rat sewer boss | REQUEST/HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS/REQUEST | Origin: CR04 — Feb 2026 Obsidian Feedback 'New Bosses for Grounded 2' Support: Fits ecosystem/franchise or current generic roadmap promise of new creatures. Limits: No first-party commitment; roadmap/category fit alone is insufficient. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-050Roly Poly return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-051Green Shield Bug return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-052Moth return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-053Black Ox Beetle return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-054Tick return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-055Black Widowling | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-056Black Widow return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-057Fire Ant Worker return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-058Fire Ant Soldier return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-059Scarab return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-060Tiger Mosquito return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-061Spiny Water Flea | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-062Ladybird return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-063Ladybird Larva return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-064Dust Mite return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-065Ant Queen encounter | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-066Wasp Queen return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-067Orchid/Adult Mantis return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-068TAYZ.T/robot enemies return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-069Infected Larva return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-070Infected Weevil return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-071Infected Mite return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-072Infected Wolf Spider return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-073Infected Ant variant | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-074Infected Ant Soldier | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-075Infected Broodmother | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-076Infected Ant Queen | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-077O.G.R.R. Mant-like hybrid | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-078O.R.C. Wasp Queen variant | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-079Haze fungus/cordyceps return | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-080Radioactive/infected zone | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-081Infected Scorpion | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-CR-082Infected human or human-sized infection story | COMMUNITY_HYPOTHESIS | RECURRING COMMUNITY RETURN HYPOTHESIS | Origin: CR05 — recurring Reddit creature-return/tier-list and infected-content discussions Support: Grounded 1 precedent and/or file-derived assets provide thematic support. Limits: No current first-party commitment; sequel may replace old creatures/systems with new equivalents. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| Signal | Class | Current state | Evidence context | What resolves it |
|---|---|---|---|---|
| RH-BG-001Bee Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-002Wasp Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-003Butterfly Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-004Moth Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-005Dragonfly Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-006Mosquito Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-007Wolf Spider Buggy | CORE_DUPLICATE → RH-SYS-008 | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-008Black Widow Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-009Scorpion Buggy | CORE_DUPLICATE → RH-SYS-011 | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-010Praying Mantis Buggy | CORE_DUPLICATE → RH-SYS-012 | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-011Cockroach Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-012Bombardier Beetle Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-013Rust Beetle Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-014Earwig Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-015Grasshopper Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-016Cricket Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-017Jumping Spider Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-018Antlion Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-019Roly Poly Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-020Caterpillar cargo Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-021Firefly Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-022Glowworm Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-023Water Strider Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-024Diving Bell Spider Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-025Larva Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-026Hornet Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-027Cicada Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-028Locust Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-029Fire Ant Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-030Black Ox Beetle Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-031Flea Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-032Stick Bug Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-033Frog/amphibious Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-034Millipede multi-passenger Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-035Centipede multi-passenger Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-036Bumblebee limited-flight Buggy | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-037Worker-ant hauling team/cart | REQUEST/HYPOTHESIS | COMMUNITY BUGGY HYPOTHESIS/REQUEST | Origin: BI01–BI06 — recurring Reddit/Obsidian Buggy wish-list threads Support: Roadmap/developer confirms more Buggies/new Buggy families generally. Limits: No first-party species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-038Mosquito Buggy specifically because of launch-file saddle/behaviour assets | REPORTED_DATAMINE | DATAMINED BUGGY HYPOTHESIS | Origin: DM01 — 30 Jul 2025 datamine Support: Specific saddle/behaviour assets reportedly existed. Limits: Assets may be prototypes/cut; no official species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-BG-039Wolf Spider Buggy specifically because of launch-file saddle/behaviour assets | REPORTED_DATAMINE | DATAMINED BUGGY HYPOTHESIS | Origin: DM01 — 30 Jul 2025 datamine Support: Specific saddle/behaviour assets reportedly existed. Limits: Assets may be prototypes/cut; no official species commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| Signal | Class | Current state | Evidence context | What resolves it |
|---|---|---|---|---|
| RH-FT-001New Game+ will return in Grounded 2 | REPORTED_DATAMINE | DATAMINED/COMMUNITY HYPOTHESIS | Origin: DM01 + NG01 — datamined NG+ infrastructure and later completionist discussions Support: Grounded 1 precedent plus launch-file infrastructure. Limits: No current Grounded 2 roadmap commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-002Story replay / mission replay will be added | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: NG01 — Mar 2026 NG+ discussion Support: Would solve missable encounter/card issues. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-003A major story reset will occur during Early Access | COMMUNITY_FORECAST | COMMUNITY FORECAST | Origin: NG01 — Mar 2026 Reddit discussion Support: Grounded 1 Early Access changed story progression. Limits: No Grounded 2 announcement. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-004Base Moving means entire connected bases can be relocated | REPORTED_DATAMINE | DATAMINED + OFFICIAL-PLAN INTERPRETATION | Origin: DM01 + current roadmap Support: Early UI/logic assets reportedly support connected-structure relocation; roadmap says Base Moving. Limits: Exact final mechanic unknown. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-005Base Moving means a mobile base carried by a Colossus | COMMUNITY_HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: FEAT05 — community roadmap speculation Support: Base Moving + Colossi invites mobile-base interpretation. Limits: No primary evidence linking them. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-006Player/Buggy cosmetic skins are planned | REPORTED_DATAMINE | DATAMINED/ROADMAP INTERPRETATION | Origin: DM01 + roadmap Customization Support: UI files reportedly suggested selectable skins. Limits: Customization is broad. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-007Armour transmog/hide armour is planned | COMMUNITY_REQUEST | COMMUNITY REQUEST/ROADMAP OVER-INTERPRETATION | Origin: C30/C31/C32 Support: Strong demand + Customization label. Limits: No explicit transmog statement. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-008Archetype skill trees will be added | COMMUNITY_HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: FEAT06 — community suggestion threads Support: Archetype system could support deeper progression. Limits: No current roadmap label. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-009Summoner archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH01 Support: Earlier roadmap promised New Archetypes. Limits: New Archetypes disappeared from current roadmap. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-010Cleric/Healer archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH01 Support: Healing/support niche. Limits: New Archetypes absent. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-011Bard archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH01 Support: Support niche. Limits: New Archetypes absent. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-012Barbarian archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH01 Support: Two-handed damage niche. Limits: New Archetypes absent. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-013Monk archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH01 Support: Unarmed/mobility niche. Limits: New Archetypes absent. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-014Druid archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH01 Support: Summon/heal niche. Limits: New Archetypes absent. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-015Artificer/Tinkerer archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH02 — archetype discussions Support: Tech/build niche. Limits: No first-party evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-016Paladin/Knight archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH02 — archetype discussions Support: Tank/support niche. Limits: No first-party evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-017Swordsman/Blade DPS archetype | COMMUNITY_PREDICTION | HISTORICAL COMMUNITY ARCHETYPE PREDICTION | Origin: ARCH02 — archetype discussions Support: Weapon-specialist niche. Limits: No first-party evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-018Sub-archetypes / D&D-style subclasses | COMMUNITY_HYPOTHESIS | COMMUNITY SYSTEM HYPOTHESIS | Origin: ARCH01/ARCH02 Support: Current soft archetypes resemble RPG roles. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-019Bug pets will return | REQUEST/HYPOTHESIS | RECURRING COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT04 + many Reddit requests Support: Grounded 1 precedent. Limits: Buggies may replace some pet use cases. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-020Aphid/Gnat rare-color utility pets | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT04 Support: Grounded 1 pets + arrow retrieval utility. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-021Bug farming/ranching for food/materials | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT04/FEAT03 Support: Existing taming/hatchery loops. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-022Insect breeding system | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT03 Support: Hatchery/egg systems provide thematic foundation. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-023Hybrid/fusion insects (Spider-Ants, Beetle-Bees, Aphid-Spiders) | COMMUNITY_CONCEPT | LOW-SIGNAL COMMUNITY CONCEPT | Origin: FEAT03 Support: O.G.R.R. genetics makes it thematically plausible. Limits: Pure user pitch; no developer signal. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-024Pet/Buggy specialization classes (Tank/Scout/DPS/Utility) | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT03 Support: Buggies already have role differentiation. Limits: No explicit class system. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-025Bug workers will harvest/defend bases autonomously | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT03/FEAT02 Support: Buggies/pets could support automation. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-026Bug army / recruitable base-defense swarm | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT01/FEAT03 Support: O.R.C./taming systems exist. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-027Pets/Buggies will man base turrets | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT07 — wishlist discussion Support: Base-defense and tame systems could combine. Limits: No evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-028Farming/crop plots/miniature vegetables | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT03/FEAT08 Support: Garden area and cooking systems. Limits: No roadmap crop system. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-029Snail/slime farming | COMMUNITY_REQUEST | LOW-SIGNAL COMMUNITY REQUEST | Origin: FEAT08 — farming ideas Support: Snail asset/community interest. Limits: No plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-030Dynamic world events such as sprinklers/mowers/storms | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT09 — wishlist threads Support: Park setting supports it. Limits: No roadmap commitment. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-031Weather machine controlled through chips | COMMUNITY_CONCEPT | LOW-SIGNAL COMMUNITY CONCEPT | Origin: FEAT10 — Obsidian forum future-updates discussion Support: Science-fiction setting can support artificial weather. Limits: User pitch only. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-032Full-size kid/human invasion events | COMMUNITY_CONCEPT | LOW-SIGNAL COMMUNITY CONCEPT | Origin: FEAT01 Support: Scale fantasy fits franchise. Limits: No developer evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-033Bug diplomacy/reputation system | COMMUNITY_CONCEPT | LOW-SIGNAL COMMUNITY CONCEPT | Origin: FEAT01 Support: Faction/taming systems exist. Limits: No first-party evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-034Walkie-talkies / long-range comms | COMMUNITY_REQUEST | LOW-SIGNAL COMMUNITY REQUEST | Origin: FEAT01 Support: Co-op utility. Limits: No plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-035Motion sensors / bug radar | COMMUNITY_REQUEST | LOW-SIGNAL COMMUNITY REQUEST | Origin: FEAT01 Support: Tech/building theme. Limits: No plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-036Grappling hook traversal | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT11 — community wishlist Support: Vertical park exploration. Limits: No official plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-037Drone traversal/scouting | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT11 Support: Tech/scouting fit. Limits: No official plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-038Tree dungeon / giant vertical tree area | COMMUNITY_CONCEPT | COMMUNITY MAP CONCEPT | Origin: FEAT11 Support: Large landmarks encourage vertical dungeons. Limits: No roadmap identity. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-039Player-made dungeons accessible from Survival worlds | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT02 Support: Playgrounds supports user creation. Limits: No first-party Survival integration plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-040Matchmaking for user-created dungeons | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT02 Support: Playgrounds/community content. Limits: No first-party plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-041Six-player co-op because Ranger Stations contain six Omni-Tools | COMMUNITY_HYPOTHESIS | COMMUNITY NUMEROLOGY/FEATURE HYPOTHESIS | Origin: STORY04 Support: Six tools prompt quantity inference. Limits: Current official co-op/player structure does not establish six players. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-042Two additional playable characters | COMMUNITY_HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: STORY04 Support: Six Omni-Tool visual clue. Limits: No character announcement. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-043Fifth kid becomes playable | COMMUNITY_HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: STORY04 Support: Would fit unresolved fifth-kid story. Limits: No gameplay evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-044Wendell becomes playable | COMMUNITY_HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: STORY04 Support: Fan desire + adult story role. Limits: No evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-045Create-a-character/custom teen | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: STORY04/FEAT12 Support: Customization demand. Limits: Story is written around named teens. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-046Local/split-screen co-op added later | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT13 — recurring request Support: Player demand. Limits: Official FAQ currently says local/offline co-op unsupported. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-047PvP expands beyond Playgrounds into Survival | COMMUNITY_HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: FEAT14 — community speculation Support: PvP/network code exists in Playgrounds. Limits: No first-party Survival-PvP plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-048Boss eggs unlock boss Buggies | COMMUNITY_HYPOTHESIS | LOW-SIGNAL COMMUNITY HYPOTHESIS | Origin: FEAT15 — community concept Support: Current Buggy acquisition uses eggs/taming. Limits: Boss tameability not established. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-049Multiple Buggies can be summoned/managed simultaneously | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT16 — Buggy request threads Support: More Buggies/progression planned. Limits: Current systems constrain usage. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-050Buggies receive armour/barding equipment | REQUEST/HYPOTHESIS | COMMUNITY REQUEST/HYPOTHESIS | Origin: FEAT16 Support: Customization/progression roadmap. Limits: No explicit armour slot plan. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-051Buggy skill trees are coming | COMMUNITY_HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: FEAT16 Support: More Buggy Progression planned. Limits: Existing progression does not prove trees. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-052Buggy feeding grants temporary buffs | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT16 Support: Food/taming loops. Limits: No evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| RH-FT-053Buggies will patrol/gather while player is away | COMMUNITY_REQUEST | COMMUNITY REQUEST | Origin: FEAT16 Support: Worker/pet automation demand. Limits: No evidence. | Official roadmap/PTB/live build, direct developer statement, or explicit rejection. |
| Signal | Class | Current state | Evidence context | What resolves it |
|---|---|---|---|---|
| RH-ST-001The fifth kid taught the protagonists how to tame Buggies. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY01 — 16 Jul 2025 crackpot fifth-kid theory Support: Would make fifth kid a wilderness-survivor mentor and explains Buggy emphasis. Limits: Current playable Buggy systems do not establish fifth-kid involvement. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-002The fifth kid has been fighting Ominent continuously for two years. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY05 — prelaunch fifth-kid villain/war theory Support: Explains anti-Ominent skills and resentment. Limits: No direct timeline bridge. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-003The fifth kid was never embiggened after Grounded 1. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY05/STORY01 Support: Explains survival expertise and resentment. Limits: No direct evidence; could have been re-shrunk later. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-004The fifth kid was recovered by Ominent and trained/experimented on. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY06 — community identity theories Support: Would explain tech access and missing-person silence. Limits: No personnel record. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-005The Stranger is Sarah Tully. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY07 — Stranger identity roundups/discussion Support: Tully family creates narrative tie. Limits: Age/history conflicts and no direct evidence. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-006The Stranger is Trudy Tully. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY07 Support: Tully-family thematic link. Limits: Age/appearance and narrative role conflict; no evidence. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-007The Stranger is an alternate-timeline/dimension Hoops. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY07 Support: Similarity/knowledge theories. Limits: No alternate-timeline mechanics established. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-008The Stranger is the Employee-of-the-Month Raw Science woman. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY02 — 31 Jul 2025 portrait theory Support: Portrait lacks death date; Raw Science expertise; resemblance theories. Limits: No identity bridge; later Employee 555 material complicates mapping. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-009The Stranger is one of the earlier Ominent teen-trial subjects, but not the fifth kid. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY07/community theory Support: Ominent conducted teen trials. Limits: No subject record identifying her. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-010The Stranger is 'Ash Ferngrass of the Green Army'. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY07/community-name claim Support: Community attempts to match stray names/lore. Limits: No authoritative identity support located. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-011The teens begin Grounded 2 as Ominent agents/employees. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY03 — 9 Jun 2025 theory Support: Trailer showed Ominent-linked gear and corporation rebrand. Limits: Released story framing is more complicated; gear does not prove employment. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-012A rogue Ominent operative recruited the teens to solve the park crisis. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY03 Support: Blue-Umbrella-style theory fits reformed-corporation framing. Limits: No direct recruiter evidence. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-013Ominent is only pretending to be reformed after Grounded 1. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY05/STORY03 recurring theory Support: Secret Park Project and harmful experiments support continued wrongdoing. Limits: Institutional motives are multi-layered; 'pretending' is motive inference. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-014Sloane is the true main villain rather than the Stranger. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY06/community theory Support: Sloane authorises troubling research; Stranger fights Ominent. Limits: Current story has not resolved antagonist hierarchy. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-015Sloane manipulated/created the Stranger as a weapon. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY06 Support: Park Project genetics + profile monitoring. Limits: No causal evidence. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-016Wendell decapitated BURG.L to protect data from Ominent/Stranger. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY08 — BURG.L-head theories Support: Decapitation may be deliberate defensive act. Limits: Control clue suggests Wendell may not be acting voluntarily. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-017The Stranger stole BURG.L's head for its memories/data. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY08/community lore theory Support: Head remains story-important; Stranger targets Ominent/Tully tech. Limits: No explicit motive. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-018The ceremony explosion was an attempted assassination of the teens/Tully. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY09 — ceremony theories Support: Public event concentrates targets. Limits: No perpetrator or target established. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-019The ceremony explosion was caused by Raw Science reservoir instability. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY09/Into Abyss synthesis Support: Raw Science instability exists in park. Limits: No direct spatial/causal bridge. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-020The teens were deliberately re-shrunk to lure or control the Stranger. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY09 Support: Could fit Ominent manipulation. Limits: No evidence. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-021The teens were re-shrunk accidentally by the ceremony blast. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY09 Support: Simple causal adjacency. Limits: No direct mechanism. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-022Subject V is 'Violet'. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: C25 — community shorthand Support: V initial invites name completion. Limits: No canonical name reveal. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-023Subject V means 'Subject Five' rather than a name initial. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: C02/community interpretation Support: Roman numeral V = five and fifth-kid thread. Limits: Could be codename/variable/initial. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| RH-ST-024The Stranger's mask/headpiece comes from or foreshadows an endgame spider/boss. | COMMUNITY_HYPOTHESIS | COMMUNITY STORY HYPOTHESIS | Origin: STORY10 — 23 Jul 2025 trailer-symbol theory Support: Headpiece/graffiti motif and controlled insects sparked pet-boss guesses. Limits: Visual motif does not identify equipment origin. | Explicit in-game identity/plot reveal or first-party developer confirmation. |
| Signal | Class | Current state | Evidence context | What resolves it |
|---|---|---|---|---|
| RH-RL-0011.0 launches at Christmas 2026 | COMMUNITY_FORECAST/HYPOTHESIS | SPECULATIVE FORECAST | Origin: REL01 — community date guesses Support: Perceived roadmap pace. Limits: Future Plans extend beyond Winter; no date. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-0021.0 launches in summer 2027 | COMMUNITY_FORECAST/HYPOTHESIS | SPECULATIVE FORECAST | Origin: REL01 Support: Two-year G1 Early Access precedent / roadmap pace. Limits: No official year. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-0031.0 launches in 2028 | COMMUNITY_FORECAST/HYPOTHESIS | SPECULATIVE FORECAST | Origin: REL01 Support: Larger sequel scope and Future Plans. Limits: No official timing. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-0041.0 immediately follows the Winter update | COMMUNITY_FORECAST/HYPOTHESIS | COMMUNITY FORECAST | Origin: RH-REL-004 cluster Support: Winter has story boss/Tier IV/new area. Limits: Future Plans remain undated afterward. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-005New Game+ arrives only after 1.0 | COMMUNITY_FORECAST/HYPOTHESIS | COMMUNITY FORECAST | Origin: NG01 + Grounded 1 precedent Support: NG+ logically follows completed story. Limits: Launch-file assets do not prove timing. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-006Grounded 2 gets Grounded 1-style Remix/New Game+ loops | COMMUNITY_FORECAST/HYPOTHESIS | DATAMINED/FRANCHISE HYPOTHESIS | Origin: DM01/NG01 Support: NG+ infrastructure reportedly exists and G1 precedent. Limits: No public G2 commitment. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-007Story progress will reset at 1.0 but bases/buildings will remain | COMMUNITY_FORECAST/HYPOTHESIS | REPORTED SUPPORT CLAIM — PRIMARY NOT RETAINED | Origin: REL02 — reported Obsidian Support response Support: Community post attributes answer to support. Limits: Support response not independently retained; policy may change. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-008All Early Access saves will wipe at 1.0 | COMMUNITY_FORECAST/HYPOTHESIS | UNSUPPORTED FORECAST | Origin: Community fear/speculation Support: Early Access can change saves. Limits: No official wipe policy; opposite support report circulates. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-009No Early Access saves will ever need reset | COMMUNITY_FORECAST/HYPOTHESIS | UNSUPPORTED FORECAST | Origin: Community reassurance/speculation Support: Obsidian aims for continuity. Limits: No guarantee. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-010Tier V Omni-Tools arrive at 1.0 | COMMUNITY_FORECAST/HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: REL03 — community progression extrapolation Support: Tier IV staging suggests later tiers possible. Limits: No roadmap Tier V. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-011More than four playable characters arrive before/at 1.0 | COMMUNITY_FORECAST/HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: STORY04/6 Omni-Tools Support: Six Omni-Tools clue. Limits: No platform/player-count announcement. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-012Six-player co-op arrives | COMMUNITY_FORECAST/HYPOTHESIS | COMMUNITY HYPOTHESIS | Origin: STORY04 Support: Six Omni-Tools visual. Limits: Current game/player architecture does not establish six-player support. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-013Achievements/trophies arrive before 1.0 | COMMUNITY_FORECAST/HYPOTHESIS | CONTRADICTED BY CURRENT DEVELOPER PLAN | Origin: Community request Support: Players want them. Limits: Parker says planned for 1.0. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-014PS5 Pro Enhanced patch arrives before 1.0 | COMMUNITY_FORECAST/HYPOTHESIS | SPECULATIVE TIMING | Origin: Community platform expectation Support: Parker intends label by 1.0. Limits: No earlier date. | Official Obsidian/Xbox/Steam release or policy statement. |
| RH-RL-015UE 5.7 migration is the Fall update / version 0.6 | COMMUNITY_FORECAST/HYPOTHESIS | COMMUNITY/TECHNICAL HYPOTHESIS | Origin: Technical extrapolation Support: Parker says migration follows Into the Abyss. Limits: No version/date specified. | Official Obsidian/Xbox/Steam release or policy statement. |
First-party material establishes plans and current facts. Community sources establish the origin or circulation of a theory—not its truth. The wider signal annex preserves its earliest located source text in each row.
Provenance discipline: community posts hosted on Obsidian forums remain community sources unless authored by Obsidian staff. Creator videos, articles and repeated posts do not count as independent corroboration when they recycle the same underlying theory.