The Queen's Domain OST is a real, released product: an official soundtrack entry appeared on Steam as a separate music release on 2026-10-30, the same day as the game, and the composer is credited as Eric Berger of Biogenesis, one half of the two-person development team; the store description also states that the release contains 55 tracks. This guide confirms what that listing establishes, what it still does not publish, and how the surrounding roadmap, DLC and bug-reporting picture looks as of 2026-10-31.
The Queen's Domain OST Release Status
The soundtrack is confirmed rather than rumored. Steam carries a separate music product titled Queen's Domain - Original Soundtrack under app 5255650, with a release date of 2026-10-30 and a short description naming Eric Berger of Biogenesis, one half of the dev duo, as the composer, and text stating that the release includes 55 tracks. That is a stronger status than a teaser: it is a storefront product entry with a title, a type, a date and a credit.
The official pricing announcement also refers to an Official Soundtrack alongside a game-plus-soundtrack bundle, which means the music was planned as part of the launch offering rather than as an afterthought. The distinction matters because a soundtrack can exist in several forms, and only some of them are confirmed here.
| Queens Domain OST question | Confirmed status as of 2026-10-31 | What buyers can verify |
|---|---|---|
| Separate soundtrack product | Released on Steam as a music entry on 2026-10-30 | Open the music listing and confirm the title |
| Composer credit | Eric Berger (Biogenesis), named in the official description | Read the product description on the listing |
| Game plus soundtrack bundle | Mentioned in the official pricing announcement | Check the bundle page for exactly what is included |
| Track count | 55 tracks, per the official store description | Open the music listing to confirm |
| Track names and order | Not published | Verify on the store page |
| Total runtime | Not documented | Check the listing once durations are shown |
| Formats and download size | Not documented | Verify on the store page before purchasing |
| Physical release | Not documented | Do not assume a disc or record exists |
| Included with the base game | Not documented as a native extra | Verify in your own library after purchase |
What the Official Soundtrack Listing Confirms
Three facts are solid enough to plan around. First, the soundtrack exists as a distinct product rather than only as in-game audio. Second, it carries an official title, Queen's Domain - Original Soundtrack, so a buyer can identify the correct listing instead of relying on fan uploads. Third, the composer credit is published as Eric Berger, which resolves the most common question about who wrote the score.
The release timing is equally clear. The music entry shares the game's 2026-10-30 date, so the soundtrack belongs to the launch window rather than to a later anniversary edition. That does not prove every track was finished before launch, but it does establish that the product was published alongside the game.
What the Soundtrack Listing Does Not Publish
Several details remain unpublished, and they should be described as unknown rather than guessed. The store description states 55 tracks, but the individual track names and their order are not published; a total runtime and the audio formats offered are also undocumented. It also does not state whether the soundtrack files are included automatically with every copy of the game, or whether the music entry must be obtained separately.
Physical media is another open question. No disc, record or other physical edition is documented as of 2026-10-31, and no label or pressing details have been published. Buyers interested in a collector version should wait for an official product page that names the format and region rather than assuming one is planned.
-
Confirmed: title, product type, release date and composer credit.
-
Not documented: track names and order, runtime, file formats and download size.
-
Not documented: whether the score is bundled natively with the base game on every platform.
-
Not documented: physical editions, vinyl, label and pressing details.
Game Plus OST Bundle Contents and Value
The official pricing post mentions a game-plus-soundtrack bundle, so the bundle itself is not speculative. What remains unclear is the exact composition of that package and how its price compares with buying the two products separately. Those details are not documented as of 2026-10-31.
The confirmed game package is substantial on its own. Queen's Domain is a single-player retro-fantasy action RPG and dungeon crawler with 50+ findable melee weapons, 20+ types of secondary throwing weapons, weapon-specific special attacks, charge attacks and a stamina meter. It also includes an interconnected island, XP progression, food that raises stats, and more than 100 enemies, mini bosses and bosses combined. The developer describes the experience as at least 40+ hours.
| Purchase factor | Confirmed information | Still undocumented |
|---|---|---|
| Core game | Single-player retro-fantasy action RPG | Nothing material; the game listing is public |
| Soundtrack | Separate Steam music entry, 2026-10-30, 55 tracks | Track names and order, runtime and formats |
| Bundle | Mentioned in the official pricing post | Exact contents, combined price and discount rules |
| Composer | Eric Berger (Biogenesis) | Any additional arrangers or performers |
| Platform availability | Game on PC, PS5, Xbox Series and Switch 2 | Whether the music product follows on every platform |
| Upgrade path for owners | Not documented | Whether existing owners receive a discount |
Why the Standard Edition Is Not the Bundle
A standard purchase and a bundle are different products, even when both include the game. The bundle is the package that pairs the game with the soundtrack, while the standard edition is the game alone unless its own description says otherwise. Because the bundle contents are not itemized in the public material, buyers should read the package description rather than infer inclusion from the price.
The launch price of the game was $19.99, €19.49 or £15.99 with a time-limited 15% discount. Those figures describe the game, not the soundtrack and not the bundle, so they cannot be used to calculate the value of the music package. A lower bundle price would only be meaningful once the included products are listed.
Checking What the Soundtrack Bundle Contains
Before buying, compare the storefront metadata with the official announcements instead of trusting a search-result snippet. The useful checks are simple and take only a minute, but they prevent paying twice for the same game or expecting files that are not part of the package.
-
Read the exact package title and the list of included products.
-
Confirm whether the soundtrack is a download, a streaming entitlement, or bundled media.
-
Check whether the package includes the base game or only the music.
-
Compare the bundle price with the separate game and soundtrack listings.
-
Verify whether existing owners receive a discounted upgrade.
-
Save a screenshot of the description, because store pages can change after launch.
Patch history does not answer these questions. The demo hotfixes 1.0.1 through 1.0.3 and launch version 1.01.01 document game fixes, not soundtrack contents, so a version number should never be read as evidence about tracks or bundle terms.
The Queen's Domain Roadmap, DLC, and Future Updates
There is no announced Queen's Domain roadmap as of 2026-10-31. No future version number, planned feature list, release window, test branch or development timeline has been published. The same applies to downloadable content: no Queen's Domain DLC has been confirmed, and there is no documented plan for story expansions, new regions, additional bosses, character campaigns or costume packs.
| Planned-content category | Official status on 2026-10-31 | Reason it remains uncertain |
|---|---|---|
| Queens Domain roadmap | Not announced | No published milestone document |
| Queens Domain DLC | Not announced | No title, teaser, release date or content brief |
| Queens Domain future updates | Not scheduled | No version beyond 1.01.01 is documented |
| Seasonal events | Not announced | No event calendar or event names |
| New regions or bosses | Not announced | Official place and creature lists are limited |
| New story chapters | Not documented | No chapter structure has been published |
| Cross-save and cross-play | Not documented | No official platform confirmation |
| Soundtrack | Released 2026-10-30, 55 tracks | Track names, runtime and formats remain unpublished |
Reading Official News Without Turning It Into a Roadmap
The Queen's Domain Steam announcements provide the strongest available timeline. They cover the 1.01.01 patch, three demo hotfixes, the PC Gaming Show reveal, launch wishlist milestones, pricing with the soundtrack and bundle mention, and Steam Deck verification. Those announcements show an active release process, but activity is not the same as a roadmap.
For example, the wishlist campaign reached 300,000, following earlier milestones at 100,000, 200,000 and 275,000. A wishlist milestone is a sales milestone, not proof of a specific future feature. Similarly, the developer's claim of a 40+ hour experience communicates the stated scale of the game, not a promise of additional hours through DLC.
Players seeking concrete details about named enemies can consult the guide to Queen's Domain enemy types. It separates the four officially documented creature names, Mimic, Star Lizard, ojum lizard and eye plants, from the Executioner door, which is an object associated with a patched bug rather than a character.
Signals That Do Not Prove Future Content
Several kinds of posts are often mistaken for development plans, but they reveal different levels of certainty. A roadmap entry may identify planned content without naming a soundtrack track, while a soundtrack release confirms a composition without establishing that it belongs to a future update. Similarly, a Discord poll may gauge community interest, but it does not equal developer approval.
-
A bug fix suggests maintenance, not a major expansion.
-
A new screenshot may highlight existing content.
-
A wishlist milestone does not identify the reward.
-
A Discord question does not establish a developer commitment.
-
A community-created concept project is not official Queen's Domain content.
The team's official Discord description identifies a two-person United States studio founded in 2021, with work on Queen's Domain beginning in 2023. It also connects the team to The New Flesh and several game jams. That background may help explain the game's scope, but it cannot establish a release schedule for Queens Domain DLC.
A Defensible Way to Track Updates
Use a three-column watchlist instead of relying on speculation: label each Queens Domain update by evidence, then track the Queens Domain roadmap, DLC and future updates separately from known issues and bug reports. This prevents a roadmap mention, a soundtrack listing and a confirmed release note from being treated as equivalent.
-
Officially announced: named feature, stated purpose, and developer or publisher source.
-
Under discussion: a question, poll, suggestion or community topic with no commitment.
-
Unverified: artwork, rumors, datamined labels or posts without a traceable official source.
The soundtrack now belongs in the first column because it has a titled product listing, a date and a composer credit. Its unpublished track details belong in a separate notes field rather than being treated as evidence that the release is incomplete or unconfirmed.
Where to Send Queen's Domain Bug Reports
Reliable Queen's Domain bug reports should reach the developer through a channel that preserves the platform, build number, reproduction steps and affected area. The official Steam community hub is the most appropriate public route for PC reports because it keeps the discussion attached to the correct game. The official Queen's Domain Discord server may also be used when its report channels are available to the player.
| Report component | What to include | Why it helps |
|---|---|---|
| Build version | Exact version shown in-game | Separates fixed issues from new ones |
| Platform | PC, PS5, Xbox Series or Switch 2 | Identifies platform-specific behavior |
| Location | Isle of Neasied, Pit of Despair or another exact area | Helps reproduce the issue |
| Reproduction steps | Short sequence from a stable starting point | Reduces follow-up questions |
| Expected result | What the game should have done | Distinguishes bugs from unclear rules |
| Actual result | What happened instead | Identifies the failure mode |
| Evidence | Screenshot, clip or error text | Preserves visual and technical details |
A Report Format Developers Can Reproduce
Start with a one-sentence summary that names the platform and version. Follow it with the location, the exact actions performed, the expected behavior and what actually happened. Finish with whether the issue can be reproduced every time, occasionally or only once.
A strong report might say that version 1.01.01 on a specific console produces a freeze during a weapon evolution attempt after entering a named area, then lists the controls used. It should avoid unsupported claims about a boss, hidden region or mechanic. Accuracy matters because the only named creatures and places currently documented are a limited set, and inventing labels can make a report harder to classify.
When documenting an apparent fall or map-boundary problem, compare it with the Queen's Domain fall-damage and off-map recovery guide. That guide can help distinguish the documented water return pits around Neasied from other falls, but the official water-return feature should still be checked in the player's current version.
Screenshots, Video, and Save Details
Attach a screenshot when the problem concerns positioning, a missing interface element or an incorrect visual state. A short clip is more useful than a long recording when the failure happens during combat or traversal. Preserve the original file rather than taking a photo of a monitor when image quality or text is relevant.
Do not upload an entire save file unless a developer specifically requests it. Instead, note the platform, version, approximate playtime and whether the same state was reached from a fresh save. If the game freezes, describe the last confirmed action rather than claiming the cause.
What Not to Submit
Several reports create more noise than useful information, especially when they describe a vague problem without identifying the encounter, weapon effect or encounter phase involved. A report stating only that a special attack does not work is less actionable than one that specifies the weapon, the target, the attack's expected behavior and whether the issue occurred during a boss fight or normal combat.
-
A difficulty complaint without the encounter or mechanic involved.
-
A request for a particular weapon, region, boss, DLC or roadmap item.
-
A reproduction video that begins after the relevant event.
-
Several duplicate comments in different channels.
-
An accusation that another player is cheating without verifiable evidence.
Reports about weapons or their special attacks can be supplemented with the Queen's Domain weapon effects reference. That resource separates documented weapon behavior from community interpretation, helping users focus the report on an observed defect rather than an undocumented expectation.
Queen's Domain Known Issues After Version 1.01.01
Version 1.01.01 is the only full launch version documented as of 2026-10-31. Its patch notes confirm fixes for six specific problems, but the release does not include a complete statement that every issue has been eliminated. The following table therefore describes confirmed fixes, not a universal list of every currently occurring defect.
| Issue addressed in 1.01.01 | Documented status | Best verification |
|---|---|---|
| Pit of Despair soft lock | Fixed | Enter the area and test progression through the sequence |
| Freeze when weapons evolve | Fixed | Evolve a weapon under normal inventory conditions |
| Executioner door getting stuck | Fixed | Reach and interact with the door |
| Mimic freeze | Fixed | Trigger an encounter with the Mimic |
| Missing water return pits around Neasied | Fixed | Verify the relevant water-return paths around Neasied |
| Star Lizard bag floating in the air | Fixed | Check the Star Lizard drop or bag location |
| Unlisted launch bugs | Not documented | Submit a reproducible report with version details |
The earlier build history includes demo hotfixes 1.0.1, 1.0.2 and 1.0.3. The demo also established an important save rule: enemies killed before death do not respawn when a player continues. That behavior is documented, but the available baseline does not provide a full changelog for every demo fix. The Queen's Domain demo hotfix guide provides a focused account of those builds and their relationship to the launch patch.
Confirming a Fix in Your Own Game
Verification should be consistent across platforms and save states. First, confirm that the installed build is 1.01.01 or a later numbered build if one appears. Then reproduce the original sequence without using unrelated shortcuts that could hide the problem. For the Pit of Despair, test the route that previously produced the soft lock. For the Mimic, engage the creature under ordinary combat conditions and check that the encounter continues.
Record the result even when the issue is gone, but classify it accurately rather than marking every successful check as a universal fix. If weapon evolution still freezes, capture the input sequence and build number. For the door, Star Lizard bag and Neasied water return pits, record the location and save-state conditions, since a single successful route may not confirm every affected path.
| Verification result | What it means | Recommended action |
|---|---|---|
| Fixed on every attempt | The tested sequence no longer reproduces the issue | No report needed unless behavior differs from expectations |
| Occasional failure | A timing, save-state or input condition may be involved | Note frequency, location, input method and nearby effects |
| Reproducible failure | The patch note may not cover this case | Submit a report with version and exact steps |
| Unable to test | The area or state was not reached | Keep the issue as unverified rather than claiming a fix |
| New crash or freeze | A separate defect may be present | Submit the original capture and recent reproduction steps |
Known Issues Versus Unverified Player Experiences
The official patch notes name specific fixed defects, but community experience can surface problems that are not in the changelog. Those experiences should be labeled as reports until verified. A player may describe a freeze near an area, but the report should not attach an invented enemy or object name to it. Similarly, difficulty complaints should be separated from technical defects.
The Queen's Domain known issues currently associated with the official record are historical entries resolved in 1.01.01. The launch patch itself did not publish a long list of unresolved bugs as of 2026-10-31. That means the most accurate known-issue table consists of what was fixed, what changed in the demo, and what remains undocumented, not an invented list of unresolved problems.
The Practical Update Checklist
Before reporting a possible audio or stability regression, complete this sequence in order and treat each result as evidence for the next step: first verify whether the change is genuinely absent, then compare the same gameplay moment against the current 1.01.01 patch, and finally distinguish a new behavior from a legitimate difference caused by progression, route selection or save-state conditions.
-
Confirm the exact game version.
-
Note the platform and input method.
-
Record the precise location without adding an unofficial name.
-
Reproduce the problem from the same save state.
-
Check whether the sequence appears in the 1.01.01 patch notes.
-
Capture a screenshot or short clip.
-
Submit the report through the official community channel.
This workflow reduces duplicate reports and prevents fixed issues from being described as current. It also gives the development team enough information to distinguish a patch regression from a misunderstanding of an undocumented mechanic.
What Is Confirmed and What Still Awaits Announcement
As of 2026-10-31, the soundtrack picture is partly settled. The Queen's Domain - Original Soundtrack exists as a separate Steam music entry released on 2026-10-30, composed by Eric Berger, and the official pricing announcement refers to an Official Soundtrack plus a game-plus-soundtrack bundle. Those are confirmed products, not rumors.
The remaining gaps are specific rather than mysterious: individual track names and their order, runtime, file formats, whether the music is included natively with every copy of the game, bundle contents and pricing, and any physical edition are all unpublished as of 2026-10-31. Buyers should verify those details on the store page instead of assuming them.
The update baseline is narrow and concrete: demo hotfixes 1.0.1 through 1.0.3, launch version 1.01.01, and six named fixes in that launch patch. No roadmap, DLC plan, seasonal event or scheduled future update has been announced. For technical problems, players should include the version, platform, location, reproduction steps, expected result and actual result in a report through the official Queen's Domain community channels.
Frequently Asked Questions
Is the Queen's Domain OST released?
Yes. A separate Steam music entry titled Queen's Domain - Original Soundtrack was released on 2026-10-30, the same day as the game. The official description credits Eric Berger as the composer. The store description lists 55 tracks; individual track names, runtime and file formats are still not documented, so check the store listing before buying.
Does a game and soundtrack bundle exist?
The official pricing announcement mentions an Official Soundtrack plus a game-plus-soundtrack bundle, so the bundle is a confirmed offering rather than a rumor. Its exact contents, combined price and upgrade rules for existing owners are not documented as of 2026-10-31. Read the package description before purchasing to avoid buying the game twice.
Is there a Queen's Domain roadmap or DLC plan?
There is no published Queen's Domain roadmap, DLC announcement, seasonal-event calendar or scheduled future-update date as of 2026-10-31. Official announcements cover launch, pricing with the soundtrack and bundle mention, wishlist milestones, demo hotfixes and version 1.01.01. Community requests should not be treated as a release commitment without developer details.
Where should I submit Queen's Domain bug reports?
Use the official Steam community hub for PC reports or the developer's official Discord server when an appropriate support channel is available. Include the exact version, platform, precise location, reproduction steps, expected behavior, actual behavior and a screenshot or short clip. Avoid unsupported enemy, weapon, region or chapter names because the official material lists very few proper names.
What did version 1.01.01 fix?
Version 1.01.01 fixed a Pit of Despair soft lock, a weapon-evolution freeze, the stuck Executioner door, a Mimic freeze, missing water return pits around Neasied, and a floating Star Lizard bag. These are confirmed historical fixes, not proof that every possible issue has been resolved. Reproduce the affected sequence in the current build before reporting a supposed regression.