A score is a judgement, not a universal instruction
NTRW reviews explain a game's strengths, compromises and likely audience. We consider mechanics, structure, writing, presentation, usability and the relationship between those elements. We ask what the game is trying to achieve and how effectively its design supports that purpose. Length, budget and popularity do not replace that assessment.
The verdict should make sense without the number. Pros and cons summarize the argument rather than introduce unsupported claims. A recommended audience explains who is most likely to value the experience and which preferences could make it a poor fit.
Our ten-point scale
- 9–10: exceptional work with a strong recommendation for the identified audience; limitations still matter.
- 8–8.9: a strong experience whose compromises should be understood before choosing it.
- 7–7.9: worthwhile for the right player, with more substantial limitations.
- 5–6.9: mixed or narrow appeal; read the reasoning carefully.
- Below 5: major problems significantly undermine the intended experience.
Decimals express an editorial distinction within a band, not scientific precision. A 9.3 does not promise that every player will enjoy the game more than one scored 9.1. The written analysis provides the useful comparison.
Scope and evidence
A design review may discuss a game's structure without providing a fresh platform benchmark. Where hands-on testing is performed, the platform and relevant conditions should be stated. We do not invent completion hours, review access, frame-rate measurements or a personal play diary to make an assessment sound more authoritative.
The review features on NTRW Gaming are critical design assessments. They should not be read as current technical certification of every port. Readers with a specific performance or accessibility requirement should verify that requirement through current documentation and suitable testing reports.
Access, sponsorship and updates
Any review access or commercial relationship relevant to an assessment should be disclosed with that article. Advertising does not purchase a score. Updates should state when a material conclusion changes and why. A historical review can remain useful when its scope is clear; it should not silently pretend to describe later content it never assessed.
For correction requests, use the contact page and identify the precise factual issue. Disagreement with an interpretation is welcome, but it is different from evidence that a release date, platform feature or mechanic has been described incorrectly.