DREADMOOR Demo Explained

The DREADMOOR Demo is a separate, free Steam application with its own questline around a remote settlement and nearby islands. It introduces fishing, scavenging, a local engineer and dry-dock work rather than giving you the complete planned Early Access game. Start with a fresh demo save if you previously joined a playtest: older saves can cause bugs and crashes.

The demo launched on October 6, 2026. On November 2, its access window needs to be checked on the current Steam listing; an exact shutdown time is not confirmed here. A demo button, an old event announcement and a copy already installed on your PC do not all establish the same thing about access.

What the demo lets you try

You travel between the settlement and its surrounding islands by boat and on foot. Fishing and scavenging supply the resources used in the progression, while an engineer and the dry dock introduce ship improvements. The setting changes after nightfall, so the demo also shows how exploration and unsettling encounters fit around the daytime work.

These activities make it a practical introduction to the game's pace. You are handling equipment and preparing a vessel, not simply watching a sequence of combat encounters. The dedicated questline gives those jobs a direction without establishing how much content the eventual main game will contain.

The expedition joins boat travel with work at a settlement.

The October quest route leads to The Throat and its waterway gate. Sailing beyond that gate reaches the demo's completion screen. There is no supported fixed completion time: time spent exploring, gathering, solving machinery tasks or recovering from mistakes changes the length of a run.

The demo is a different Steam application

Check which name is in your library before applying build-specific advice. A playtest recording can show a different sequence from the October demo, and a demo review score does not become a review score for the main game.

Prepare a fresh game after a playtest

Returning testers should take the old-save warning seriously. The demo announcement recommends removing previous playtest save data and starting again because continuing an old save may produce unexpected bugs or crashes.

Before choosing a reset, keep an external backup of any save you want to preserve. A reset sacrifices that saved progress; it is not a way to retain your old campaign while repairing it.

The announced installation route is Steam Library, right-click DREADMOOR, choose Manage, then Browse local files. Inside the Dreadmoor folder, the announcement identifies the Saved folder for the old-save reset. Only carry out that removal when you have identified the correct installation and decided to abandon that old progress. Do not use it as a general fix for an unrelated graphics or monitor problem.

If you never joined an earlier playtest, the warning is not evidence that every new player must delete files before starting.

PC requirements for this demo

The demo store lists the following Windows requirements. Its storage figure is 20 GB, separate from the main game's 60 GB store requirement.

These are specifications, not a promise of a particular frame rate or resolution. They also replace the much higher requirements circulated for the early pre-alpha test; do not judge the October demo using that old test's hardware list.

Languages and handheld expectations

The demo supports twelve interface and text languages. English and Russian have professional full audio. Other supported languages, including Japanese, use localized text and subtitles with English or Russian speech.

Dialogue text and spoken audio are separate language-support categories.

The October announcement says the demo can be played on Steam Deck, while also stating that it had not received an official Steam Deck Verified rating. Treat those as two separate statements. Playability does not supply a frame-rate benchmark or guarantee the same result on every software configuration.

Decide what to report when progress breaks

Use the demo's in-game bug-reporting route if an interaction stops advancing. Include the application name, the displayed objective and what you did immediately before it stopped. A report about the waterwheel repair is more useful when it distinguishes missing components from installed components that the journal has not registered.

The dry dock is one of the demo’s progression areas.

Keep a copy of the affected save before trying a rollback. That preserves the state you need to describe and avoids replacing your only record of the problem while checking an earlier point.