The Hunter’s Journal in Silksong isn’t just a checklist; it’s a systemic test of how deeply you understand Pharloom’s ecology, combat language, and hidden rules. Veterans expecting a straight port of Hollow Knight’s journal will get burned fast. Silksong expands the system with layered completion thresholds, conditional entries, and enemies that only register under very specific circumstances.
Every bug you encounter is quietly tracked the moment Hornet aggroes it, but registration alone doesn’t equal completion. Like Hallownest before it, most entries demand a minimum number of confirmed kills, yet Silksong is far more aggressive about variants, phase-based enemies, and scripted encounters that only count if defeated in the correct state. Miss one condition, and the Journal entry stays permanently incomplete until New Game Plus.
How Journal Entries Are Actually Unlocked
An enemy only appears in the Journal after first contact, not first kill, but the real gate is the defeat counter tied to that bug’s internal classification. Standard fodder bugs usually cap out quickly, while elite units, caste guardians, and mini-boss-tier enemies often require multiple kills across different zones. This is where RNG patrol spawns and late-game backtracking become mandatory for full completion.
Silksong also introduces conditional unlocks tied to encounter context. Some bugs only register if defeated while enraged, shielded, or during an environmental hazard like silk storms or bell-triggered aggro states. Killing them too cleanly can actually lock you out of the full entry until you find another spawn.
Hidden Thresholds and Soft-Completion Traps
The Journal’s percentage completion is deceptive. Hitting the visible completion number does not mean every bug entry is fully logged. Certain rare enemies and one-off encounters contribute to hidden thresholds that only trigger once their lore notes or special illustrations are unlocked.
This is where completionists get punished. Scripted enemies tied to quests, escape sequences, or collapsing arenas may not respawn, and failing to defeat them before the scene ends can permanently gray out parts of the Journal. Silksong is less forgiving than Hollow Knight here, especially with NPC-adjacent enemies that blur the line between character and combatant.
Variants, Castes, and Why One Kill Isn’t Enough
Pharloom’s caste system matters mechanically. Many bugs share a base model but count as entirely separate Journal entries based on weapon type, armor state, or silk augmentation. A spear-bearing guard and its bell-infused counterpart are not the same entry, even if they share animations and hitboxes.
Some variants only appear after world-state changes, such as region corruption, late-game bell activations, or quest resolutions. If you rush progression without farming earlier zones, you can accidentally skip low-tier variants that never reappear, forcing another full playthrough for true completion.
Rewards for Full Journal Completion
Completing the Hunter’s Journal isn’t cosmetic fluff. Full completion unlocks unique lore tablets that recontextualize Pharloom’s power structures, along with mechanical rewards that directly impact combat efficiency. Expect permanent stat modifiers, silk interaction bonuses, and at least one high-impact upgrade that changes how Hornet interacts with elite enemies.
There’s also narrative payoff. The final Journal thresholds reveal information about the nature of the Hunt itself and Hornet’s role within it, delivered in the same cryptic, environmental storytelling style veterans expect. Skipping the Journal means missing some of Silksong’s most important world-building.
What the Game Never Tells You
The Journal does not warn you about missable entries, variant dependencies, or conditional defeats. There is no in-game checklist, no NPC hinting that you should let an enemy enrage before killing it, or that a bell must be rung mid-fight for the kill to count properly.
For hardcore completionists, the Hunter’s Journal is the real final boss of Silksong. Understanding its rules early is the only way to avoid late-game frustration, wasted hours, and the sinking realization that a single overlooked bug is standing between you and true 100 percent completion.
How Pharloom’s Ecology Works: Enemy Families, Regions, and Variant Bugs
Everything about Pharloom’s enemy design reinforces a single idea: bugs don’t exist in isolation. Unlike Hallownest, where many foes were functionally standalone, Silksong organizes enemies into interconnected families that evolve based on region, world state, and Hornet’s interference. If you’re hunting Journal entries efficiently, understanding these ecological links is just as important as raw combat skill.
Enemy families determine spawn logic, variants, and even aggro behavior. Kill one caste too aggressively and you may never see its support unit. Leave another alive during certain events and it can transform into an entirely different Journal entry later. Pharloom rewards observation first, aggression second.
Enemy Families and Shared Lineages
Most bugs in Pharloom belong to a broader lineage, not a single enemy type. Weaverkin, Bell-Servitors, Mossbound laborers, and Ascetic cultists all feature multiple entries that stem from a shared base organism. These families often share silhouettes, attack timings, and hitbox logic, but the Journal treats each functional role as a distinct entry.
This is where completionists get trapped. A shield-bearing Weaver Sentinel and its silk-channeling variant might look identical in motion, but the moment silk is introduced into its moveset, it becomes a new classification. If you kill the base unit after triggering the silk state without letting the variant fully manifest, you won’t get credit for either entry.
Regional Adaptation and Environmental Pressure
Pharloom’s regions actively shape the bugs that live there. Enemies in the Gilded City favor armor, shields, and formation-based aggro, while the Mossed Lowlands introduce status effects, regeneration, and terrain-assisted ambushes. The Journal tracks these as separate organisms, even when the differences feel subtle in combat.
Environmental hazards matter, too. Some bugs only appear near bell structures, silk conduits, or corrupted growths. If you clear a room too cleanly, you may never trigger the conditions needed for a rarer spawn to emerge. Smart farming means manipulating the environment, not just resetting checkpoints.
World State, Progression, and Locked Variants
Silksong quietly ties enemy variants to global progression flags. Ringing certain bells, completing faction quests, or destabilizing a region can permanently replace low-tier enemies with upgraded versions. Once that shift happens, earlier variants often disappear entirely.
This is the single biggest reason Journal completion fails on first playthroughs. A late-game Pharloom looks radically different from its early state, and the Journal does not retroactively fill gaps. If a bug only exists before a bell’s activation, that entry is gone unless you start over.
Caste Roles: Workers, Guards, and Ascended Forms
Within each family, bugs are divided by role rather than strength. Workers, scouts, guards, and ascended elites are all tracked separately, even if their DPS difference is minimal. The Journal cares about behavior, not threat level.
Some enemies only qualify for their proper entry if defeated while performing their role. Guards must be actively defending, not staggered. Ascended forms often require you to survive an enrage phase or let them complete a transformation animation before landing the killing blow. Rushing damage can invalidate the entry entirely.
Artificial Variants and Silk Corruption
Silk changes everything. Bugs augmented by silk are not reskins; they’re mechanically distinct entities with altered I-frames, recovery windows, and sometimes entirely new attacks. The Journal treats silk-infused enemies as separate lifeforms, even when their origin is obvious.
These variants are easy to miss because they often spawn mid-fight. If you burst an enemy before it fully integrates silk, the game logs the base form only. Completionists should intentionally slow fights, bait transformations, and prioritize survival over DPS when farming entries tied to silk corruption.
Why Ecology Dictates Your Journal Route
Pharloom’s ecology is the hidden framework behind every Journal pitfall. Enemy families evolve, regions overwrite themselves, and variants depend on timing rather than location. Treating bugs as isolated targets guarantees missed entries.
For true 100 percent completion, you’re not just fighting enemies. You’re studying an ecosystem, learning when to intervene, and knowing when not to. That mindset is the difference between a filled Journal and a single, maddening blank entry staring back at you from the menu.
Common Bugs of Pharloom: Standard Enemies and Their Journal Requirements
With ecology in mind, it’s time to talk about the backbone of the Hunter’s Journal: Pharloom’s common bugs. These are the enemies you’ll fight constantly, but that familiarity is exactly what makes their entries dangerous. Standard does not mean simple, and many of these bugs hide missable conditions behind routine encounters.
Weaverkin Drones and Silk Runners
Weaverkin Drones are Pharloom’s baseline worker caste, found in early regions like the Lower Loomways and Scaffold Warrens. Their Journal entry only registers if defeated while actively carrying silk bundles or reinforcing terrain. Killing them during idle patrols logs nothing.
Silk Runners are counted separately despite sharing models and arenas. You must defeat them mid-dash, not during recovery, or the game flags the kill as a Drone instead. The safest method is to bait a horizontal sprint, pogo to force hit confirmation, then finish before they disengage.
Lore-wise, these entries establish how deeply silk is embedded into daily labor, not just combat. The Journal text subtly changes depending on which entry you unlock first.
Bellbound Sentinels
Bellbound Sentinels act as Pharloom’s equivalent to guards, typically stationed near bell mechanisms and vertical chokepoints. Their Journal requirement is strict: the Sentinel must be alerted by bell resonance before death. Ambushing them from off-screen skips the entry entirely.
Once aggroed, Sentinels gain extended I-frames during shield raises, which tempts players to overcommit DPS. Don’t. Let the bell pulse complete, then punish during the downward spear sweep for consistent registration.
These enemies reinforce the idea that Pharloom’s defenses are reactive systems, not static obstacles. The Journal reflects this by treating unalerted Sentinels as incomplete data.
Threadleeches and Burrow Swarms
Threadleeches are minor enemies, but their Journal entries are some of the most commonly missed. Single Threadleeches do not count. You must defeat a Burrow Swarm variant after it emerges from the ground as a group.
The trick is patience. If you kill the initial scout leech too quickly, the swarm never spawns, and the Journal remains blank. Backstep, let the ground ripple, then use wide-hitbox attacks to clear multiple bodies in one cycle.
Their lore entry hints at how silk infestation spreads underground, foreshadowing later corrupted zones without directly spoiling them.
Carapace Walkers
Carapace Walkers are slow, armored bugs found across mid-game regions, often used to teach spacing and stamina control. Their Journal entry only completes if you break their armor naturally. Using armor-piercing tools or silk abilities skips the requirement.
You need to force them into a defensive curl, bait the overcommit slam, and crack the shell during the exposed recovery window. It’s slower, but it’s the only way the Journal recognizes proper observation.
This entry reinforces the Hunter’s role as a researcher, not an executioner. How you fight matters as much as the outcome.
Chorus Flies
Chorus Flies are ambient enemies that appear harmless, floating near sound-based environmental hazards. They only become hostile when multiple are active, and the Journal entry requires defeating them during a synchronized sonic attack.
Most players kill these accidentally with stray hits and never trigger the correct state. To farm the entry, stand near bell clusters and wait for three or more Flies to harmonize before engaging. Vertical attacks help avoid desyncing their pattern.
Their lore text provides crucial insight into how sound replaces infection as Pharloom’s controlling force, tying directly into bell mechanics without explicit exposition.
Missable Early-Phase Variants
Several common bugs have early-phase variants that disappear once regional bells are activated. These include Pale Weaverkin, Dormant Sentinels, and Unbound Threadleeches. Each has a separate Journal entry, even though their combat profiles are simpler.
The requirement is blunt: defeat them before progression overwrites the zone. There is no workaround, no late-game spawn, and no retroactive unlock. If you’re chasing full completion, these should be prioritized over bosses.
These entries exist to test whether players are paying attention to Pharloom as a living space. Miss them, and the Journal never lets you forget it.
Elite & Specialized Bugs: Armored, Elemental, and Role-Based Variants
Once you move beyond baseline enemies, Silksong starts layering intention into its bug design. These elite and specialized variants are not just tougher stat blocks, but mechanical exams that test whether you understand how Pharloom’s systems overlap. Most Journal failures here come from killing them too efficiently, or in the wrong role state.
These enemies also mark the point where the Hunter’s Journal stops being passive. Observation requires restraint, controlled aggression, and sometimes deliberately letting a fight drag on longer than feels safe.
Plated Wardens
Plated Wardens are elite sentry units stationed near bell-gated paths and high-value traversal routes. Their frontal plating completely nullifies frontal DPS, and backstab damage only registers after they commit to a charge or shield bash.
For Journal completion, you must break the armor plating before landing the killing blow. Silk-based grapples that flip them or bypass their guard invalidate the entry, even if the enemy dies normally. Bait the charge, dash through the hitbox during the recovery frames, and punish the exposed core.
Lore-wise, their entry frames them as ceremonial defenders rather than soldiers, reinforcing the idea that bells protect tradition, not territory.
Elemental-Bound Variants
Elemental bugs come in fire, frost, shock, and resonance-aligned forms, often sharing base models with standard enemies. The Journal treats each element as a distinct species, not a modifier, and killing the wrong variant does nothing for completion.
Each requires defeat using non-matching damage. For example, Frostbound Skirmishers must be killed without fire-based silk, or their bodies shatter and deny proper observation. Likewise, Shockcallers must be grounded before death, or they discharge and despawn their entry.
Their lore entries are critical, quietly confirming that Pharloom’s ecology adapted to bell resonance rather than infection. These bugs aren’t corrupted; they’re specialized.
Role-Based Combat Bugs
Several enemies dynamically change roles mid-fight, and the Journal only completes if you defeat them in their intended role state. Bannerbearer Drones, for instance, must be killed while actively buffing nearby enemies, not while isolated or stunned.
Thread Medics are even more specific. You must interrupt at least one healing cast, then allow them to resume support before landing the final blow. Killing them too quickly flags the encounter as incomplete.
These entries exist to punish speedrunning habits. Silksong wants you to read the fight, not erase it.
Elite Duo and Pack Leaders
Some bugs only appear as leaders within mixed enemy packs, identifiable by size, coloration, or bell-marked armor. Killing the leader first prevents the Journal entry from registering, as the game never observes the full command behavior.
To complete these, thin the herd but leave the leader active long enough to trigger at least one rally or command animation. Once that behavior is logged, the kill becomes valid.
Their lore text reinforces Pharloom’s hierarchical survival structure. Unlike Hallownest, order here is maintained through coordination, not mindless spread.
Reinforced Shell Variants
Reinforced Shell bugs are late-game evolutions of earlier armored enemies, often mistaken as repeats. They are not. Each has a separate Journal page, and their defeat condition requires fully stripping every armor layer before the core becomes vulnerable.
Multi-hit silk slashes can accidentally bypass layers if chained too tightly, invalidating progress. Slow, deliberate strikes are safer, even if the fight drags on. If you hear the shell crack but see no stagger, you’re doing it wrong.
These entries serve as a final exam for everything armored enemies taught earlier. By now, the Journal expects mastery, not improvisation.
Bosses & Major Encounters: Mandatory, Optional, and Multi-Phase Journal Entries
Where standard enemies test execution, bosses test comprehension. In Silksong, boss Journal entries are not automatic rewards for victory. They are behavioral records, and several encounters can be permanently botched if you skip phases, over-optimize DPS, or end fights too early.
Pharloom’s major bugs are defined by escalation. The Journal only completes when the game has observed the full arc of the encounter, including desperation states, environmental shifts, and bell-triggered transitions.
Mandatory Bosses: Journal Completion Is Not Guaranteed
Mandatory story bosses do not auto-complete their Journal entries. Defeating them is required for progression, but the Journal only updates if every scripted phase occurs naturally. This includes arena changes, summon cycles, and resonance surges tied to bell mechanics.
Several early-mid game bosses have low HP thresholds that can be skipped with aggressive silk builds. If a boss never enters its resonance phase or fails to deploy its signature mechanic, the Journal flags the encounter as incomplete, even though the boss is dead.
A common example is bell-bound sentinels that summon auxiliary enemies or alter terrain mid-fight. You must allow at least one full summon cycle to resolve on-screen before landing the killing blow. Speed kills actively punish Journal hunters here.
Optional Bosses: Missable and Often One-Shot
Optional bosses are where most Journal failures occur. Many are tied to side routes, collapsing arenas, or single-use challenges that do not respawn once cleared. If you defeat them incorrectly, there is no second attempt.
Some optional bosses only register if you trigger their enraged state, usually tied to time elapsed or HP thresholds. Killing them too cleanly results in a partial entry that never upgrades to a full page.
Exploration-focused players should delay these encounters until their build can comfortably survive longer fights. The Journal rewards patience, not dominance, and optional bosses are tuned to exploit overconfidence.
Multi-Phase Bosses: Phase Skipping Breaks the Entry
Multi-phase bosses are the Journal’s most demanding checks. Each phase is treated as a distinct behavioral log, even if the fight occurs in a single arena without cutscenes. Skipping a phase invalidates the entire entry.
Phase transitions are often triggered by positioning, bell resonance, or environmental damage rather than raw HP. If you pin a boss against terrain or stunlock them through a threshold, the transition may never fire.
Watch for audio cues and arena tells. A change in music layer, bell pitch, or background motion usually signals a required phase. If you don’t see it, stop attacking and let the fight breathe.
Bosses with Summoned or Shared Entities
Several bosses rely on summons, puppets, or linked entities to define their identity. The Journal requires that at least one summon completes its full lifecycle, including spawn, behavior, and termination.
Destroying summons instantly with area silk attacks can invalidate the record. You must allow them to act, attack, or interact with the arena before clearing them.
Lore-wise, these fights emphasize Pharloom’s reliance on delegation and control. Bosses here are commanders, not solo tyrants, and the Journal reflects that philosophy.
Rematches, Refights, and Bell-Triggered Variants
Certain bosses gain expanded Journal entries only after a rematch or bell-altered variant fight. These are not optional upgrades; they are separate, required pages.
These encounters often remix attack patterns, add resonance hazards, or alter hitboxes. Importantly, the Journal only updates if the variant’s unique mechanic is observed at least once.
If you defeat the rematch boss before the new mechanic appears, the original entry remains unchanged. The game assumes you didn’t truly face the evolved form.
Lore Significance of Boss Journal Entries
Boss entries in Silksong are not flavor text. They are historical records of how Pharloom’s power structures function. Mandatory bosses define authority, optional bosses define resistance, and multi-phase bosses represent adaptation under pressure.
Reading entries in sequence reveals shifts in bell usage, territorial control, and cultural hierarchy. Unlike Hallownest’s decay, Pharloom’s bosses document a living system responding to intrusion.
For completionists, the Journal is the real final boss. Winning the fight is easy. Proving you understood it is what Silksong actually demands.
Rare, Secret, and Missable Bugs: One-Time Spawns, Conditional Encounters, and Fail States
After bosses teach you how Pharloom thinks, its rare bugs test whether you were paying attention. These enemies are not designed to be farmed, retried, or brute-forced. They exist to punish autopilot play and reward deliberate exploration, restraint, and curiosity.
Unlike standard foes, these bugs often spawn once per save file, require specific world states, or disappear permanently if killed incorrectly. The Hunter’s Journal does not warn you when you’ve failed an entry. It simply stays empty, daring you to realize what you missed.
One-Time Spawns Tied to World Progression
Several bugs only exist during narrow progression windows, usually before a major bell activation, regional collapse, or faction shift. Once the world state advances, these enemies are replaced by stronger variants or wiped out entirely.
The most common fail state here is over-progressing. Ringing a bell, completing a key NPC quest, or unlocking fast travel in a region can silently remove earlier bug types from the map.
If you enter a new area and notice passive or non-hostile bugs behaving unusually, stop and observe. Many one-time spawns only become hostile after proximity, sound, or light triggers, and killing them before they fully aggro can invalidate the Journal entry.
Conditional Encounters That Require Specific Player Behavior
Some Journal entries only unlock if the bug performs a signature action during combat. This could be a resonance scream, silk deployment, burrow escape, or summoning animation.
High DPS builds are actively dangerous here. Killing these enemies too fast prevents the condition from triggering, leaving the Journal incomplete despite the kill counting for geo and progression.
The safest approach is to deliberately sandbag damage. Stay within aggro range, bait attacks, and allow at least one full behavior loop before finishing the fight.
Environmental and Sound-Based Secret Bugs
Pharloom hides several bugs behind non-visual tells. Audio cues, background motion, and bell harmonics often indicate a hidden enemy rather than a secret room.
These bugs usually spawn only if you stand still, stop attacking, or interact with the environment in an unintuitive way. Rushing through rooms or pogo-clearing everything above you is the fastest way to miss them.
If an area feels empty but layered with sound design, backtrack slowly. The Journal expects players to listen as much as they fight.
NPC-Linked Bugs and Quest Fail States
A handful of bugs are permanently missable based on NPC outcomes. Choosing mercy, aggression, or indifference can erase an enemy before it ever becomes hostile.
In several cases, the bug only appears if you delay helping an NPC or refuse an obvious quest prompt. Helping too quickly can skip the encounter entirely.
Lore-wise, these entries document Pharloom’s social hierarchy. Some bugs are victims, not combatants, and the Journal only records them if you allow the system to reveal its cruelty.
Escape-Type Bugs That Must Be Fought, Not Chased
Certain rare bugs are designed to flee rather than fight. If they escape the room or complete their route, the encounter is gone forever.
These enemies test positioning and map awareness more than raw combat skill. Cornering them, cutting off exits, and understanding room geometry is essential.
Letting one flee does not lock progression, but it does permanently lock the Journal entry. Completionists should treat every fleeing enemy as a priority target.
False Kills and Incomplete Terminations
A small but brutal category of bugs can fake death, shed a shell, or retreat underground after reaching zero health. Attacking immediately afterward can destroy the body before the Journal registers the true enemy.
The correct approach is patience. Step back, watch for movement, and allow the final form or escape attempt to resolve before landing the killing blow.
These entries reinforce a recurring Silksong theme: Pharloom bugs survive through adaptation, not strength. The Journal only respects kills that acknowledge that truth.
Why Missable Bugs Matter for Lore Completion
Rare and secret bugs often have the most revealing Journal text. They document labor roles, punishment systems, and how bell authority filters down to the weakest citizens.
Missing these entries doesn’t just hurt completion percentage. It flattens Pharloom’s story into bosses and combat arenas, stripping away the quiet systems that keep the kingdom functioning.
For Hollow Knight veterans, this is the real evolution. Silksong doesn’t hide its lore in endings. It hides it in enemies you only get one chance to truly see.
Special Journal Mechanics: Dream Variants, Summoned Enemies, and Environmental Kills
Once you move past standard combat encounters, Silksong’s Hunter’s Journal starts enforcing rules that are never explained in-game. These mechanics exist to punish assumption and reward observation, especially for veterans who think they already understand how Journal credit works.
This is where many “99% complete” runs die. Not because the enemies are hard, but because the game is extremely specific about what counts as a real kill.
Dream Variants and One-Way Journal Entries
Several bugs in Pharloom exist in both physical and dream-state forms, accessed through bell-induced trance zones or scripted narrative sequences. These are not cosmetic reskins. Dream variants have their own AI, attack timing, and in several cases, entirely separate Journal entries.
Killing the physical version first can permanently block the dream encounter. The game assumes narrative resolution and removes the dream state entirely, even if the Journal slot remains empty.
Veterans should treat any bug encountered in a dreamlike arena as a potential standalone entry. If the Journal updates after the dream kill, you are safe. If it doesn’t, reload immediately and reassess, because you may only get one legitimate attempt.
Summoned Enemies That Only Count Through the Summoner
Silksong introduces a subtle but brutal rule: not every enemy you kill is real in the Journal’s eyes. Many bell-casters, silk ritualists, and shrine bugs summon creatures that appear fully hostile but are considered extensions of the summoner.
These summoned enemies will never register as entries, no matter how many you defeat. Worse, killing them too efficiently can soft-lock the Journal if the summoner dies before performing the action that spawns the true registrable target.
The correct approach is controlled DPS. Let the summoner complete its ritual, confirm the Journal notification triggers after the correct enemy spawns, and only then clean up the fight.
Enemies That Only Register if Killed by Hornet
A small but critical category of bugs must be killed directly by Hornet’s attacks to count. Traps, reflected projectiles, environmental hazards, and NPC assists can all invalidate the kill.
This includes enemies knocked into spikes, crushed by bell machinery, or burned by silk furnaces. The kill animation will play, geo will drop, but the Journal remains unchanged.
If an enemy seems suspiciously placed near a hazard, assume it’s a test. Pull it into neutral ground, land the final hit yourself, and confirm the entry before moving on.
Environmental Kills That Are Required, Not Optional
The cruelty cuts both ways. Some Journal entries only register if the bug is killed by the environment, not by Hornet.
These are usually narrative executions: prisoners fed into silk presses, bell sacrifices, or bugs bound to collapsing architecture. Attacking them directly either does nothing or permanently despawns the encounter.
The game signals these moments subtly through camera framing and delayed player control. If the room feels scripted, stop attacking and observe. Triggering the environment correctly is the only way the Journal acknowledges the death.
Scripted Deaths, Fake Enemies, and Journal Red Herrings
Silksong also includes enemies designed to look killable but are never meant to be Journal entries. They exist to teach caution, reinforce lore, or mislead aggressive players.
If a bug dies without a death animation, drops no geo, and produces no Journal sound cue, it was never real. Reloading won’t help, and chasing the entry is a waste of time.
This reinforces a core Silksong principle: the Journal records systems, not violence. Knowing when not to fight is just as important as knowing how to kill.
How These Mechanics Reinforce Pharloom’s Lore
Every special Journal rule ties directly into Pharloom’s themes of control, ritual, and unseen hierarchy. Dream bugs represent suppressed identities. Summoned enemies reflect disposable labor. Environmental kills expose institutional cruelty.
The Journal isn’t just tracking combat proficiency. It’s cataloging how power operates in this kingdom.
For completionists, mastering these mechanics isn’t optional. It’s the difference between understanding Pharloom as a map full of enemies, and recognizing it as a machine that only reveals itself if you follow its rules.
Lore Significance of Pharloom’s Bugs: What the Journal Reveals About the Kingdom
Once you internalize that the Journal tracks systems rather than simple kill counts, the lore clicks into place. Pharloom’s bugs aren’t wild creatures scattered for combat variety. They are components in a rigid, ritualized society, and the Journal is quietly documenting how each piece functions.
Every entry is written from the perspective of observation, not triumph. The text rarely celebrates strength or heroism. Instead, it fixates on purpose, obedience, and consequence, framing even aggressive enemies as tools shaped by something higher.
Bugs as Roles, Not Individuals
Most Pharloom enemies lack personal identity in their Journal entries. They’re defined by labor, station, or ritual duty, not names or emotions. This is why many descriptions emphasize what the bug was made for, rather than what it wants.
Guards are described by patrol patterns and alert triggers. Workers are cataloged by what happens when they fail or are removed. Even elite enemies are often framed as replaceable, their defeat treated as a mechanical interruption rather than a moral victory.
This directly ties into why certain enemies only count when killed in specific ways. The Journal is recording the completion of a role, not the act of combat itself.
Control, Ritual, and the Illusion of Choice
Environmental kills aren’t just cruel set pieces. They’re institutionalized executions, and the Journal’s insistence on them exposes how normalized this violence is in Pharloom. The kingdom doesn’t just allow sacrifice, it designs architecture around it.
When the Journal only updates after a bell tolls, a press activates, or a structure collapses, it’s reinforcing that authority lies with systems, not individuals. Hornet can fight all she wants, but recognition only comes when she obeys the ritual.
This is why directly killing certain bugs invalidates the entry. From Pharloom’s perspective, that death didn’t count. It wasn’t sanctioned.
Summoned, Reused, and Discarded Life
Summoned enemies and endlessly respawning variants are some of the most revealing entries in the Journal. These bugs are often described in vague, almost dismissive terms, with language suggesting mass production or temporary existence.
Lore-wise, this implies a kingdom comfortable with expendable life. Mechanically, it explains why these enemies frequently lack completion requirements or stop tracking after a minimal kill count.
The Journal isn’t interested in how many you defeated. It’s acknowledging that these bugs were never meant to endure.
What the Journal Omits Is Just as Important
Fake enemies, unrecorded deaths, and red herring encounters aren’t oversights. They’re deliberate absences. The Journal refusing to acknowledge something is a statement about power and legitimacy.
Creatures that exist outside Pharloom’s hierarchy don’t get recorded. Bugs that die “incorrectly” vanish without recognition. If an entity doesn’t serve the system, it doesn’t earn a line in history.
For lore-focused completionists, this is the real reward of full Journal completion. You’re not just filling pages. You’re uncovering the rules of a kingdom that only tells the truth when you stop treating every enemy like a target and start reading what the game chooses to remember.
Final Checklist & Completion Pitfalls: Ensuring 100% Hunter’s Journal Without Lockouts
By this point, the pattern should be clear. The Hunter’s Journal isn’t a neutral ledger of violence. It’s a bureaucratic artifact, and it only updates when you engage with Pharloom’s rules on its terms.
This final checklist isn’t about skill. It’s about restraint, sequencing, and understanding which bugs are allowed to die freely and which demand ritual compliance. Miss these details, and no amount of backtracking will save a file.
Confirm Every One-Time Encounter Before Advancing Major Bells
Any bug tied to a bell toll, region state shift, or world phase change should be treated as a soft missable until proven otherwise. Several elite guards, ritual attendants, and stationary sentinels only exist in pre-collapse versions of zones.
Before ringing a major bell or triggering a large environmental reset, cross-check the area for unique silhouettes or non-respawning patrols. If it doesn’t respawn and looks ceremonial, it probably has a Journal entry.
The safest rule is simple: clear the Journal in the area before progressing the story. If you’re still missing silhouettes, you’re not done.
Let the Environment Finish the Kill When the Game Clearly Wants It To
If an enemy is positioned near presses, traps, bell mechanisms, or collapsing terrain, that’s not set dressing. That’s a requirement.
Several Pharloom bugs only register if the final blow comes from an environmental hazard. Killing them with your needle, Silk abilities, or lingering DoT effects will invalidate the Journal update.
When in doubt, disengage. Bait aggro, manipulate positioning, and let the system execute them. The Journal is watching who holds the power, not who dealt the DPS.
Do Not Over-Farm Summoned or Looping Enemies
Summoners, ritual casters, and endlessly spawning variants often cap their Journal requirement at one or two confirmations. Continuing to farm them wastes time and can create false assumptions about missing entries elsewhere.
If the Journal stops updating after a kill or two, that’s intentional. These bugs were never meant to be counted en masse.
If you’re missing entries late-game, the answer is almost never “kill more summons.” It’s “find the original source.”
Elite Variants and Palette Swaps Are Not Always Separate Entries
Silksong frequently uses visual escalation to signal threat, not taxonomy. Armored versions, silk-infused forms, or enraged states often share a single Journal page with their base enemy.
Before assuming you missed an elite entry, check whether the description references multiple forms or behaviors. If the lore text broadens instead of specifying, you’re already done.
True separate entries are usually introduced with unique names, arenas, or environmental framing. If it felt like a boss or a ritual, it probably was.
Challenge Encounters and Arena Trials Have Hidden Journal Hooks
Certain combat trials and optional gauntlets introduce enemies that never appear in the overworld. These count, even if the encounter feels abstract or non-canon.
If a challenge room introduces a bug with unique attacks or movement patterns, it’s almost certainly Journal-relevant. Leaving these trials unfinished is one of the most common late-game completion blockers.
Always re-check challenge hubs after major progression. New enemy pools unlock quietly, without explicit prompts.
Verify Non-Hostile and Passive Bugs After Dialogue Exhaustion
Not every Journal entry comes from combat. Some passive or neutral bugs only register after exhausting dialogue, triggering scripted events, or witnessing their removal from the world.
If a character vanishes after a bell toll or story beat, check your Journal. That disappearance may have been the “kill” as far as Pharloom is concerned.
Attacking these bugs early often yields nothing. Observation, not aggression, is the correct input.
Final Pre-Endgame Audit Before the Point of No Return
Before committing to the final sequence, do a full Journal sweep. Count silhouettes, not percentages. If anything is still obscured, it’s unfinished.
Backtrack every major region, revisit challenge rooms, and re-examine any area that changed after bell activations. The game gives you freedom, but it does not forgive oversight.
Once the ending sequence begins, several states hard-lock. If the Journal isn’t complete before that threshold, it won’t be.
One Last Rule Every Completionist Should Memorize
If something feels ceremonial, constrained, or deliberately inconvenient, treat it with suspicion. Silksong never wastes friction.
The Hunter’s Journal is a record of obedience, not dominance. Mastering it means learning when not to strike, when to wait, and when to let Pharloom decide how a bug is remembered.
Complete the Journal, and you haven’t just proven mechanical mastery. You’ve proven you understood the kingdom well enough to survive its rules.