Editorial Methodology

KonNetwork reviews games through direct play, clearly stated experience, and close attention to how mechanics, presentation, narrative, and technical performance work together.

Our goal is to explain what a game is trying to accomplish, how its design choices shape the player experience, and how successfully those choices come together.

Jump to Content
  1. Analytical Philosophy
  2. B.E.I.V.T. Review Framework
  3. Game Evaluation Method
  4. Scoring System
  5. Technical Evaluation Standards
  6. Editorial Independence
  7. Corrections & Updates

Analytical Philosophy

KonNetwork evaluates games as complete experiences shaped by mechanical, technical, narrative, and creative decisions.

Our analysis considers:

  • Gameplay mechanics and systems interaction
  • Level, encounter, and progression design
  • Narrative, characterization, and presentation
  • Technical performance and platform behavior
  • Genre expectations, series history, and development context

Personal enjoyment remains part of every review, but it is not treated as the only measure of quality. We distinguish between a design choice that does not suit our preferences and one that fails to support the experience the game is trying to create.

B.E.I.V.T. Review Framework

KonNetwork uses the B.E.I.V.T. framework as an internal editorial foundation for its reviews. It guides the questions considered during evaluation, but it does not require every article to use the same visible headings or structure.

Background
This establishes the who, what, and how while providing the historical context needed to understand the game’s development and, where documented, developer intent, while spotlighting the core staff.

Experience
The reviewer’s familiarity with the game, genre, series, platform, and completion status. It is our way of acknowledging potential biases and helping the reader understand where the perspective is coming from.

Impressions
Analysis of the game’s mechanics, level design, presentation, narrative, audio, accessibility, and technical performance. A guided-tour approach walks the reader through how the game fundamentally plays, building a mental picture they can use to interrogate the experience alongside the reviewer.

Verdict
A final assessment of how successfully the game’s individual elements work together as a complete experience. It brings together the reviewer’s experience, developer intent, and underlying systems to explain the final assessment.

TLDR
A concise summary of the review’s key strengths, cautions, and final score. A pros and cons list accompanies the scorebox summary to provide an at-a-glance snapshot. We still believe you should read the full review, since the summary can’t capture all of the context behind how that conclusion was reached.

Individual reviews may adapt this framework to suit the game and the material being discussed.

Game Evaluation Method

KonNetwork does not calculate scores through formulas, weighted categories, or numerical averages.

Each evaluation is based on:

  • Direct gameplay and documented completion status
  • Observed mechanics, systems, and encounter design
  • Narrative, presentation, and emotional impact
  • Technical performance and platform-specific behavior
  • Genre, franchise, and historical context

Scores reflect the reviewer’s overall assessment of the complete experience. A strong mechanic, technical problem, or personal preference may influence the result, but no single element determines the score by itself.

Scoring System

KonNetwork uses a 10-point scoring scale with half-point intervals. Higher scores reflect stronger overall execution, while lower scores reflect increasingly serious design, structural, or technical problems. Scores summarize the final critical judgment and are not a substitute for the reasoning in the full review.

  • 10 – Masterpiece
  • 9.5 – Near Masterpiece
  • 9 – Excellent
  • 8.5 – Very Strong
  • 8 – Great
  • 7.5 – Above Average
  • 7 – Good
  • 6.5 – Decent
  • 6 – Fair
  • 5.5 – Below Average
  • 5 – Mediocre
  • 4.5 – Poor but Playable
  • 4 – Weak
  • 3.5 – Rough
  • 3 – Flawed
  • 2.5 – Glitchy
  • 2 – Broken
  • 1.5 – Unstable
  • 1 – Unplayable

A score should be read alongside the review itself. Two games with the same score may arrive there for very different reasons, and the written analysis provides the context behind that judgment.

Technical Evaluation Standards

Technical analysis is included when it materially affects the experience. This may cover:

  • Frame-rate stability and responsiveness
  • Visual settings, resolution, and image quality
  • Platform-specific behavior and optimization
  • Crashes, stuttering, input issues, and other reproducible problems
  • Linux and platform compatibility where relevant

When Linux compatibility is relevant to a review or guide, it is tested directly on systems such as Nobara Linux. ProtonDB may be referenced as supplementary community evidence, but it is not used as a substitute for hands-on testing.

Technical observations are limited to what was tested or supported by reliable evidence. Estimates, platform differences, and testing limitations are identified where appropriate.

Editorial Independence

KonNetwork is an independent publication supported through self-funding, optional reader donations, and affiliate commissions. These sources help cover hosting, development, and editorial operations while allowing the site to remain free of display advertising.

Affiliate partnerships, reader support, review materials, early access, and publisher or developer relationships do not influence our reviews, recommendations, news coverage, or final scores.

Most games are independently purchased. When a review copy, early access, or another form of access is provided, it is disclosed within the relevant coverage. All conclusions remain based on direct experience and independent editorial judgment.

Corrections & Updates

KonNetwork strives to keep its published work accurate and useful. Factual errors are reviewed and corrected when identified.

Minor spelling, grammar, formatting, or clarity edits may be made without a public notice. Significant factual corrections are noted within the article when they affect its information, analysis, or conclusions. Evergreen articles may also receive update notes when important information changes.

News articles are generally preserved as a record of what was known at the time they were published rather than continually rewritten as events develop.

If you believe an article contains inaccurate information, or outdated information on a page intended to remain current, please contact us through our Contact page. Good-faith correction requests are welcomed and reviewed.