Queen's Domain bosses are easy to misunderstand because the official 100+ enemy total combines mini bosses and bosses without publishing names. This guide separates confirmed facts from unknowns, shows how to identify major enemies in game, and explains why the Executioner door is not a boss.
Queens Domain Bosses: 100+ Enemies, Mini Bosses and Bosses
The confirmed scale of Queen's Domain is broader than a simple “boss list.” The developer states that the game contains 100+ enemies, mini bosses and bosses combined, which means there is no verified split between the three categories. As of 2026-10-31, no individual boss names, health values, phase lists, or official boss count have been published.
That distinction matters for anyone searching for the Queens Domain boss list. A trustworthy list cannot honestly supply dozens of invented names or pretend that every enemy is a major boss. The useful approach is to explain what can be counted, which creatures are actually named, and how to verify the remaining entries through the in-game bestiary.
| Publicly discussed category | Confirmed information | What is not documented as of 2026-10-31 |
|---|---|---|
| Overall enemy roster | More than 100 enemies, mini bosses, and bosses combined | Exact total |
| Major bosses | Bosses exist within the roster | Names, count, health, phases |
| Mini bosses | Mini bosses are included in the combined total | Names, count, separate criteria |
| Named creatures | Mimic, Star Lizard, ojum lizard, eye plants | Any confirmed label as a boss |
| Environment objects | Executioner door received a stuck-object fix | Any boss status or combat role |
What the Official Roster Count Really Means
The most useful answer to the question of how many bosses the game contains is not documented as of 2026-10-31. The only official figure is the combined total of 100+ enemies, mini bosses, and bosses. Subtracting a speculative number of regular creatures would produce false precision, so the combined total should not be presented as a boss count.
The official Steam news feed for Queen's Domain also confirms that the game launched with a substantial bestiary and several technical fixes. However, those patch notes do not reveal a roster taxonomy. They address a Mimic freeze, a floating Star Lizard bag, the Executioner door, and other issues without labeling any creature as a boss.
| Counting approach | Result | Reliability |
|---|---|---|
| Use the developer's combined figure | 100+ enemies, mini bosses, and bosses | High |
| Subtract every non-boss creature | Not possible without a complete published roster | Unreliable |
| Count only creatures with an official boss title | Zero published titles | Accurate but not a total roster count |
| Inspect the in-game bestiary | Player-built inventory of discovered enemies | Requires direct verification |
The Only Publicly Named Creatures
Four creature names are available in official material: Mimic, Star Lizard, ojum lizard, and eye plants. Their appearance in patch notes or gameplay materials does not automatically make them major bosses. The Mimic had a freeze corrected, the Star Lizard had a floating bag corrected, and the ojum lizard can be cooked; those details confirm they exist without establishing their category.
This is why the phrase “Queens Domain all bosses” cannot be answered with a definitive named checklist. A complete list depends on what the game itself marks as a boss, and that classification is not documented publicly. The Queen's Domain monsters guide is useful for separating named creatures, lore questions, and roster gaps without assigning unsupported roles.
Queens Domain Boss Guide: Why No Boss Names Are Published
The absence of published names is the central limitation of any Queens Domain boss guide. The developer has described the scale of the enemy roster, but has not released a labeled bestiary, boss checklist, region list, or encounter guide. Any page claiming to list named bosses with health bars, weaknesses, and phases would be inventing details beyond the official record.
This does not make the game untestable. It changes the research method from web-based name matching to in-game observation and documentation. You can still record where an encounter occurs, what the enemy does, which attacks force movement, and whether the bestiary adds an entry after the fight.
Confirmed Facts Versus Unknown Details
The combat foundation is confirmed. A stamina meter governs attacks, melee weapons have weapon-specific special attacks, and the game includes charge attacks plus more than 20 types of throwing weapons. Those facts support practical preparation, but they do not establish which enemies use a particular attack or what any boss's health pool contains.
| Question | Verified answer | Best next step |
|---|---|---|
| Are bosses present? | Yes, within the combined 100+ roster | Identify major encounters in game |
| Are their names published? | No official names as of 2026-10-31 | Read the bestiary entry |
| Are phases documented? | No | Record visible attack-state changes |
| Are weakness values published? | No | Test cautiously and record observations |
| Are mini bosses counted separately? | No | Inspect enemy presentation and bestiary classification |
| Was the Executioner door a boss? | No; it is a door | Treat the patch note literally |
The correct boss list is therefore the in-game bestiary, not a copied list of achievement names. The public achievement display includes titles such as Unsealed Tomb, Halls of Hatred, and Sin Keeper, but these titles do not prove that an area or enemy has a matching name. For the broader achievement context, see the 53-achievement name file.
A Documentation Template That Avoids False Claims
When recording an encounter, use categories that can be supported by observation rather than assumptions. A practical entry can include the enemy’s bestiary name, the location reached immediately before the fight, the visible weapon or body shape, the attack behavior, and the reward or bestiary change.
| Record field | Example format | Reason it helps |
|---|---|---|
| Bestiary name | Copy exactly from the entry | Prevents name invention |
| Encounter type | Major enemy or mini boss, as shown in game | Preserves the game's classification |
| Location | Describe the route or nearby landmark | Finds the encounter later |
| Offense | Summarize observed attacks | Supports preparation |
| Stamina pattern | Note which actions created openings | Helps with resource planning |
| Outcome | Defeated, escaped, or interrupted | Tracks completion honestly |
Because weapons can evolve and enemies killed before death do not respawn on continue, keeping personal notes is particularly useful. A route that changes after a death may otherwise look like a missing boss. The guide to beating Queen's Domain bosses expands on those encounter-testing considerations.
Queens Domain Boss List: How to Identify a Boss in Game
No official visual rule separates every major enemy from a mini boss, so identification requires several observations at once. Look for a dedicated arena or route blockage, a distinct enemy presentation, a sustained combat sequence, and a bestiary entry that appears or updates after the encounter. One signal alone—such as a large enemy or a long health bar—is not conclusive.
Start with the Mimic because it is one of only four publicly named creatures and had a specific freeze fixed in version 1.01.01. A player who encounters a Mimic can record it immediately instead of assuming it is an ordinary enemy. That does not establish it as a boss, however, and its official patch-note identity should not be expanded into unsupported lore or mechanics.
The Six-Signal Boss Check
Use this sequence after an unusual or demanding encounter. It separates a major boss from a mini boss or regular enemy while remaining honest about categories that the public documentation has not defined.
| Signal | What to inspect | Confirmed or player-derived |
|---|---|---|
| Encounter framing | Arena, blocked route, or scripted sequence | Player observation |
| Presentation | Unique silhouette, behavior, or attack setup | Player observation |
| Combat duration | Sustained encounter versus brief skirmish | Player observation |
| Bestiary response | New entry or updated description | In-game verification |
| Reward signal | Item, progression, or unlock | In-game verification |
| Enemy label | Boss or mini boss wording, if shown | In-game verification |
Do not use a fixed health percentage to classify an enemy, because exact boss health and damage values are not documented. Instead, record relative outcomes in your own notes. “Required two attempts” may be useful, but present it as a player report rather than an official difficulty rating.
What to Do Before Engaging
Preparation should focus on confirmed systems: stamina, charge attacks, weapon-specific specials, and available throwing weapons. If you enter with a new weapon, learn its normal attack and special move before testing them under pressure. Food can raise stats, and a life charm raises life points, but the source of either item is not publicly documented, so any preparation route must be verified in game.
For an observed mini boss, preserve stamina for movement and avoid spending every recovery window on repeated attacks. For a suspected major boss, the same logic applies, but the longer encounter makes retreat planning more important. Detailed movement and spacing considerations appear in the Queen's Domain stagger guide.
Verification Workflow for a New Enemy
First, defeat or approach the creature enough to see how it behaves. Second, note whether the encounter ends the normal route, changes the room, or triggers a separate bestiary response. Third, inspect the bestiary entry with the controller's scrolling function. Fourth, record the name and classification exactly as displayed. Fifth, test the encounter again only if the entry remains ambiguous.
| Step | Action | Record |
|---|---|---|
| 1 | Observe the creature before committing | Visual and behavioral features |
| 2 | Compare with ordinary encounters | Whether the fight is structurally distinct |
| 3 | Check the bestiary afterward | Exact name and visible category |
| 4 | Note the route | Reliable method for revisiting it |
| 5 | Confirm rewards or changes | Whether the entry or loadout changed |
This workflow is especially helpful when players share conflicting reports. Community experience can reveal patterns, but labels should still come from the game itself. The Queens Domain mini bosses are best identified by verified bestiary entries rather than by community assumptions based on size or location.
Queen's Domain All Bosses: The Executioner Door Is Not a Boss
The Executioner door is the most important misconception to clear up in any discussion of Queen's Domain bosses. It is a door, not an enemy or character. Version 1.01.01 corrected an issue that caused the door to get stuck, placing it in the same technical-patch category as the Pit of Despair soft lock and a Mimic freeze.
That distinction prevents a common error: a dramatic-looking name can cause players to add an environmental obstacle to a boss checklist. A door can still be strategically important, especially if it gates access to a serious encounter, but “important obstacle” and “combat boss” are different categories.
| Item in the patch note | Correct classification | Why |
|---|---|---|
| Executioner door | Door or access obstacle | The patch says it got stuck |
| Mimic | Named creature | A freeze affected it |
| Pit of Despair | Named location | A soft lock occurred there |
| Star Lizard bag | Inventory or world object | A floating bag was corrected |
| Weapon evolution freeze | System interaction | The freeze occurred while weapons evolved |
How to Handle a Blocked Door
If a door will not open, first confirm that it is still affected by a bug. Version 1.01.01 is listed as fixing the issue, so an unpatched copy may behave differently from a current build. Update the game, return to the door, and avoid repeatedly using it as though a hidden combat trigger will eventually respond.
If the door opens but leads into an encounter, record the route from the entrance rather than treating the door as the enemy. This distinction also keeps personal boss notes cleaner: list doors, traps, and traversal gates separately from creatures. The early and late boss notes can use the same separation when documenting progression.
Why No Fixed “First Boss” Exists in Public Data
The query about the Queen's Domain first boss has no verified public answer. No published boss order, region list, chapter structure, or map identifies the first major encounter. The only named official locations are Isle of Neasied and Pit of Despair, and neither is documented as a boss arena.
A player's first boss may also depend on the route taken through an interconnected island containing secrets and shortcuts. Until the in-game bestiary and route order are checked directly, naming a “first boss” as fact would exceed the available information.
| Possible answer to “first boss?” | Evidence status | Better wording |
|---|---|---|
| A named creature | No official major-boss label | Not documented as a boss |
| Pit of Despair encounter | Location is named, encounter is not | Verify in game |
| First mini boss | Category order is unknown | Player-specific discovery |
| First bestiary boss entry | Depends on route and classification | Record your first verified entry |
Queens Domain Bosses and the Bestiary: Recording Every Discovery
The bestiary is the game's in-game encyclopedia and is the best source for building a Queens Domain boss list. Its entries can be scrolled with a controller, and discovered creatures can provide a record of what you have actually encountered. However, the official Steam achievement page shows that only ten of 53 achievement display names are public, and all unlock conditions remain undocumented.
This means achievement names should not be used as a substitute for the bestiary. Titles can hint at story milestones without revealing which enemy corresponds to them. Even the achievement named Sin Keeper is not official evidence of a boss called Sin Keeper, because its condition is not documented.
A Complete Bestiary Record
A complete player record should separate six fields: enemy name, classification, location, combat notes, completion state, and screenshot reference. The screenshot reference is especially useful because a bestiary entry can be easier to recognize than a text description, particularly for visually similar creatures.
| Field | Required entry | Verification source |
|---|---|---|
| Enemy name | Exact bestiary label | Bestiary |
| Classification | Boss, mini boss, or ordinary enemy | Bestiary or game presentation |
| Location | Route from the last recognizable landmark | Personal exploration notes |
| Attack notes | Observed close-range and ranged behavior | Player log |
| Completion | Defeated or not yet defeated | Personal log |
| Evidence | Screenshot number or note date | Player archive |
Start the log when the bestiary entry first appears, not only after a victory. This preserves a valuable sequence: when the enemy was encountered, what the loadout was, and whether the player needed multiple attempts. Since exact boss health and damage numbers are not published, personal attempt counts are best treated as anecdotes rather than balance benchmarks.
Turning the Log Into a Practical Guide
Once several encounters are recorded, compare them by stamina pressure rather than by invented weakness categories. The documented combat economy revolves around stamina, charged attacks, melee specials, and throwing tools. A boss that repeatedly interrupts recovery may create a different resource problem from one that pressures movement.
| Recorded pattern | Preparation focus | Result |
|---|---|---|
| Long close-range strings | Preserve movement stamina | More space to read the next attack |
| Aggressive pursuit | Prioritize escape routes | Fewer forced resource losses |
| Frequent ranged attacks | Keep a throwable option ready | More room to reposition |
| Weapon special performs well | Test it during a safe attempt | Earn confidence before committing |
| Special consumes too much stamina | Alternate attacks and spacing | Reduce empty recovery windows |
Do not assign a numerical weakness unless you have clearly separated your observation from the official record. The safest useful statement is “my test suggests,” followed by the weapon, encounter, and conditions. That preserves credibility and makes the guide more useful to other players.
Practical Boss Tracking Checklist
A concise tracking sheet can prevent several common errors: adding the Executioner door to the roster, treating the four named creatures as a complete boss list, or assuming the 100+ figure counts bosses alone. Record only what the game shows and distinguish published facts from personal discoveries.
| Checklist item | What to verify |
|---|---|
| Update status | Current patch installed |
| Enemy name | Copied from the bestiary |
| Enemy class | Shown or observed in game |
| First location | Route recorded |
| Combat behavior | Summarized without invented values |
| Stamina experience | Personal observation |
| Completion state | Defeated, escaped, or undiscovered |
| Screenshot | Saved for later comparison |
| Official versus personal note | Clearly labeled |
The key takeaway is simple: Queen's Domain contains a large combined roster, but its public boss information is intentionally sparse. Use the official 100+ enemies, mini bosses and bosses combined figure, verify names in the bestiary, keep the Executioner door in the environmental-obstacle column, and record your own observations without presenting them as developer-confirmed lore.
Frequently Asked Questions
How many bosses are in Queen's Domain?
The exact number is not documented as of 2026-10-31. The developer confirms more than 100 enemies, mini bosses, and bosses combined, but does not publish a separate total for major bosses or mini bosses. Your most accurate count comes from the in-game bestiary and the classification shown for each discovered enemy.
What is the first boss in Queen's Domain?
There is no verified official first-boss name as of 2026-10-31. No published map, chapter order, or region list identifies one, and route choices across the interconnected island may change which qualifying enemy appears first. Record the first enemy explicitly labeled as a boss or mini boss in the game.
Are the Mimic and Star Lizard bosses?
Their names are officially documented, but neither is publicly labeled a major boss. Version 1.01.01 mentions a Mimic freeze and a floating Star Lizard bag. Verify their classification and bestiary entries in game before adding them to a Queens Domain all bosses checklist.
Is the Executioner door a boss?
No. The Executioner door is an environmental door whose stuck condition was fixed in version 1.01.01. It is not a character or combat encounter. Keep it separate from boss records, although it may still lead to a genuine boss encounter that should be documented on its own.
Can I make a complete boss list from the achievements?
Not reliably. Although Steam exposes ten achievement display names, their unlock conditions are not documented as of 2026-10-31, and an achievement title does not prove an enemy has the same name. Use the in-game bestiary as the primary source for a Queens Domain boss list, then use achievements only for separate progression tracking.