Current playable surface

Route

  1. historicalAlpha preview

    The alpha preview is an earlier development stage, not a current downloadable build.

  2. historicalBacker beta milestone

    The beta milestone is a historical stage before the limited demo became playable.

  3. currentLimited Demo / Build 0.7

    Build 0.7 is the current limited standalone demo available to test.

  4. upcomingEarly Access plan

    Early Access is planned before the end of 2026, without an exact calendar date.

  5. upcoming1.0 plan

    Version 1.0 is planned sometime in 2027, without an exact calendar date.

Historical milestones

Alpha and beta previews came before the current demo. They explain why older versions may show a smaller ancestry list, a different feature emphasis, or a different expectation for availability. They are useful context for understanding development, but they are not live builds that a new player should plan around.

When you find an older description, separate the milestone date from the feature it discussed. A preview can show the game’s direction without establishing the exact contents of Build 0.7. Treat the current demo as the anchor so an older detail does not quietly become a present-tense promise. Use the older stages to understand change, not to reconstruct a route you cannot launch. The practical comparison is simple: play the current demo, record the build and platform, and then decide whether a later window is worth following. This keeps historical context useful while protecting the player from planning around a feature, save, or control scheme that belonged to an earlier stage. If a future note changes a date or feature, compare it with the playable build before changing your plan. A new target matters for timing, but the current demo remains the direct test of the game’s present loop. Keep the distinction visible when discussing the game with friends: say whether you are describing a build you played, a target you are waiting for, or a lesson from an older preview.

Current playable surface

Build 0.7 is a limited standalone demo. It is the right place to judge the game’s current character creation, village-to-forest route, dungeon loop, encounter pressure, and co-op foundation. The demo is a one-shot rather than a final campaign save, and its saves will not transfer to the final game during development.

Use the demo for direct answers. Does a background make the character feel distinct? Does a weapon or Magic Path create a useful combat question? Does a return to Rivermere make preparation feel meaningful? Those are playable observations. If a later update changes the answer, treat that build as a new playable surface rather than a correction to what you experienced in Build 0.7.

Early Access plan

Early Access is planned before the end of 2026. No exact calendar date, locked content checklist, or guarantee for every target system has been announced. Use the window as a broad direction when you plan your time, and check the official channels before making a purchase or download decision.

A release window is useful when it changes how you plan your time, but it should not replace the current demo. Play Build 0.7 if you want to know how the game feels now; follow later announcements if you want to know when the plan changes. Keep a target window separate from a playable release.

Version 1.0 plan

Version 1.0 is planned sometime in 2027 without an exact date. That is a broad future target, not a calendar commitment. The final shape can change as player feedback affects scope, balance, co-op rules, and the world route. If you are deciding whether to try the demo, focus on its current value rather than a future feature list.

Before acting on a roadmap detail, check the newest announcement and compare it with what the current build lets you do. Plans can be meaningful while still changing, so keep the broad target and the playable experience in separate boxes.

How to follow the project

Follow the game’s official site, Steam community, and publisher or developer channels for new announcements. Community discussion can add useful play experience, especially around demo length, controller preferences, handheld optimisation, and co-op habits. A player report is strongest when it names the build, platform, party size, and route.

No exact calendar release date has been announced. The current status is a demo available to test, Early Access planned before the end of 2026, and version 1.0 planned sometime in 2027. Check the official channels when you are ready to download, buy, or report feedback; the difference between “playable now” and “planned next” protects the decision.

A habit for reading status updates

When a new update appears, identify the kind of statement it makes. A playable build tells you what can be installed and tested; a milestone tells you what the team has reached; a target window tells you how the release plan is moving. These statements can all be useful without being interchangeable. Keep them separate so a preview does not become a release or a target become a fixed appointment.

Then compare the statement with your own player task. If you want to try the current systems, open the demo and judge Build 0.7. If you are deciding when to return, save the Early Access or 1.0 window as a broad expectation and check again near the decision. If you are sending feedback, name the build and route. That small habit creates a clearer conversation between a changing game and the people playing it. The historical alpha and beta stages can explain why an older feature list looks different, but they cannot tell you how the current demo will feel on your machine or with your party. Use Build 0.7 for that answer, and let the future windows guide when you check again rather than replacing the experience you can play today.