Methodology: How We Verify The Ranchers Data
The Ranchers is in Early Access and its economy changes between patches. This page is the single reference for how every guide, database row and problem fix on this site is sourced, graded and kept current — so individual pages can show answers instead of repeating policy.
The one editorial rule
Never invent numbers. A longer table is not more useful when its prices or timings are guesses. When a value has not been measured in a named game version, the field stays pending — a short status note, not a paragraph of excuses. Unknown values stay unknown until the evidence below exists.
The five-level evidence scale
Every build-specific claim on this site carries one of these labels, placed on the specific data row or conclusion it supports — not once per page.
From an official announcement, patch note, store page, or developer reply.
Directly visible in video footage; always cited with the source and a timestamp.
Two or more independent player reports agree under comparable conditions.
Measured hands-on by a co-op tester in a named build, with retained evidence.
A single-source clue. Useful as a test lead, not a settled fact.
Older pages may still show the previous label set (Verified / Corroborated / Reported / Historical / Obsolete). The mapping is: Verified → Player-tested or Video-observed, Corroborated → Community-confirmed, Reported → Unverified lead, Historical and Obsolete stay as-is for pre-Early-Access values and patched-out results.
How a report becomes published data
- Collect. Evidence comes from public gameplay videos, official updates, community reports and tester sessions. A usable report includes the game version, the screen or action that produced the value, and enough context to repeat it.
- Screen. We check the report is complete, legally usable and not contradicted by a newer official source.
- Corroborate. A second independent matching observation promotes a lead to Community-confirmed.
- Test. A retained hands-on reproduction promotes it to Player-tested.
- Re-check. A later patch can move any record to Historical or Obsolete. Balance patches can make an old observation obsolete without making it dishonest; when a value changes, the current row shows the newer build.
Crop records include seed cost, occupied days, yield, quality, and sale channel. Animal records include purchase and housing costs, upkeep, production cycle, output, and care conditions. Submit evidence through the contribution form or collect it privately first in Field Notes.
When sources conflict
When two credible sources give different values for the same thing, we display both side by side and say the value is uncertain. We do not silently pick one. Conflicting rows are marked with a data-conflict block:
A conflict resolves only when current-build evidence at Player-tested or Community-confirmed level settles it. Until then, both values stay visible with their sources and versions.
What "pending" means on a page
Pending means the value has not been measured in the current build — nothing more. Pending fields are shown as a short status note or an empty cell, and each content page carries a single evidence-status card at the top summarizing what is verified and what is still open. The research queue lists the specific open questions and the smallest test that would answer each one.
Sources we use
- Official Steam store page and official Steam announcements — system-level facts and patch notes.
- Public gameplay videos, cited with channel and timestamp — Video-observed facts. The current primary video-observation source is Games Station's Early Access gameplay footage (V0.8.10.455), reviewed August 7, 2026.
- Steam discussions, Reddit and fan wikis — leads and community confirmation, linked rather than copied.
- Tester sessions in named builds — Player-tested facts.