PLAYED IT? PROVE IT.
Reviews built on verified experience and transparent preferences.
● Demo data only
NO MORE DRIVE-BY SCORES

Real playtime.
Better context.
Smarter ratings.

To affect the score, a reviewer must pass a game-specific 40% participation threshold. Then the genre-weighted score takes their gaming interests into account—without silencing different opinions.

40%minimum verified progress
Top 5ranked favorite genres
3 scoresraw · genre · personal

Browse games

Click any game to see exactly how the review scores are calculated.
6 demo titles

How it works

1

Link a gaming account

Connect a platform such as Steam. In a production site, obtain eligible gameplay data with user permission.

2

Meet the 40% rule

Story progress for campaign games; defined playtime plus completed activity for competitive games.

3

Review in context

Every eligible vote affects the verified score. Genre familiarity adjusts its influence in the genre score.

REVIEW INTELLIGENCE

Madden NFL

Reviewer breakdown

Each person below passed this game's demo verification rule. Scores reflect fictional reviews.

Make the weighting visible

Genre ranking determines the multiplier for that game's main category. This is an illustrative policy, not a claim about review quality.

What would your rating need?

YOUR GAMING DNA

Build your reviewer profile

Rank your five favorite genres, from #1 to #5. This helps people interpret your reviews and powers a personal-match score. Your preferences never lock you out of reviewing another genre.

Which games do you actually enjoy?

Current taste profile

In a real product, self-reported rankings should be checked against actual play history where possible, with an option to correct the profile. Liking a genre is not the same as being technically knowledgeable.

GATING LOGIC

Try the 40% review rule

This section simulates eligibility. Moving a slider is not actual proof; a launched service would read permitted platform or game telemetry server-side.

25%

Demo preview only. Nothing is posted, and no account or gameplay is actually verified.

EVERY SCORE SHOULD BE AUDITABLE

A transparent rating system

The proposed scoring model, including the distinction between preference, expertise, and verified engagement.

The weighting policy

Reviewer's genre rankingVote weightMeaning
Top 1–21.40×Strong genre interest
Top 3–51.20×Established genre interest
Outside top 50.75×Different gaming perspective

Genre Score = sum(score × genre weight) ÷ sum(genre weights). Verified Score = arithmetic mean of qualified reviews. Your Match Score further weights reviewers with taste profiles similar to yours. These are proposal numbers; test them before launch.

Eligibility, not just ownership

Story-driven games: 40% of verified campaign progress, ideally from developer-supplied checkpoints. Time estimates are only a fallback and require anti-idling checks.

Sports, multiplayer, sandbox: 40% of a published evaluation benchmark—plus a minimum number of genuinely completed matches or sessions. The benchmark is game-specific and shown before rating.

Incomplete platform data: allow discussion but label the rating “unverified” and exclude it from official aggregated scores until verifiable.

Protection against score manipulation

Keep one eligible rating per unique player per game; handle review edits, suspicious bursts, duplicate platform accounts, and rewarded/incentivized reviews. Cap outsized influence and show sample sizes.

Keep genre affinity separate from a future genre expertise signal (verified game breadth, playtime, review quality and consistency), so players cannot claim expertise just by picking favorites.

Publish the weighting rules and version history. No publisher should be allowed to buy a higher score.

What a first real launch would need

A backend with user accounts; permitted Steam login and data access; a game catalog (such as IGDB, subject to its terms); per-game progress requirements; a protected rating database; review moderation; and a versioned scoring service. Console support would be added only after confirming permitted integrations.

This file demonstrates the interface and math, but intentionally has no production login, data integrations, server-side verification, user database, or public hosting.