We have no controlled observation dataset showing whether rare eggs follow a fixed timer or spawn randomly. Do not treat five minutes as a guaranteed rare egg spawn time. It is only our editable check-reminder default.
By the independent StealAnEgg.app site team. Method/content updated October 23, 2026. Stored official description snapshot dated Nov 18, 2026. Mechanism last tested: not yet tested in a controlled study. This page is a protocol, not a completed experiment.
What evidence do we have?
| Evidence | What it supports | What it cannot establish |
|---|---|---|
| Official Roblox game description, stored snapshot Nov 18, 2026 | Describes stealing, hatching, and discovering rarer eggs. The stored text publishes no rare-egg spawn cadence. | No statement here proves either fixed or random timing. This is not a fresh check of the live page or an in-game test. |
| Five-minute check reminder | A site-selected, adjustable reminder duration. | A timer setting is not game evidence. |
| Local sighting tracker | Past gaps calculated from timestamps entered by the user. | It cannot see Roblox, identify missed events, log all no-spawn rounds, or prove a future schedule. |
| Controlled round log and recordings | Observation data pending. No observations, recordings, or statistics are published here. | We cannot estimate spawn probability, a reliable cadence, or differences between servers yet. |
Planned method and test conditions
- Identify the game using place ID 107778070777162. Record the displayed game update/build label; write unknown if unavailable.
- Before watching, define the exact rare-egg label and visible spawn event. Keep map reset, egg appearance, pickup, and hatch as separate events; do not assume a reset produces a rare egg.
- Use a pseudonymous server/session label. Record public/private server type, biome or source, device, join time, observation start/end in UTC, and any event or boost state. Do not include private-server access links.
- Watch continuously and capture timestamped video where possible. Choose the observation duration before starting and retain quiet periods. A five-minute observation block is a chosen sampling unit, not an assumed game round.
- If the game visibly marks round/reset boundaries, log their actual times. Otherwise use the predeclared observation blocks and label them as blocks. Record every block/round, even when no rare egg appears.
- Mark lost visibility, late joins, interruptions, server hops, and update boundaries. Start a separate session after a hop or update; do not silently combine samples.
- Before reporting conclusions, publish the full de-identified round log and supporting recordings, define inclusion rules, and separate observations from hypotheses. Two sightings supply only one past gap.
Observation table structure
Observation data pending. The table below defines fields only; it contains no observation records. A no-spawn round is an observed negative result only if coverage was complete. Use unknown for incomplete coverage.
| Field | Record |
|---|---|
| Session and context | Session/server label, place ID, game update/build label, public/private server type, device, biome/source, join time, and event/boost conditions. |
| Round/block and time | Sequential round/block ID, boundary definition, start/end UTC, and visible reset time if any. |
| Coverage | Complete or interrupted, gaps and their times, observer visibility, and reason for exclusion if applicable. |
| Outcome | Rare egg seen: yes / no / unknown. Log no-spawn rounds too. Never infer a spawn from a reminder ending. |
| Sighting details | Exact egg label, rarity as shown, appearance UTC, location, and whether the appearance itself was witnessed. Leave sighting fields empty for no-spawn rounds. |
| Evidence and review | Video/screenshot URL or filename, video timestamp range, observer notes, confidence, and review status. |
CSV template
Download the existing observation CSV template ↓. It is a general-purpose template with a clearly labeled example row, not our research data. Delete that example before collecting observations.
For each watched round/block use evidence_type = rare egg spawn round, capture_sequence = round/block ID, observed_at_utc = start UTC, sample_seconds = watched duration, server_notes = session label and conditions, and evidence_url_or_filename = recording reference. Use notes for end UTC, boundary definition, coverage gaps, outcome yes/no/unknown, appearance UTC if seen, and video timestamp range. Keep egg_name empty when no egg was seen. Other columns can remain empty when irrelevant.
Limits and unanswered questions
- A regular map reset and a rare egg appearance may be different processes. We have not established the relationship.
- Gaps between sightings can include missed events or no-spawn rounds. A few similar gaps cannot prove a fixed schedule, and uneven gaps cannot by themselves prove randomness.
- A sample from one server, event, biome, or update cannot establish universal behavior. Device clocks and recording delays also affect precision.
- Without complete coverage and negative rounds we cannot calculate a meaningful per-round spawn rate. We publish no percentages, sample sizes, or timer estimates before data exists.
- No recording is available yet. There is no official developer endorsement of this protocol.
Help collect evidence
Follow the spawn-timing contribution task and attach a complete session log, including no-spawn rounds and evidence references. Submissions require review before they become published evidence.