Dimraeth's roadmap aims to expand the world, playable races and classes, late-game progression, bosses, crafting, building and story throughout Early Access. The developer also plans continuing combat, co-op and progression tuning. These are development goals rather than a dated release calendar. The estimated eighteen-to-twenty-four-month Early Access window has no fixed exit date.
As of October 9, 2026, the current game and its released patches should be kept separate from those future additions. A plan is not proof that its feature can already be played, and a patch fixing an existing system is not automatically the arrival of a new content milestone. Use the distinction below when deciding whether to buy, return or wait for a specific feature.
What the official plan actually covers
The Early Access answers describe six main areas of expansion, alongside ongoing tuning. They identify the type of work without naming every future zone, class, boss or delivery date. That is enough to understand the intended direction, but not enough to fill a month-by-month schedule.
| Development area | Present baseline | Planned direction |
|---|---|---|
| World | Opening route through the Lost Caverns, Earlwood Village and Wildwood Forest | New biomes and zones beyond Earlwood and Wildwood |
| Character options | Human, Minotaur and Elf; Brawler, Mage and Shadow | Additional playable races and classes |
| Progression | Working attributes, skill trees, equipment tiers and upgrades | A higher later-game skill and equipment ceiling |
| Bosses | Multiple encounters in the available game | More boss encounters |
| Crafting and building | Existing crafting and base-building loop | Deeper options within those systems |
| Story | The Early Access Act I release | A longer overall story arc |
| Tuning | Current combat, co-op and progression | Continued changes based on community play |
The published graphic uses a historical Fall 2026 Early Access window; Update I and Full Release remain TBA.
More world space is planned, not already unlocked
The current Early Access description identifies a starter route from the Lost Caverns through Earlwood Village into Wildwood Forest. The development plan calls for biomes and zones beyond the existing Earlwood and Wildwood regions. That supplies a boundary between the world available now and the larger world being built.
The September Early Access content announcement already described the expanded Wildwood and Goblin Caves as additions for that release. Those belong to the launch scope, not automatically to the next future milestone. Calling an already released region upcoming makes a roadmap look more active while giving players the wrong expectation.
If you are waiting for more exploration, use the next official content announcement to establish the new area's status and entry requirements. The current map guide owns the available-region question. This roadmap does not invent an entrance or hidden route to an area that has not been established as released.
The present roster and the larger character target
The current Steam Early Access answer lists three playable races and three classes. Broader store copy describes eight races and six classes, producing forty-eight combinations. Treat the larger figures as planned scope instead of telling a returning player that those options should already appear at character creation.
The target does not establish the missing options or their launch order. Use the classes guide and race guide for the currently playable choices.
Compare the future expansion plan against the scope described as playable now.
Later-game progression will expand
The plan describes an expanded late-game skill and equipment ceiling. The launch announcement identifies a level cap of twenty-five for the Early Access endgame, and the September content announcement says that cap is intended to increase with each new act. Those statements explain the direction of progression without supplying the future level cap for every act.
Do not treat a current ceiling as a permanent ceiling for the eventual game. Equally, do not assign a new cap before a released update establishes it. A roadmap statement about raising the limit cannot tell you how many skill points, equipment tiers or additional encounters a later version will contain.
If you have reached the current limit, you can decide whether the existing repeatable systems remain interesting while you wait. The current max-level guide covers that state, and the boss replay guide covers an available activity. This roadmap does not turn unreleased progression into a checklist you can complete now.
Boss, crafting and building plans need concrete releases
More bosses and deeper crafting and building options are explicit parts of the intended full-version expansion. The current game already contains multiple bosses, crafting stations, resource processing and base development. The plan expands existing pillars rather than introducing proof that those pillars are absent today.
A longer story is a goal, not a dated next act
The Early Access launch announcement identifies Act I across three chapters. The full-version plan calls for a longer overall story arc. That establishes a difference between present story scope and intended future scope without fixing the date of the next act.
The September 21 notes address quest completion when a player and Aelwynor die at the same time. September 23 addresses the Forest King restarting from the three-seed phase after a wipe. October 5 includes restoring closing dialogue if death interrupted it. Those are examples of work on the current story encounter, not evidence that the campaign endpoint moved to an unannounced later chapter.
Use the walkthrough for the supported current route. If you have reached its endpoint, the absence of another objective may reflect the present content boundary. The roadmap gives a reason to follow later developments; it cannot reveal a hidden next act in the current game.
The latest near-term project has a dated context
The October 5 release note describes a project to make client-side monster attacks smoother, especially for players with higher ping. The developer expects progress that month. In that announcement, this month means October 2026. It should not be repeated indefinitely as a promise for whichever month a reader happens to arrive.
That wording describes work and expected progress. It does not say every high-ping issue is fixed, promise an exact completion day or identify a future patch number that will finish the project. Keep the status of the project separate from the individual hotfixes listed in the same post.
Shipped patches and future content are different records
Recent updates provide concrete examples of the development loop. September 25 changes multiplayer protections and fixes a world-name collision that could overwrite a world. The same patch makes the Hoard King bounty respawn the Goblin Caves immediately. October 5 addresses crafting-queue persistence and other current systems.
These changes matter to players, but they should not be counted as new races, new regions or a longer story simply because they are updates. A hotfix can improve the existing loop without fulfilling a broad content-expansion milestone. Conversely, a major content addition can still require later fixes.
| Announcement wording | Best way to read it |
|---|---|
| A feature is planned | Direction of development, not availability |
| Work is underway | Active effort, without a guaranteed finish date |
| Progress is expected in a named period | A dated expectation, not proof of completion |
| A patch addresses a bug | A change to the stated case, not universal recovery |
| A feature is released | Check its version and actual scope |
No fixed Early Access exit date
The developer's estimate of eighteen to twenty-four months provides a planning range while prioritising quality and milestones. It is not a commitment to a particular date in 2028 or a guarantee that the project cannot take longer. A calculated calendar endpoint would still be a calculation rather than an announced launch.
If your purchase depends on completion, use the current product as the decision baseline and wait for an explicit full-release announcement. The release-date guide separates the already completed Early Access launch from the open full-release question. Keeping that boundary avoids reading a historical launch countdown as a present development deadline.
Price and platform expectations remain separate
Mudtek plans gradual price increases as content and polish grow, followed by a higher full-release price. That does not specify which roadmap item triggers the next increase or how large it will be. Use the price guide for the checked price and historical launch offer, then check your actual storefront.
A content roadmap is also not proof of a platform port. The current supported product is the Windows Steam release; console plans in the official FAQ remain unconfirmed. Mobile and console dates cannot be derived from the Early Access duration estimate.
Follow the milestone that matters to you
Choose the feature you are waiting for and look for an announcement that establishes its actual status. For a class, that means a playable addition; for story, a released continuation; for a smoother client experience, an update describing the relevant improvement. A broad expression of ambition is not an interchangeable answer to all three.
You can give feedback about what matters to you without treating a request as a commitment. The developer identifies Discord, Steam reviews and discussion threads as places it follows. A clear description of the player problem can inform development; it does not create a guaranteed deadline.