Method notes · Method

How we read the Badges API, and what it cannot tell youField note

This is a field note, not a data page. It reads the endpoints named inside it. The pages carrying game figures are marked Data page, and every value on those opens its own source.

Something to play while you read

Candy Gold is a coin pusher on coinpushergames.com. It has nothing to do with Steal An Egg — it is here because it loads in one click and is more fun than a loading spinner.

Something free to play elsewhere

Play retro arcade games free at RetroGameStore.cc

Retro arcade games on retrogamestore.cc. Also nothing to do with Steal An Egg — same reason as the coin pusher on the left.

This is a field note. Its basis is a single Roblox endpoint — `badges.roblox.com/v1/universes/10563114921/badges` — read on 14 August 2026, plus the game's own description from the Games API. Nothing below has been measured in-game, and no figure appears here that those two sources do not contain. ## What the endpoint returns Six badges, and `nextPageCursor: null` on the first page. That null is the part worth pausing on: it means the six are the complete set, not the first page of a longer list. A wiki that says "these are the achievements" without checking the cursor is guessing, and would keep guessing correctly right up until the developer adds a seventh. Each badge carries an `awardedCount` — how many distinct players have ever earned it. Three of the six are named `Hatched Secret!`, `Hatched Eternal!` and `Hatched Divine!`. Two more, `Divine Trail!` and `Angelic Treadmill!`, are not hatch outcomes. The sixth is `WELCOME!`, which is awarded on entry. ## What we do with it Every share on the rarity page divides one badge's count by the 4,474,854 players holding `WELCOME!`. That denominator is a choice, and the page says so rather than presenting it as the obviously correct one. Total visits would be worse — a visit includes anyone who loaded the place and left — but "holds the entry badge" is not the same as "played seriously", and we have no source that measures the second thing. ## The question it cannot answer Players ask what the odds are of hatching a Divine. This endpoint cannot say. It counts *players who have ever succeeded*, not *attempts*. A player who opened four hundred eggs and one who succeeded immediately are the same single increment. Without the number of eggs opened, no per-hatch rate can be derived from these counts, and no source we checked publishes one. So the rarity page reports attainment and refuses to convert it. `0.124% of WELCOME-badge holders have hatched a Divine pet` is a sentence the data supports. `Divine has a 0.124% hatch chance` is not, and the site's build fails if that second form ever appears in the source. ## What would change this An in-game capture log with attempt counts. That is scheduled work rather than a someday, and when it exists the odds move to a data page with screenshots attached — and this note gets shorter.