Steal an Egg Wiki Source and Evidence Policy

What do the evidence labels mean?

Label	Meaning
Official	Published by Roblox or the game developer
Cross-checked	Repeated in multiple recent, independent observations
Community tracked	Useful player-recorded data that can change without notice
Calculated	Produced from an exposed formula and user-supplied inputs
Conflicting reports	Current sources disagree; the disagreement is part of the answer

How are conflicts handled?

The pet and biome totals are a good example. Older current-month sources describe nine biomes and roughly 78 pets, while post-update trackers include Cherry Blossom and report ten biomes and 86 pets. We preserve the conflict, state the check date, and treat the live in-game Index as the final authority.

Correction rules

• A correction keeps its date and reason.
• A changed number does not erase the earlier source context.
• Unverified codes are never promoted into the active list.
• Calculators do not hide assumptions behind site-supplied rates.

See the data corrections log for launch-state known gaps.

What counts as evidence for a particular claim?

A source must support the sentence it accompanies. The official experience description can establish the broad gameplay loop, but it cannot establish a specific pet’s income if that number never appears there. A screenshot of one pet card supports the visible card value under its recorded conditions. It does not establish every size, mutation, or future version of that pet.

We therefore separate identity, mechanics, measurements, and advice. Identity includes the experience URL and creator label. Mechanics describe what the game says an action does. Measurements record what an observer saw. Advice explains a decision using those facts and stated assumptions. Advice does not become an official instruction merely because the article also links to Roblox.

An evidence panel summarizes the page’s approach. It is not a blanket guarantee that every sentence has the same certainty. When a page combines an official description with a player testing procedure, the text should identify that boundary. A method can be useful without claiming that the editors have completed every test it describes.

How do we assess independence and freshness?

Two pages repeating the same screenshot or copying the same table count as one underlying observation, not two independent confirmations. Useful cross-checks should have separate observations, compatible definitions, and dates recent enough for the question. A newly published page containing old footage is still old evidence for an update-sensitive value.

We distinguish the date the article was edited from the date a game claim was checked. Correcting grammar, expanding a worksheet, or improving an explanation can change the article’s modification date without making the underlying pet rate newly verified. Readers should use the evidence note and individual source context when freshness matters.

The live game is often the best place to inspect a value that applies to your session. Even then, record the relevant conditions. A temporary modifier or a pet’s size can explain a disagreement without either observer being dishonest. We do not force different measurements into one number simply to make a table look complete.

Which details should accompany a player observation?

A useful submission states the page and claim in question, the observation date, the exact experience, and the visible conditions that could affect the result. Include the unit for every measurement. “Income increased” is difficult to check; a before value, after value, elapsed time, and unchanged setup are more informative.

Screenshots should preserve the labels required to interpret the claim while removing unrelated personal information. A cropped number without a pet name or unit may be impossible to evaluate. Never include passwords, authentication cookies, private messages, payment details, or information about another player that the correction does not need.

For a route claim, explain the starting point, finishing point, whether the egg was carried, and what counts as a failure. For a code claim, include the exact response shown by the game and whether the account had already redeemed it. For a purchase claim, use the official item’s current description instead of a reseller’s promise.

What happens to a correction before publication?

Use the contact page to send a correction through the available channel. Suggestions do not automatically appear on the wiki. The editorial process is to identify the disputed claim, review the supplied evidence, compare it with the existing source context, and decide whether to correct, qualify, or retain the text.

This site does not promise an immediate review time. A report with missing context may remain unresolved until enough evidence exists. Repeating a claim more forcefully does not raise its evidence level. When the evidence is useful but incomplete, an uncertainty note may be a more accurate outcome than a new definitive value.

Accepted changes should leave a short reason and a meaningful date. If a correction affects a calculator example, linked guide, or comparison table, those uses also need inspection. Fixing one occurrence while leaving the same old assumption elsewhere would continue misleading readers.

How do calculations and examples differ from game data?

A calculated result is conditional on its inputs. Publishing a formula makes the arithmetic inspectable; it does not validate the game values entered into it. We name the input units, distinguish displayed totals from base rates, and explain whether a modifier is already included.

Hypothetical numbers are labeled as examples. They teach a calculation or a decision and must not be copied into pet databases, advertised as measured rates, or converted into claims about drop chances. A proposed experiment is likewise a protocol, not a report that the experiment has already happened.

When evidence is absent, we leave the value unresolved. We do not invent codes, badge requirements, pass prices, update announcements, sample sizes, or successful tests to fill a page. The research method explains the broader testing process, while individual guides explain how a reader can apply it to a specific decision.

How should readers use an unresolved answer?

Check whether the uncertain detail actually changes your choice. You may be able to compare the live income cards in your own base without knowing a universal multiplier. You may be able to practice a route without knowing a rare egg’s exact schedule. Prefer the decision that uses observable information until the disputed claim can be resolved.

If the unknown affects spending, a limited event, or a large time commitment, pause that decision and consult the current official interface. This wiki is fan-made and independent. It cannot issue official support decisions, restore items, manage accounts, or guarantee that a community strategy will remain valid after an update.