Bilewater map: layout, traversal, and what the design teaches about Metroidvania flow
Players who reach the lower reaches of Hallownest eventually need a reliable bilewater map to plan routes through one of the most vertical and hazard-heavy regions in Hollow Knight. The zone sits beneath the City of Tears and above the Deepnest, and it punishes careless traversal with rising acid, fragile platforms, and a mid-boss gauntlet that gates the path to the next major ability. This guide treats the bilewater map the way a level designer would: as a graph of rooms, transitions, and checkpoints whose structure reveals how Team Cherry controls pacing in a dense Metroidvania area. The same lessons are useful for any developer building a vertical, ability-gated region in a 2D exploration game.
What follows is a practical walkthrough of the bilewater map’s room layout, the routes players actually use after collecting key abilities, the hazards that shape those routes, and the design decisions that make the region feel coherent despite its complexity. Each section keeps player goals and developer observations side by side so the article stays useful whether you are trying to reach the next bench or studying how a small studio resolved a tight space-budget problem in a finished title.
Where the bilewater map sits in the Hallownest world graph
The bilewater region occupies a narrow vertical band between the Royal Waterways and Deepnest, with a single short connection back up toward the City of Tears through a passage that opens only after a specific story condition. On the bilewater map, that vertical stacking is the single most important fact. Most of the rooms you need to reach are below the entry point, and the region’s checkpoints are deliberately uneven, so a route plan has to read the bilewater map as a column rather than a flat network.
Three external connections define the bilewater map’s role in the larger world:
- An upper exit that leads toward the City of Tears and the Royal Waterways, usable only after a late-game story trigger.
- A lower exit that drops into Deepnest, providing a one-way escape and a way to integrate bilewater into longer cross-map routes.
- Internal side passages that loop back to the region’s own checkpoints, creating short optional paths for resource runs.
On the larger world graph, the bilewater map acts as a hinge rather than a hub. The City of Tears, the Royal Waterways, and Deepnest each have their own internal logic, but the bilewater map is the place where those three areas physically overlap. That overlap is what makes the bilewater map a useful study object: it is small enough to read in a single sitting, but it touches enough of the world that decisions made in this region ripple outward into how the rest of Hallownest feels.
Players who treat the bilewater map as a side area tend to bounce in and out of it. Players who treat it as a transit corridor between the City of Tears and Deepnest tend to remember it as one of the more elegant regions in the game. The difference is not skill, it is mental model. Once the bilewater map is read as a vertical column with a top hub, a long middle, a lower hub, and one exit per side, the rest of the design starts to make sense.
Reading the bilewater map: rooms, edges, and checkpoints
When you translate the bilewater map into graph terms, the region has a relatively small number of named rooms but a high number of edges between them, because most rooms connect to two or three neighbors. The result is a dense, web-like structure that can confuse a first-time player, especially because vertical edges are visually easy to miss on the in-game map before the area is fully explored.
| Room category | Role on the bilewater map | Typical contents | Design intent |
|---|---|---|---|
| Entry chamber | Single transition from the upper waterways | Lantern, lore NPC, basic enemies | Slows the player and frames the acid theme |
| Vertical shafts | Long downward edges with platforming | Acid pools, fragile platforms, flying enemies | Tests precise control and punishes panic jumping |
| Hub rooms | Three or more edges, often with benches | Save bench, simple NPCs, optional sub-areas | Provide recovery and route planning |
| Optional sub-zones | Side passages with rewards | Geo, soul vessels, charms, lore tablets | Reward thorough exploration without blocking progress |
| Mid-boss arena | Required gate before the lower exit | Two-phase encounter with acid hazards | Raises stakes and force-saves the player before Deepnest |
| Lower exit | Transition to Deepnest | Brief corridor, visual cue change | Signals a thematic shift in music and palette |
The interesting design choice is that the bilewater map’s hub rooms are not placed at the geometric center of the region. They sit closer to the top and the bottom, leaving the middle of the bilewater map as a long, uninterrupted gauntlet. This split gives the region a clear rhythm: descend through the long middle, recover at the lower hub, then choose between an optional loop and the descent into Deepnest. A level designer reading the bilewater map can see immediately that the team wanted a sustained tension spike without checkpoints in the middle, and a soft release only after the player proves they can survive it.
Edges on the bilewater map also carry implicit information. A vertical edge is harder than a horizontal one, a hub edge is safer than a mid-shaft edge, and an edge that loops back to the same room is a hint that the room has a hidden reward. Players learn these patterns quickly, and the bilewater map rewards that learning with faster subsequent runs. Designers building similar regions can borrow the same idea: every edge on a map should communicate something about the challenge ahead, even before the player enters the next room.
Traversal routes through the bilewater map
Most players approach the bilewater map with one of three goals: reach the mid-boss to unlock the lower exit, farm a specific resource, or do a clean backtrack to the City of Tears. Each goal produces a different route, and the bilewater map’s edge density means all three routes overlap heavily, which is why even experienced players keep the area map open.
First descent: from entry to the lower hub
The standard first descent follows the right-hand side of the bilewater map. You drop through a sequence of vertical shafts, dodge acid plumes that rise from the floor, and use the Mantis Claw to cling to walls when platforms give way. The route is linear in the sense that almost every room in the chain has only one viable forward edge, but the bilewater map still offers small detours for geo or soul.
The mid-boss sits at the end of this chain. The arena is deliberately wider than the surrounding corridors, which forces the player to learn new movement patterns against a multi-stage opponent. Once the encounter is cleared, the bilewater map updates: a new lower hub becomes available, and the Deepnest transition opens. The checkpoint placement is no accident. By saving the bench right before the mid-boss, the team ensures that the bilewater map always offers a quick rematch for any player who wants to refine the fight or use it as a charm-testing ground.
On a first run, most deaths in the bilewater map’s first descent come from a small set of repeating situations: a platform that breaks one jump earlier than expected, an acid plume that triggers on contact rather than on a timer, and a flying enemy that knocks the player into a pool. The bilewater map is honest about these hazards once they have been learned, but it does not telegraph them on the first pass. That is part of the contract the bilewater map offers to new players: survive the descent, and the rest of the region becomes a series of solved puzzles rather than open questions.
Optional loops: resource routes through side passages
Side passages on the bilewater map reward players who read the geometry carefully. These loops often contain soul totems, a Mask Shard, or a Notch that meaningfully expands build options. Because the bilewater map’s side passages tend to reconnect with the main shaft, they rarely add time to a run, but they do add risk. Acid rises faster in the narrower rooms, and enemies are placed to punish the player who tries to farm while looking at the map.
For developers, this is a useful case study in optional content pacing. Optional content should not feel like a separate region tacked onto the bilewater map. It should be woven into the same edges, with the same hazards, so that the cost of exploring is the same as the cost of progressing. The bilewater map respects that rule consistently, which is why its optional content is remembered as part of the region rather than as a checklist of side rooms.
A useful practical pattern is to read each side loop as a question. The bilewater map asks the player: is the reward worth the time the acid will cost you? A Mask Shard usually is. A single soul totem often is not, unless the player is building around a spell that needs the extra soul. The bilewater map does not explain this, but it makes the math visible through the geometry, which is a more elegant solution than a UI prompt would have been.
Backtrack route: from Deepnest back to the City of Tears
After the lower exit opens, the bilewater map supports a backtrack route that climbs from Deepnest back into the upper area in roughly the opposite order of the first descent. The climb uses the Monarch Wings and Isma’s Tear in combination, and the bilewater map reveals why both abilities are placed in different parts of the world: the climb is only possible when the player has them both, which means the backtrack is a late-game privilege rather than an early shortcut.
That delay is what makes the backtrack feel like a reward. A player who reaches the City of Tears through the bilewater map in late game has already earned the climb, and the bilewater map uses that earned traversal to compress a long section of the world into a single, satisfying run. For developers, this is a useful contrast with the early-game experience of the same region, and it shows how the bilewater map can be read as two separate maps that share a single set of rooms.
Hazards, checkpoints, and how the bilewater map controls risk
The bilewater map’s defining hazard is rising acid. Acid appears in pools, in plumes triggered by player movement, and as a slow fill that turns safe rooms into timed rooms. The bilewater map handles this in three distinct ways, and each one corresponds to a different design goal.
| Hazard type | Where it appears on the bilewater map | Player counterplay | Pacing effect |
|---|---|---|---|
| Static acid pools | Lower vertical shafts and side passages | Wall cling, Mantis Claw, precise jumps | Slows exploration, forces route reading |
| Triggered acid plumes | Hub-adjacent rooms and the mid-boss arena | Wait for the plume, dash through the gap | Creates rhythm breaks between safe rooms |
| Rising acid floods | Optional sub-zones and certain corridors | Quick platforming chain, soul-based healing | Adds a soft timer to optional content |
| Fragile platforms | Most vertical shafts | Memorize break points, avoid dwelling | Encourages forward momentum |
| Flying enemies | Open chambers near hubs | Down-strike, ranged spells | Tests combat resource use in safe rooms |
What stands out is that the bilewater map rarely stacks more than two of these hazards in the same room. Static acid plus a flying enemy is common; static acid, triggered plumes, fragile platforms, and a flying enemy together would be overdesigned. By limiting combination density, the bilewater map keeps each room readable while still feeling threatening, and that readability is what allows the region to scale gracefully for both new and experienced players.
That structure is typical of late Metroidvania design. A single dense region becomes a hinge between two larger areas, and the bilewater map rewards players who have already invested in traversal abilities such as the Mantis Claw, Isma’s Tear, and Monarch Wings. Without those, the bilewater map is effectively a maze with dead ends; with them, it becomes a fast lane between two hubs. The contrast is intentional, and it is one of the clearest examples in the broader Hollow Knight game design discussion of how ability gating is used to make a single map feel like several different regions to different players.
Checkpoint placement follows the same rule. Benches are placed at the top of a hazard cluster, not in the middle, so the bilewater map guarantees that the most punishing sequences can be reset only by re-entering them. That is a stricter design than many action games use, and it is one of the reasons the bilewater map’s mid-boss fight feels earned rather than cheap.
For developers, the bilewater map is also a reminder that risk control is rarely about adding checkpoints. A region can be made fairer by raising the player’s ability to predict the next hazard, and the bilewater map does most of that work through repetition and visual consistency. Acid looks like acid in every room, fragile platforms behave the same way in every shaft, and that consistency is what allows the bilewater map to keep its checkpoint count low without feeling unfair to the player.
Ability gating and how it reshapes the bilewater map
The bilewater map changes meaning as the player collects abilities. The same edges that are dead ends on a first visit become fast lanes on a second visit, and the bilewater map’s role in the world graph changes from a frontier into a transit corridor. That dynamic is the core Metroidvania loop, but the bilewater map demonstrates it especially cleanly because almost every traversal edge uses at least one ability that is unlocked in another region.
- Without the Mantis Claw, the bilewater map’s vertical shafts are impassable, so the region reads as a single horizontal corridor with no depth.
- Without Monarch Wings, several of the optional loops are unreachable, so the bilewater map’s optional content is hidden until the player invests in aerial movement.
- Without Isma’s Tear, the bilewater map’s acid pools are walls, so the mid-boss and the Deepnest exit are locked behind a late-game ability.
- With all three abilities, the bilewater map becomes a fast lane, and players can move between the City of Tears and Deepnest in roughly a minute.
For developers, the bilewater map is a reminder that ability gating is not only about locking content. It is also about giving the same map several distinct personalities. A bilewater map without Isma’s Tear is a puzzle; a bilewater map with Isma’s Tear is a highway. Both versions use the same rooms, but the player’s mental model of the region is completely different.
The bilewater map also shows how ability gating interacts with checkpoint density. Without the right abilities, the player gets stuck in long rooms with no save point, and the bilewater map feels punishing. With the right abilities, the same rooms can be cleared in seconds, and the bilewater map starts to feel generous. That swing is not a bug. It is the same region being read by two different players at two different points in the playthrough, and the bilewater map is designed to be fair to both of them.
A useful way to study this is to draw the bilewater map as two separate graphs: one for the early-game state and one for the late-game state. The room layout is identical, but the number of usable edges, the value of each loop, and the risk of each transition all change. Developers building similar regions can use the same trick: design the room graph first, then think about which abilities remove which edges, and let the bilewater map’s pacing emerge from that interaction rather than from explicit tuning.
Map discovery, UI, and the player’s mental model of bilewater
The in-game map for the bilewater region follows the same system as the rest of Hollow Knight. The player must purchase the map from a named NPC, after which the bilewater map reveals explored rooms in real time and shows the rough shape of corridors as the player walks through them. Corners only fill in after the player has touched them, so the bilewater map rewards deliberate movement rather than brute-force exploration.
Three details are worth noting for developers building similar map systems:
- Map completion requires revisiting rooms, not just passing through them. The bilewater map therefore trains a specific behavior: backtrack to fill the map, then plan routes against the completed picture.
- The bilewater map uses color cues for room type and elevation cues for vertical edges, which keeps the map readable even when corridors cross over each other.
- The bilewater map does not show live hazards. Acid plumes and fragile platforms are not represented on the map, so the player has to remember them from previous runs, which is a deliberate choice that turns the bilewater map into a memory aid rather than a survival tool.
That last point is significant. A map that shows live hazards would reduce the bilewater map to a checklist, and the region would lose the tension that comes from not knowing whether a specific room is still safe. The bilewater map’s restraint in this area is one of the more interesting UI decisions in the broader puzzle and traversal design discussion that the team has inspired.
Another subtlety is how the bilewater map handles edges that cross over each other. In a flat 2D layout, two vertical shafts that share a screen would look like a single X on the map. The bilewater map avoids that confusion by tinting overlapping edges and by giving each room a stable identifier, so the player can always tell which corridor belongs to which room. That small touch does a lot of work, and it is one of the reasons the bilewater map stays readable even in the densest part of the region.
What the bilewater map teaches about vertical Metroidvania design
For developers, the bilewater map is a compact case study in how to design a vertical region without making the map illegible. Several lessons stand out:
- Stack the region along a single axis, but offset the checkpoints so the player has a sense of progress even when every screen looks similar.
- Use hub rooms to break long gauntlets, but place them at the top and bottom of the gauntlet rather than in the middle, so the tension spike is real and the recovery feels earned.
- Limit hazard combinations to two at a time, so each room reads at a glance and difficulty comes from sequencing, not from clutter.
- Tie optional content to the same edges as required content, so exploration and progress share a cost and a reward structure.
- Reuse the same map across multiple ability states, so the same rooms can serve as a puzzle, a challenge, and a highway at different points in the playthrough.
These patterns show up in many successful Metroidvania titles, and the bilewater map is one of the clearest examples of how they can be applied in a finished product. The team behind the title has discussed similar ideas in the broader study of Unity-based game development workflows, where level designers often borrow the same checkpoint and ability-gating structures for their own projects.
It is also worth noting what the bilewater map does not do. It does not introduce a new movement verb just for this region, it does not overload the player with a new enemy type in every room, and it does not require a long cutscene to explain the acid mechanic. Each of those choices would have made the bilewater map more impressive on paper, but each one would also have made the region feel detached from the rest of the game. The bilewater map is a stronger design for what it leaves out, and that restraint is itself a lesson.
Common player mistakes when reading the bilewater map
Even with the map purchased, several reading errors show up repeatedly. Most of them are caused by treating the bilewater map as a flat network when it is actually a layered column.
- Ignoring vertical edges because the bilewater map renders them with the same line weight as horizontal edges, which leads to missed shortcuts.
- Assuming side passages are dead ends, when in fact they loop back to the main shaft and are required to fully map the region.
- Forgetting that the lower exit to Deepnest only opens after the mid-boss, so the bilewater map looks incomplete until the fight is resolved.
- Trying to farm optional content without tracking the rising acid timer, which makes those loops more dangerous than they look on the bilewater map.
- Backtracking before unlocking the upper exit, which leaves the bilewater map with no quick route back to the City of Tears until a late-game condition is met.
Each mistake is a small lesson in how a dense map punishes a flat reading. Players who learn to think of the bilewater map as a column rather than a network tend to clear the region in a single sitting, while players who treat it as a flat maze often spend two or three sessions on the same content.
A related mistake is over-reliance on the in-game compass. The bilewater map is dense enough that a compass marker can point the player toward a room that is technically on the bilewater map but only reachable through a path the marker does not show. Once players stop trusting the compass and start trusting the room graph, the bilewater map becomes much easier to read, and the time spent in the region drops sharply.
Performance, optimization, and the bilewater map as a render-budget example
The bilewater map also offers a useful case study in 2D rendering. Acid shaders, dynamic lighting, and a high enemy count are present in almost every room, and the bilewater map therefore pushes the engine’s particle and lighting budgets harder than most regions in the game. For developers, the way the bilewater map handles that load is instructive.
| Render feature | Where it appears on the bilewater map | Budget pressure | Mitigation pattern used |
|---|---|---|---|
| Acid shaders | Vertical shafts and side passages | Per-pixel cost rises with screen coverage | Reduced resolution of the acid texture at distance |
| Dynamic lighting | Hub rooms and the mid-boss arena | Multiple light sources overlap in small rooms | Pre-baked ambient for static geometry, dynamic only for the player |
| Particle systems | Acid plumes and fragile platform debris | Many short-lived particles per frame | Pooled particle systems with capped counts per room |
| Enemy AI | Hub-adjacent chambers and mid-boss arena | Pathfinding cost grows with room density | Simple scripted behavior for non-boss enemies |
| Audio layers | Throughout the region | Multiple ambient layers in overlapping rooms | Crossfade zones keyed to the bilewater map’s hub rooms |
For a developer working on a 2D action game in Unity or a comparable engine, the bilewater map shows that optimization is not only about cutting effects. It is about choosing where to spend the budget so the most important rooms feel rich while the corridors stay light. The bilewater map spends its budget on the mid-boss arena and the two hubs, which are exactly the rooms players remember, and keeps the long middle gauntlet lean enough to run at a stable frame rate even on modest hardware.
Audio budgeting is the part that is most often missed. The bilewater map layers several ambient tracks over the same vertical shaft, which can easily double the audio cost compared with a single-layer region. The team handles this by treating the hub rooms as audio crossfade points, so only one ambient track is active in any given room. That decision also helps the player: the bilewater map’s audio shifts are tied to the same rooms where the visual style shifts, which reinforces the region’s rhythm without the player having to think about it.
Narrative placement and why the bilewater map feels lonely
The bilewater map is also one of the quieter regions in the game in narrative terms. There is very little friendly dialogue, and the few NPCs that do appear tend to be in the upper entry chamber rather than in the deeper rooms. The bilewater map uses that silence deliberately. The rising acid, the muted color palette, and the absence of dialogue work together to set up the tonal shift that hits the moment the player crosses into Deepnest.
For developers, the bilewater map is a useful example of how environmental storytelling can replace scripted narrative. The bilewater map does not tell the player that the area is dangerous; it shows it, and it asks the player to internalize the danger through repeated failed jumps and rising acid. By the time the mid-boss is reached, the bilewater map has already done most of the narrative work, and the boss fight can focus on mechanical challenge rather than on explaining the stakes.
That silence is also a contrast tool. The bilewater map is quiet precisely because Deepnest is loud, and the upper waterways are full of dripping sound. The bilewater map sits in the middle of that range, and the player’s ears recalibrate as they move through the region. For developers, this is a reminder that a region’s narrative weight is often carried by what is absent, and the bilewater map is a clear example of that principle working as intended.
Putting the bilewater map into a wider design vocabulary
Read against other regions in the same game, the bilewater map is a useful counterweight to the more open hubs. The City of Tears gives the player vertical space and slow fall damage, Greenpath gives the player a forgiving early-game difficulty curve, and the bilewater map gives the player density without forgiveness. That placement is not accidental. The bilewater map is a deliberate compression point in the campaign, and the design lessons it offers transfer to any project that needs a region which feels both short and demanding.
Studios building similar games can borrow several of the bilewater map’s habits directly: a single dominant hazard, two hubs with a long middle, a mid-boss that gates the next region, and a tight render budget on the corridors between hubs. None of those choices are unique to the bilewater map, but the way the bilewater map combines them is unusually clean, and that combination is what makes the region worth a close reading.
For players, the practical takeaway is simple. Read the bilewater map as a column, not as a network, learn the acid patterns, and treat the long middle as a single challenge rather than a sequence of small ones. The bilewater map will reward that reading with a faster, less frustrating run, and the rest of the late game will feel a little easier as a result.
Frequently asked questions
Where does the bilewater map fit in the overall Hollow Knight world?
The bilewater map sits between the Royal Waterways above and Deepnest below, with a single late-game connection back to the City of Tears. It is one of the lowest regions accessible before the final act of the game, and it functions as a hinge between two larger areas rather than as a destination on its own.
Do I need any abilities before I can use the bilewater map?
Yes. The Mantis Claw, Monarch Wings, and Isma’s Tear are all required to traverse the bilewater map fully. Without Isma’s Tear, the mid-boss and the Deepnest exit are unreachable, so the bilewater map effectively becomes a dead end until that ability is collected.
Where is the first bench on the bilewater map?
The first bench is in the upper entry chamber, shortly after the transition from the Royal Waterways. The bilewater map places this bench before the long middle gauntlet so that players can save before committing to the descent toward the mid-boss arena.
How does the bilewater map change after the mid-boss is defeated?
Once the mid-boss is cleared, the lower hub opens, the Deepnest exit becomes accessible, and the bilewater map gains a useful fast lane for backtracking. The same rooms now serve as a transit corridor rather than as a frontier, and the bilewater map’s role in the world graph shifts accordingly.
Why does the bilewater map feel harder than nearby regions?
The bilewater map combines rising acid, fragile platforms, and dense enemy placement in long, checkpoint-light sequences. The combination of those hazards and the limited bench density is what makes the region feel harder than the City of Tears or the upper waterways.
Can the bilewater map be fully mapped on a first visit?
Not usually. Several optional loops require abilities that the player does not have on a first visit, and the upper exit to the City of Tears only opens after a late-game story condition. A complete bilewater map typically requires two or three visits with different ability sets.
Does the bilewater map show live hazards on the in-game UI?
No. The bilewater map shows static room shapes and edges, but it does not display live acid plumes, rising water levels, or fragile platform state. Players have to track those hazards from memory, which is part of the region’s design intent.
What is the best route for farming geo in the bilewater map?
Most players farm the side passages connected to the lower hub, because those loops respawn quickly and reward careful traversal. The bilewater map’s side passages share the same hazards as the main shaft, so farming is only safe with a heal-heavy build.
Is the bilewater map useful for a developer studying level design?
Yes. The bilewater map is a compact example of vertical Metroidvania design, ability gating, hazard sequencing, and render-budget allocation, which is why it is often cited in case studies of 2D action game design.
How long does it take to clear the bilewater map on a first playthrough?
On a first playthrough with no prior knowledge, clearing the bilewater map typically takes between 30 minutes and an hour, depending on how much optional content is collected and how many deaths occur in the mid-boss arena. Experienced players can move through the bilewater map in roughly five to ten minutes once the route is known.
Leave a Reply