Read the score field rather than surrounding metadata
The Metacritic game page is the relevant reference for the displayed score status. In the collected snapshot it does not show a numeric critic average or user-rating average. That is a specific observation about the page, rather than an estimate based on the genre or the studio’s earlier work.
The details page supplies title information, including platforms and the release date. Those fields help identify the product but do not describe a scored review. Keeping identification and evaluation separate avoids treating the presence of a game entry as evidence that a critical consensus has already been published.
Preview coverage does not fill an empty Metascore
A hands-on preview can discuss mechanics and concerns without assigning the same kind of result as an aggregator. Game Informer’s September article describes a preview build, praising its foundation while criticizing difficulty balance. That account belongs to the evidence about the game, but it is not the missing number in the Metacritic score field.
The same applies to a viewer’s prediction of a future score. The collected research does not authenticate such a number as a published rating, so none is presented here. The following sections explain the real preview context and confirmed release information without attaching an invented average to them.
Metacritic currently displays TBD
The retrieved Metacritic page displays TBD rather than a numeric Metascore or user score. It does not show a published critic consensus or a user-rating average in this research snapshot. TBD is a status indicating that a score is not displayed, so it should not be read as a score of zero or an unfavourable review. The displayed status is the answer available from that snapshot, rather than a number to replace with an estimate until a rating appears.
The separate details page lists the game’s release date and platforms. That metadata helps identify the title, but it is not itself a review and does not add points to a score. Keeping the details page and the rating display distinct prevents a release-date entry, an advertisement or a community prediction from being mistaken for a critical result. The distinction is especially useful before release, when a product can have an identifiable page without having a published numerical evaluation in its score field.
What the hands-on preview actually says
Game Informer’s September hands-on article describes a preview build rather than a review of the released game. Wesley LeBlanc praises the combat foundation and environmental design while criticizing uneven difficulty, particularly in important encounters. Both parts matter when reading the assessment, because it is neither unqualified praise nor a numerical final verdict. Attributing the observations also identifies who made them and what kind of experience produced the assessment, keeping it distinct from an anonymous final verdict.
The writer also describes the sabre’s blocking role and the rapier’s weak-point attacks, providing observations about the version he played. Those details are useful alongside the developer’s explanation of the demo and balancing changes. They remain attributed preview observations, rather than a promise that every criticism or compliment applies unchanged to the launch build. That separation lets a reader compare the preview with the written changes while avoiding a claim that the site independently tested the same encounters.
The current release date and the earlier delay
Valor Mortis is scheduled to release on October 13, 2026. The earlier September 24 announcement was changed in a June 11 update, which Gematsu reported with the developer’s explanation. Keeping that sequence in mind resolves the most common disagreement between an older trailer and the current storefronts. The later statement is the one used for current planning, while the earlier announcement remains useful only for understanding the change in schedule.
The October launch announcement continues to use October 13, and the official platform listings support that date. This research was checked on October 11, while the game was still ahead of its full release. It records the announced launch date without substituting a fan-site countdown for a verified global unlock schedule. Release-date confirmation and exact time-zone conversion are separate questions, and only the date has been consistently established across the sources used here.
Why the demo differs from the campaign
The public Steam demo used specially adapted versions of Chapters I and VII. In the September development update, the studio explains that these levels were rebuilt for Steam Next Fest rather than simply copied from the finished campaign. Their chapter labels therefore describe the pieces used for the demo, not a complete route through the retail story. The modified structure explains why a guide can discuss a later chapter immediately after an introductory section without documenting the intervening story.
The developer also said that incorporating final-game optimization, balancing and fixes into those bespoke demo levels was not straightforward. This is why the demo’s presentation and difficulty need to be read as a particular build. A video recorded in that version remains useful historical material, but it does not establish the exact state of the game released later. The announcement gives a reason for comparing builds carefully, rather than assuming that an earlier recorded bug or difficulty spike describes every subsequent version.
The announced difficulty approach
In an interview published by Insider Gaming, One More Level said Valor Mortis would not have selectable difficulty levels on release day. The studio described its intended challenge as demanding while rewarding persistence and skill. Its recommendations emphasised perfect parrying and aggressive direct combat, explaining the kind of mastery the game is designed to encourage. The answer comes from a direct studio interview, so the absence of a launch difficulty selector is more than an inference from an early test.
The developer’s demo-feedback update also addressed combat readability, boss variety and the difficulty curve. These topics show that a fixed difficulty does not mean the team ignored balance feedback. They describe areas being refined during development, rather than a separate easy mode or a numerical comparison with another Soulslike’s difficulty. Keeping the launch policy separate from ongoing balancing work makes both statements understandable without assigning a difficulty setting that the studio never announced.
The developer’s twenty-hour story estimate
The developer’s price announcement describes Valor Mortis as having a twenty-hour story. Insider Gaming’s length coverage repeats that estimate and identifies the studio as its origin. This gives a clear main-story planning figure without claiming that the number came from a large sample of players who completed the released game. The source and the category of playthrough are both part of the answer, so the number remains identifiable as a story estimate.
The figure concerns the story rather than a measured platinum or full-collection run. The published research does not establish a completed-game average for every play style. It is therefore useful to keep the developer’s estimate attached to the main campaign and to leave preview sessions, optional exploration and future expansion content outside that single stated number. This distinction preserves the one supported playtime figure without adding speculative hours for trophy cleanup, later updates or a different player’s encounter attempts.
Sources and further reading
- Valor Mortis — Metacritic
- Valor Mortis details — Metacritic
- Valor Mortis hands-on preview — Game Informer
- Launch Trailer and Launch Times
- Valor Mortis delayed to October 13 — Gematsu
- The Final Stretch - Development Update
- Valor Mortis Demo is Available Now!
- Difficulty interview — Insider Gaming
- Responding to the biggest feedback from the Demo
- Revealing the price of Valor Mortis
- How Long Is Valor Mortis? — Insider Gaming