Patch 1.01.01 matters because it repairs six progression blockers without announcing a published route overhaul. Its effects are especially relevant to the Queens Domain speedrun, achievements route, and collectible checklist: fixes to exploration, long weapon sessions, and collectible or achievement detection can prevent valid progress from being interrupted or misread. Because no new regions, bosses, items, or faster progression order are announced, the patch should be treated as a targeted stability update rather than a route-changing patch, with run plans adjusted only where the repaired progression checks affect timing or completion.
The official Queen's Domain Steam news feed identifies the update as a focused bug-fix release. It does not announce new regions, bosses, items, or a faster progression order, so the safest response is to treat 1.01.01 as a stability patch and adjust a run plan without assuming that any area became faster or newly accessible.
Queens Domain Patch 1.01.01: Six Confirmed Repairs
Version 1.01.01 delivers six targeted repairs spanning progression, combat, traversal, recovery, and interactable behavior. The most route-critical correction is the Pit of Despair soft lock, which could otherwise block continued progress; elsewhere, the fix for the Executioner door restores movement through a traversal gate, while restored water-return pits near Neasied shorten recovery after a fall. The patch also resolves the Mimic and weapon-evolution freezes, preventing either an encounter or the Weapon Evolution screen from interrupting a Queens Domain speedrun attempt. Finally, correcting the floating Star Lizard bag repairs a conspicuous world-state error that could obscure or prevent interaction.
| Documented issue | Fixed behavior | Route impact |
|---|---|---|
| Pit of Despair soft lock | The progression block no longer prevents continued play | Potentially restores access after the affected encounter |
| Weapon evolution freeze | Weapon evolution no longer freezes the game | Reduces the risk of losing a long item-management session |
| Executioner door stuck | The door can proceed instead of remaining blocked | Keeps the route moving through a documented traversal gate |
| Mimic freeze | The Mimic no longer locks the game | Reduces repeated encounter and save-management risk |
| Missing water return pits near Neasied | Water returns are restored around Neasied | Recovering from a fall can return the player to the route sooner |
| Floating Star Lizard bag | The bag no longer floats in the air | Cleans up an interactable that may have been difficult to reach or read |
These are developer-documented fixes from the official feed, verified as of October 31, 2026. The six-entry table separates route-critical repairs from encounter and recovery fixes, including the Pit of Despair soft lock, Executioner door, Mimic freeze, Weapon Evolution freeze, Neasied water-return pits, and floating Star Lizard bag. The release also contains no documented weapon balance changes, collectible additions, achievement changes, or new speedrun rules, so Queens Domain route planning should treat 1.01.01 as a bug-fix update rather than a rules revision or collectible expansion.
Pit of Despair and the Executioner Door
The two progression-focused fixes concern the Pit of Despair soft lock and the Executioner door getting stuck. These are the clearest reasons to update before continuing a serious playthrough, because either problem can interfere with forward movement even when the player has explored the surrounding area correctly.
The Executioner door is an environmental obstacle, not a character or boss. Likewise, the Pit of Despair is a named place rather than a published encounter title. Players searching for official boss order should not infer either name from the patch notes.
A practical update check takes less than a minute: confirm that 1.01.01 is installed, then use a recent save to test the Pit of Despair soft lock and the Executioner door interaction. The value of this check is that it verifies the two progression fixes in the actual rooms, rather than assuming the patch worked merely because the game updated; exact enemy placements and room layouts are not documented as of 2026-10-31.
-
Confirm that version 1.01.01 is installed.
-
Load a recent save.
-
Approach the Executioner door and verify that it opens normally.
-
Revisit the Pit of Despair route when safe.
-
Continue only after both progression checks pass.
Because exact enemy placements and room layouts are not documented as of 2026-10-31, verify these points in game rather than copying a guide's assumed room order. The broader Queen's Domain exploration route can help organize connected areas, but it cannot replace direct confirmation of patch behavior.
Mimic, Water, and Interactable Fixes
The Mimic freeze, missing water return pits around Neasied, and floating Star Lizard bag have a smaller individual effect on the route, yet together they address common exploration friction. A freeze can interrupt a save or item-management decision, while a missing return point turns a simple fall into additional travel.
The repaired water behavior is especially relevant on the shore of the Isle of Neasied, where players begin after washing ashore. The player can now use the restored return pits around Neasied as intended. The patch does not document their exact locations or activation rules, so test them in the current build rather than relying on a static coordinate list.
For the Star Lizard bag, compare the object both before and after interacting with it. The developer describes the original problem as a bag floating in the air, not as a collectible being added or removed. Players can review the Queen's Domain patch update overview for version context, while confirming the actual object placement in their save.
How the Queens Domain Soft Lock Repair Reshapes Routing
The Pit of Despair soft lock fix has the greatest potential to alter a route, because a blocker may have prevented a player from continuing toward a later objective. It does not prove that the room became shorter, faster, or newly required, so any route comparison should distinguish access restored from time saved.
What Changed Between Builds
| Situation | Possible pre-patch result | Post-patch route decision |
|---|---|---|
| Player reaches the affected state | Progress may stop at the Pit of Despair | Retest the room and continue if movement is restored |
| Save was created before the blocker | The existing save may remain stuck | Test the current build before assuming the save is invalid |
| Run depends on repeated attempts | Failed attempts consume time without creating progress | Avoid treating the old failure loop as normal routing |
| Player uses flight to cross cliffs | Flight may still be the principal traversal method | Keep flight planning even though the soft lock is repaired |
The key distinction is that version 1.01.01 removes a documented failure state; it does not change the underlying exploration structure. Cliffs remain important because the Legendary Holy Sword Endu is the main way to fly between platforms, and upgrades extend flight distance.
Confirming Each Fix in Your Save
Use a clean test rather than risking a valuable save. Reach the nearest available checkpoint, reproduce the path leading to the Pit of Despair, and test whether the player can continue past the previously blocked state. Save again only after movement and menu access both work normally.
Record three results from the same clean checkpoint attempt: whether the route reaches the Pit of Despair without a freeze, whether the player can leave the affected state after the documented transition, and whether reloading and continuing from that checkpoint preserves normal progression. For example, if movement works but opening the menu remains blocked, note that separation instead of marking the patch as fully verified; a successful retry should be logged only after both systems respond normally.
-
Whether the route reaches the Pit of Despair without a freeze.
-
Whether the player can leave the affected state after completing the documented transition.
-
Whether reloading and continuing from the same checkpoint preserves normal progression.
These checks are deliberately procedural because no official room layout, floor count, or exact Pit of Despair objective is published. If the area differs from the patch description, stop and record the behavior rather than publishing a definitive route. The developer’s Steam Community achievement hub confirms achievement totals but does not document a full spatial route.
What This Means for Existing Saves
A bug fix does not automatically guarantee that every pre-patch save can bypass a state created under the old behavior. Test the affected route in the current build. If it remains blocked, try loading a checkpoint created before entering that state, provided the save permits it.
Do not assume that deleting the save is required, and do not assume the patch repaired every save-state edge case. No official support policy or compatibility note for version 1.01.01 documents that distinction. The practical choice is to test the fastest reversible option first, then compare it with a new or earlier checkpoint.
Weapon Evolution Freeze and Queens Domain Long Runs
The weapon evolution freeze fix reduces a major session-ending risk. The game has more than 50 melee weapon types and more than 20 secondary throwing weapons, while weapon evolution is officially confirmed by this patch note. That creates enough inventory decisions for a freeze during evolution to interrupt a long run.
Why the Fix Matters for Long Sessions
| Run type | Pre-patch risk | Safer post-patch habit |
|---|---|---|
| Open-ended exploration | An evolution freeze can interrupt movement and menu use | Perform weapon changes in a safe area |
| Collectible search | Repeated backtracking can stretch the session | Test evolution before beginning a long search chain |
| Achievement run | Repeated deaths and revisits increase exposure to bugs | Keep checkpoints and verify core interactions |
| Speedrun practice | A freeze adds an avoidable non-game delay | Record the interruption only if it occurs in the current build |
Weapon evolution should now complete normally in version 1.01.01. That does not mean every possible weapon combination has been tested publicly, so verify the specific weapon you intend to evolve and confirm that the inventory and equipment screens remain responsive afterward.
Practical Equipment Checks
Perform a short equipment test before committing to a long exploration session, especially when verifying the changes associated with Queen's Domain patch 1.01.01. Begin by checking a basic melee weapon and its weapon-specific special attack, then compare the action with a throwing weapon and a charge attack. This controlled sequence can reveal whether the patch affects weapon activation, stamina consumption, or general combat responsiveness before you invest time in the longer speedrun and achievements route.
-
Evolve the weapon you expect to use.
-
Confirm that the action completes without a freeze.
-
Equip it and attack a low-risk target.
-
Switch to a secondary throwing weapon.
-
Check that the power bar and stamina meter remain responsive.
-
Save in a safe location before continuing.
The stamina meter is the documented core of combat, and every melee weapon has a weapon-specific special attack. The game also supports charge attacks. These facts favor a restrained test: observe whether the freeze is absent without trying to calculate an undocumented damage, regeneration, or stamina-cost advantage.
For broader progression order, the Queen's Domain walkthrough can provide structure, while this patch guide supplies only the verified 1.01.01 changes. In practice, treat the walkthrough as the route plan for the speedrun, achievements route, and collectibles, but use this guide to validate combat behavior after the patch. For example, if a route requires a weapon-specific special attack before a boss encounter, record whether that action completes normally and whether the stamina meter remains responsive; this separates a genuine 1.01.01 change from a difficulty spike or an ordinary failed attempt.
Queens Domain Collectibles and Achievements: What Is Confirmed
Version 1.01.01 does not document any new collectible, achievement, or completion reward. The floating Star Lizard bag repair may affect how that interactable is found or reached, but the patch note does not identify it as a collectible.
Documented and Undocumented Status
| Topic | Confirmed as of 2026-10-31 | Not documented |
|---|---|---|
| Collectibles | A floating Star Lizard bag was repositioned or corrected | Complete collectible list, count, or locations |
| Achievements | Steam lists 53 achievements | Unlock conditions for the achievements |
| Public names | Ten achievement display names are visible | Meaning or trigger for 43 unnamed entries |
| Patch rewards | Six fixes are listed | New collectibles, achievements, or rewards |
| Route order | Two place names (Isle of Neasied, Pit of Despair) and one door object (Executioner door) are documented | Area order, boss order, chapter structure |
The ten public Steam achievement names are Queen's Domain, Ocean Walk, Endless Pages, Unsealed Tomb, Genesis, Halls of Hatred, Dark Silence, Sacred Groves, Deep Mire, and Sin Keeper. A display name alone does not prove that it represents a specific region, boss, or collectible. The full Queen's Domain achievement reference separates documented names from assumptions that can create an unreliable queens domain achievements route.
Building a Queens Domain Achievements Route Without Invented Triggers
A reliable route begins with evidence rather than guesses. Record each achievement popup as it appears, then note the action or exploration event immediately preceding it. This player-generated method is not an official trigger list, but it can reveal which events matter without assigning unsupported meanings to the achievement names.
For the Queens Domain patch 1.01.01 achievements route, make each log entry reproducible by adding the quest state, character or party state, and the precise event that preceded the popup—for example, examining a highlighted interactable, completing a flight traversal, or defeating a documented creature. If the same popup appears in different quest states, record those separately: an achievement tied to one stage of the Queens Domain progression may not trigger during a later speedrun revisit. Preserve unmatched or ambiguous entries too, since their absence from the sequence can help distinguish a confirmed trigger from an event that merely coincided with the unlock.
| Run | Activity before popup | Achievement name observed | Location recorded |
|---|---|---|---|
| First test | Examine an interactable | Record only if unlocked | Approximate, player-created note |
| Second test | Use flight to cross a gap | Record only if unlocked | Approximate, player-created note |
| Third test | Defeat a documented creature | Record only if unlocked | Approximate, player-created note |
For queens domain collectibles, create a separate inventory with three fields: the item seen, where it was observed, and whether the observation occurred before or after the patch. Avoid turning every decorative object into a collectible, because the developer has not published a complete list as of 2026-10-31.
Queens Domain Speedrun Caveats Without an Official Route
A queens domain speedrun cannot be built from an official route because no approved route order, split list, frame rules, or completion-time target is documented as of 2026-10-31. The 1.01.01 update removes six problems, but it does not publish new timing data or declare that any section is faster.
Reliable Run Segmentation
Segment a personal practice run around documented systems rather than invented room names: label each attempt by the same checkpoint sequence—such as the Isle of Neasied shore, flight gaps, the Pit of Despair, and restored Neasied return pits—and record the time, stamina state, and equipment changes needed to complete it. This makes failures comparable: a death in the combat system can be distinguished from a missed flight crossing or a recovery setback after falling into water. Use the patched 1.01.01 behavior as your reference point, since the repaired progression state changes how the Pit of Despair and return pits function. The resulting split times form a repeatable queens domain speedrun baseline, while route timing still needs at least two runs to account for combat decisions and enemy-placement variance.
| Segment | Documented objective | Timing evidence to record |
|---|---|---|
| Opening shore | Begin on the Isle of Neasied shore and establish the Holy Sword Endu | Time until first playable movement |
| Flight movement | Cross gaps between platforms | Flight usage and failed crossings |
| Combat system | Manage stamina, charge attacks, and weapon specials | Combat time, deaths, and recovery time |
| Pit of Despair | Confirm the repaired progression state | Time to enter, resolve, and leave |
| Water recovery | Use restored Neasied return pits | Time lost to falls and recovery |
| Equipment changes | Evolve or swap weapons without a freeze | Menu time and interruptions |
This creates a personal baseline rather than an official leaderboard route. Run the same segment twice before drawing conclusions, because combat decisions, enemy placement, and route familiarity can vary between attempts. For example, if a Pit of Despair run ends with a death, compare it with the next attempt’s entry, resolution, and exit times rather than treating the whole route as one variable; likewise, track whether a failed flight gap or a fall into water caused the larger time loss. Patch 1.01.01’s repaired progression state makes the Pit of Despair and restored Neasied return pits comparable across sessions, so differences in these measured segments are more useful than a single total time.
What Not to Claim
Do not publish an exact completion time, frame advantage, boss sequence, or optimal collectible order without direct in-game evidence and version labeling. Do not treat the developer’s “at least 40+ hours” description of the overall experience as a speedrun target. That statement describes the expected campaign scale, not a verified category of completion time.
The official launch trailer on the developer’s YouTube channel demonstrates flight, stamina-based melee combat, throwing weapons, and the retro-fantasy setting. It does not name bosses, weapons, regions, or a route, so it cannot justify an assumed sequence. For any serious attempt, update to 1.01.01, verify the six fixes in a controlled save, record personal segment times, and label any discovered route as player-created. That approach produces useful practice data without presenting undocumented information as an official speedrun plan.
A Practical Verification Checklist
The most reliable way to use the Queens Domain patch 1.01.01 is to treat it as a stability update with direct route consequences. Test each repair in the current build, document personal findings, and keep assumptions about collectibles or achievements separate from confirmed game behavior.
-
Confirm the installed version reads 1.01.01.
-
Test the Pit of Despair for restored progression.
-
Confirm the Executioner door opens normally.
-
Check that Mimic encounters no longer freeze.
-
Verify the Neasied water return pits after a fall.
-
Inspect the Star Lizard bag’s corrected placement.
-
Evolve a weapon and test combat afterward.
-
Record achievement popups rather than inferring triggers from names.
-
Label player-created routes and collectible notes clearly.
| Priority | Verification task | Why it matters |
|---|---|---|
| 1 | Pit of Despair continuation | Restores a documented progression blocker |
| 2 | Executioner door movement | Prevents a route from stopping at a fixed obstacle |
| 3 | Weapon evolution completion | Protects long inventory and combat sessions |
| 4 | Water return pits | Reduces recovery time after falls |
| 5 | Achievement and collectible log | Prevents unsupported claims about undocumented triggers |
Version 1.01.01 gives the game a cleaner foundation by repairing six specific technical problems. It does not redefine progression, publish a faster route, or reveal missing achievement conditions, so careful in-game verification remains the best way to build a dependable route.
Frequently Asked Questions
Does Queens Domain patch 1.01.01 add new collectibles or achievements?
No new collectibles or achievements are documented in version 1.01.01. The update fixes six existing issues, including a floating Star Lizard bag, but does not identify that bag as a collectible. Verify additions in the current build because the full collectible list and achievement unlock conditions are not documented as of 2026-10-31.
Does version 1.01.01 make the game faster for a speedrun?
The patch removes several interruptions, but no official speedrun route, segment time, or completion-time target is published. It fixes a Pit of Despair soft lock, an Executioner door issue, a Mimic freeze, a weapon evolution freeze, missing water return pits near Neasied, and a floating bag. Create personal segment baselines rather than claiming the patch produced a specific time saving.
Can the ten public achievement names reveal the fastest completion route?
No. Only ten of the 53 Steam achievement display names are public, and none of their unlock conditions are documented. A name does not prove that an achievement corresponds to a region, boss, or collectible. Record actual in-game unlocks and label any resulting route as player-created instead of treating display names as an official queens domain achievements route.
Should old saves be restarted after the Queens Domain patch 1.01.01 update?
Do not restart immediately. Test the affected progression first, especially the Pit of Despair and Executioner door. If an existing save remains blocked, try an earlier checkpoint or a new save and compare the results. The developer has not documented a specific save-compatibility procedure, so preserve your original file until one of these reversible tests succeeds.