Identity and announcements
The Roblox experience, group and event pages are the first source for place identity, public mechanics, displayed codes, update dates and scheduled events.
Data methodology
A practical evidence ladder for a fast-changing Roblox game: official first, current-patch observation second, dated community reports third, and no invented values.
The Roblox experience, group and event pages are the first source for place identity, public mechanics, displayed codes, update dates and scheduled events.
Egg pools, laying chances and UI values should be captured from the current game build. A dated table is not treated as permanent.
Community guides can identify codes, skills and combinations to test. Until reproduced, they stay visibly marked as community-reported.
Publication rules
Freshness means retesting the claim, not changing the date.
| Status | Minimum evidence | How it appears |
|---|---|---|
| Official | Visible on a current Roblox-owned experience, group or event page. | Named as official with a source link and check date. |
| Observed | Captured from the current game build with identifiable inputs and output. | Published as current-patch game data. |
| Community reported | A dated public report that is specific enough to reproduce. | Useful lead, clearly separated from confirmed facts. |
| Still testing | Incomplete, conflicting or one-off evidence. | No confident recipe, reward or stat claim. |
Cumulative hatch odds use 1 − (1 − p)ⁿ. They describe the chance of at least one success across independent rolls; they never turn a random drop into a guarantee.