📋 Editorial Policy

How we collect, verify, and maintain game data across all AverGames tools.

📊 Data Sources

AverGames uses a multi-source verification approach. No single data point is published based on a single source.

Source TypeWhat It ProvidesReliabilityExamples
In-Game TestingBase values, formulas, grow times, multipliers⭐⭐⭐⭐⭐Crop profit formulas, mutation stacking, DPS calculations
Developer AnnouncementsPatch changes, new features, balance adjustments⭐⭐⭐⭐⭐Official Discord posts, Twitter/X patch notes, in-game changelogs
Community Wiki & DiscordTrade values, spawn timers, meta strategies⭐⭐⭐⭐Pet trade values, seed shop rotation timing, boss strategies
Competitive Player InputTier rankings, optimal builds, endgame meta⭐⭐⭐Unit tier placements, trait priority rankings, team compositions

🔄 Verification Process

1
Initial Data Collection
Data is collected from in-game testing on the latest game version. For calculators, formulas are reverse-engineered through controlled experiments with known inputs and measured outputs.
2
Cross-Reference
All data is cross-referenced against at least one additional source (developer patch notes, community wiki, or independent tester reports). Discrepancies are resolved through additional testing.
3
Publication with Source
Each tool page includes a "Data Source & Methodology" section explaining where the data comes from and how calculations work. This transparency allows users and other data miners to verify our work.
4
Post-Patch Re-verification
The "Last Updated" or checked date changes only after a real re-check. Core codes hubs are reviewed against current public trackers; other tools stay on their last verified date until the next pass.
5
Community Corrections
When users report inaccurate data via our Contact page, we investigate as soon as we can. Confirmed errors are corrected and the page date is updated when the fix is published.

📝 Content Quality Standards

Every page on AverGames follows these editorial principles:

  • Specific over vague. We write "Strawberry grows in 12 seconds and sells for 45 Sheckles" instead of "Strawberry is a good starter crop."
  • Show the math. Every calculator explains its formula. Users should be able to verify our calculations independently.
  • Explain the "why". Our tier lists explain ranking methodology. Our guides explain why a strategy works, not just what to do.
  • No "best" without context. The "best" crop, unit, or build depends on your progression stage, playstyle, and goals. We always qualify recommendations.
  • Disclose uncertainty. Trade values are estimates from community data — we say so. Gacha rates are based on community testing unless developer-confirmed — we note the source.
  • Real dates only. Our "Last Updated" timestamps reflect the actual date data was verified, not when the website was deployed.

🏆 Tier List Ranking Methodology

Our tier lists use a weighted scoring system that considers multiple factors:

  • Raw performance (40%): DPS output, profit per second, stat multipliers, or whatever the primary metric is for that tier list type.
  • Versatility (25%): How well the item/unit/crop performs across multiple game modes, stages, or situations.
  • Accessibility (20%): How easy is it to obtain? A slightly weaker but easily obtainable option can be more practically useful than a rare one.
  • Meta relevance (15%): How well does it synergize with the current meta? This factor is most volatile and changes with patches.

We use 5 tiers: S (must-use/build-defining), A (excellent), B (solid/reliable), C (situational), D (avoid unless no alternatives). Items within the same tier are roughly interchangeable.

🔧 Corrections & Updates

Found incorrect or outdated data? We take data accuracy seriously.

How to report: Visit our Contact page and describe what data is incorrect and, if possible, the correct value with your source. We typically respond within 24 hours.

Update frequency: High-traffic pages (codes, calculators, tier lists) are checked daily. Lower-traffic guides and wiki pages are reviewed weekly. All pages are re-verified within 48 hours of major game patches.