Sources and editorial method
Gameplay claims use the official experience, its public records and dated video observations. We separate reported code availability, store descriptions and promotional art from personal playtesting.
Player-facing sources
Developer description and game identity · October 7 snapshot
Official creator community · October 7 snapshot
Seven published effects and prices · October 7 snapshot
Three enabled badges and their requirements · October 7 snapshot
Egg names and visual identity; printed figures are promotional
Uploaded October 6 · selected frames inspected October 8
Five Active reports reviewed October 8. The strings and reward descriptions are publisher reports, without developer confirmation or personal redemption. The codes page keeps this label beside each report.
How the answers are produced
The local Roblox site Agent workflow profiles the game, researches player tasks, collects public data and prepares original explanations. An independent review checks the resulting pages and their source boundaries. Using an Agent does not make a reported value automatically correct or turn this into an official Roblox resource.
October 7 official snapshots establish the game identity, description, three badge records and seven Game Pass descriptions. A beginner video uploaded October 6 was inspected on October 8 at selected timestamps, including training, carrying, plot countdowns and a visible pet-income label. No personal in-game run is claimed.
Code status is based on an attributable publisher's current Active listing. Its reward descriptions are publisher reports, not developer-confirmed quantities. Competitor pages are used for research internally; public navigation points players to the actual game and substantive guide pages.
We do not invent mutation probabilities, complete egg rosters, game-event schedules, stacking formulas, exact unobserved controls or contact addresses. Source timestamps stay attached to values that can change.