
The no-difficulty-settings answer is directly sourced
The relevant interview asks the developer about the game’s approach to challenge. One More Level’s answer states that difficulty levels will not be available on release day. That is a specific launch-policy statement, rather than a conclusion drawn from a demo menu or a comparison with another studio’s games.
The studio’s stated recommendations focus on perfect parrying and aggressive combat. Those comments explain the skills it expects players to develop, not an exact rating of how difficult the game is for everyone. They also do not announce an easy mode under another name, so no such feature is included here.
Fixed difficulty and balance changes are compatible
The developer’s August feedback update discusses improving combat readability and boss variety. Its September update then explains the relocation of General Lothaire within the campaign. These are changes to how the game presents and paces its challenge, even though the announced release still has no difficulty selection.
This matters for interpreting older hands-on reactions. A player’s experience with the demo remains evidence about that version, but the studio has documented structural differences before release. The following sections describe those changes and the defensive tools without claiming a universal difficulty score or an unannounced assistance mode.
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.
General Lothaire’s chapter placement
General Lothaire is a boss explicitly identified in the developer’s written updates. He appeared at the end of Chapter I in the Steam demo, after a short introduction to the combat system. The studio acknowledged feedback that this encounter was unforgiving for players who were still learning how a first-person Soulslike handles defence and positioning. The discussion identifies the encounter by name and by its position in the playable slice, supplying a concrete reference for the balance feedback.
For the full game, the developer places Lothaire at the end of Chapter II. Its explanation is that the player will have spent more time with the mechanics and progressed further before meeting him. That change is concrete information about the difficulty curve, although it does not supply his final health, a list of phases or an exact attack-by-attack strategy. Its confirmed location is enough to correct the order shown in a demo walkthrough without inventing a new explanation of the boss’s narrative role.
Parries, dashes and finishers
The developer identifies parries, dashes and finishers as core combat actions. These mechanics sit alongside melee attacks, ranged weapons and powers rather than forming separate game modes. Knowing which defensive action is available with the equipped weapon matters, particularly when comparing a blade that can block with one that depends on precise parries. The reliable distinction is between the described actions and weapon restrictions, rather than an assumed timing rule borrowed from an unrelated action game.
An official combat update explains that players found some defensive cues difficult to read in the early playtest. The team described work on attack windups, pre-attack audio and clearer distinctions between blocking and parrying. Those changes explain the focus of development without supplying a numerical parry window or a promise about the timing of every attack. The source is a development explanation, which makes its stated changes useful context even when a recording shows an earlier version of the interface.
The rapier has a distinct defensive tradeoff
The July demo announcement describes the rapier as a weapon that cannot block. Its defensive option is a correctly timed parry, while its attacks can strike enemy weak points without requiring a firearm. These are meaningful differences in how the weapon works, rather than evidence that it is always stronger than another blade. The comparison is therefore about available actions and the cost of choosing them, not a tested calculation of damage for an entire campaign.
Game Informer independently observed the distinction between the sabre and rapier in a hands-on preview. The writer described the sabre as an option for general damage and blocking, and the rapier as a way to target weak points at the cost of blocking. That agreement supports the weapon roles shown before release, while keeping demo observations separate from a final-game damage comparison. Both references identify the defensive tradeoff, which is the relevant shared detail rather than an unsupported claim that the preview settles every balance question.
Rebinding and target lock
Keyboard rebinding is explicitly discussed in the official combat development update. Players had reported that the old Ctrl and Alt controls could feel uncomfortable, and the studio said it would reconsider the defaults. The same post highlights mouse side buttons as an alternative for blocking or dodging, so a player’s own comfortable mapping is part of the supported control approach. That is practical input information confirmed by the studio, without requiring every player to copy the same keys from an old demonstration.
Target lock and camera behaviour were another focus of the update. The team described plans for better tracking, smarter target priority and a range that accommodates both melee and ranged combat. Those statements confirm the system under discussion, without turning an old demo layout into a complete table of final keyboard and controller bindings. A recorded target-lock change concerns camera handling, whereas a binding concerns the input used to trigger it, and the update addresses both questions.
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.
Sources and further reading
- Difficulty interview — Insider Gaming
- Responding to the biggest feedback from the Demo
- The Final Stretch - Development Update
- Valor Mortis — One More Level
- 3 things we are working on to improve combat in Valor Mortis
- Valor Mortis Demo is BACK for Summer events!
- Valor Mortis hands-on preview — Game Informer
- Valor Mortis Demo is Available Now!