What are Hatchmon in Neon Abyss 2?
Hatchmon are companions obtained through the egg system. They can contribute attacks or utility and can become part of a wider weapon, item, Faith, or set build.
Neon Abyss 2 Hatchmon
Neon Abyss 2 Hatchmon guide for eggs, companion roles, evolution paths, build fit, unlock links, and deciding when to hatch or hold. Verified October 2026.
~10 min read
At A Glance
This Neon Abyss 2 Hatchmon guide treats every egg as a live run decision, not an automatic pet pickup. Eggs build hatch progress and can become companions; Hatchmon can attack, provide utility, and combine into stronger forms. The useful loop is to acquire an egg, check its competing value, advance or accelerate its hatch only when the companion helps now, then judge the result by room safety and boss uptime. Exact hatch thresholds, complete species lists, evolution recipes, and per-Hatchmon values remain Unverified unless the current version 1.0 interface shows them. Verified October 10, 2026.
The shortcut is role-first evaluation. You do not need a complete tier list to decide whether a Hatchmon belongs in a run. Ask what problem it solves, whether it acts often enough to matter, and whether eggs have a stronger immediate use as payment, Faith progress, or part of a set loop. A companion that covers an unreachable lane can be worth more than one with impressive effects that duplicate damage you already have.
| Fact | What is safe to conclude |
|---|---|
| Eggs | Eggs can hatch into Hatchmon and may also have competing run uses |
| Companions | Hatchmon follow the run and can contribute attacks or other abilities |
| Growth | Hatchmon can combine or evolve; recipes and thresholds must be checked live |
| Build role | Companions can become part of a weapon, item, Faith, or set engine |
| Lovely Legion in 1.0 | Its documented direction converts egg value toward shields |
| Co-op | Each player can have personal weapons, Hatchmon, and effects |
| Verification boundary | Names, stats, rarity, hatch timing, and full evolution paths require current UI evidence |
How do Hatchmon eggs work in Neon Abyss 2?
An egg is potential value with a delay. Acquiring eggs advances the run toward more Hatchmon, while some effects can change hatch progress or reward obtaining and hatching eggs. Public gameplay shows eggs eventually opening into Hatchmon and later companions combining. That proves the broad loop, but it does not establish one universal timer or one recipe for every species.
| Egg state | Decision | Reason |
|---|---|---|
| Just acquired | Read current egg and build effects | An item, Faith, or set may change what obtaining or hatching it does |
| Progressing normally | Keep playing if the run is stable | Do not pay a premium merely to remove a manageable delay |
| Acceleration offered | Compare its cost with the companion’s expected role | Faster is useful only when the result helps before the next threat |
| Merchant or room accepts eggs | Price the lost Hatchmon opportunity | The egg is a resource as well as a future companion |
| Several Hatchmon are active | Look for a proven shared payoff | Companion count alone is not a complete build |
Count opportunity cost, not just hatch progress
An egg can compete with gold, HP, keys, bombs, and other route resources depending on the live offer. Selling or spending one is sensible when the immediate purchase prevents a run loss or completes a reliable engine. It is weak when the player pays only because an offer exists.
Do not infer a universal clock
Effects can alter progress, and version changes can rebalance pacing. Record what moved the current egg meter instead of publishing a fixed room count from one run. The correct practical question is whether the companion will arrive before the encounter where its job matters.
When should I hatch an egg instead of holding it?
Hatch now when the run needs companion value immediately, when the hatch completes a verified trigger, or when holding the egg has no identified higher-value use. Hold when a known shop, Faith choice, recruitment, or Lovely Legion interaction makes the egg strategically valuable and the current rooms are already stable. If neither side has evidence, preserve flexibility rather than spending a scarce egg to satisfy curiosity.
- Do01Name the room or boss problem the new companion should solve
- Do02Check whether an egg is required by the next known shop, room, or Faith choice
- Do03Read any effect that triggers on obtaining versus hatching an egg
- Do04Keep a survival buffer before paying to accelerate progress
- Do05Prefer immediate coverage when the run cannot reach or control a threat
- Do06Mark unknown species, thresholds, and outcomes Unverified
Immediate value beats theoretical ceiling
A modest Hatchmon that starts covering enemies now can be better than preserving eggs for an elaborate combination that may never appear. Conversely, a healthy run does not need to force an early hatch when the egg is enabling a stronger documented resource loop.
Use a before-and-after room test
Before hatching, note which targets consume time or HP. After hatching, watch whether the companion reaches those targets, distracts them, adds control, or merely repeats your existing damage. The change in safety and uptime is more useful than visual size.
How do I judge a Hatchmon without a tier list?
Judge an unknown Hatchmon by job, trigger, uptime, coverage, and cost. Job is the result you need. Trigger is what makes the companion act or its effect occur. Uptime is how consistently it contributes. Coverage is the threat it can reach that the main weapon cannot. Cost includes eggs, room choices, Faith, items, and the opportunity to build another direction.
| Observed job | Useful when… | Warning sign |
|---|---|---|
| Damage | It attacks targets while you preserve safe weapon uptime | Its attacks duplicate an already solved lane |
| Crowd coverage | It reaches side, high, or distant enemies | It follows too slowly for the room pattern |
| Control | Its effect creates safer movement or interrupts pressure | The trigger is too rare to plan around |
| Survival | It produces or protects recovery and shields reliably | The benefit requires more damage than it prevents |
| Resource engine | Obtaining, hatching, or supporting eggs returns usable value | The loop needs more eggs than the route can sustain |
| Combination piece | A live description proves the next form and benefit | The plan depends on a remembered recipe |
Tier lists hide run context
A global rank cannot know your weapon range, Agent ability, current Faith, room route, or survival state. Rank the job inside the current run: essential, useful, duplicated, or unsupported. That four-part label is enough to make the next egg decision.
More companions can create noise
A crowded screen does not prove effective damage. Watch clear time, hits avoided, boss uptime, and whether the companion reaches its target. If the result cannot be separated from weapon and item effects, keep the conclusion observational rather than inventing a stat.
Then spend Faith with a Temple plan
Matched by build plan, shared topics, and guide progression — not random related links.
How do Hatchmon evolve and combine?
Hatchmon can combine into stronger companions, but this page does not claim a complete Neon Abyss 2 Hatchmon evolution list. Gameplay footage visibly shows companions combining and a larger form appearing; it does not prove that every Hatchmon uses the same count, rarity rule, or branch. Read the current companion panel before planning a recipe.
| Verify | Capture from the live build | Why it matters |
|---|---|---|
| Inputs | Exact names and number of Hatchmon involved | Prevents a visual coincidence from becoming a false recipe |
| Result | Resulting name, form, and displayed ability | Separates evolution from an unrelated pickup |
| Condition | Automatic, room-triggered, item-driven, or manual behavior | Determines whether the path can be planned |
| Retention | Which prior effects remain after combining | A bigger form may change rather than simply add abilities |
| Version | Game version and update date | Recipes and balance can change |
Do not combine away needed coverage blindly
If two companions solve different lanes, a combination may concentrate their value into one behavior. Confirm what the result does before treating “larger” as “strictly better.” The correct evolution is the one that preserves or improves the job the run needs.
Test the result immediately
Use the next ordinary room to observe targeting and cadence, then a durable target to observe uptime. If the evolved form changes the build’s safe position, adjust the weapon and item plan rather than assuming the old loop still works.
How does the Lovely Legion set change the egg loop?
The version 1.0 Lovely Legion direction connects eggs with shields. Gameplay shows an egg-focused run converting egg-related value into repeated shield drops. Treat that as the set’s strategic lens—eggs can become survival economy—without inventing an exact piece threshold, conversion rate, cap, or every item name. Those details require current set panels.
| Run state | Lovely Legion decision |
|---|---|
| Low durability | Value a verified egg-to-shield effect as a survival layer |
| Stable shields, weak damage | Do not keep adding survival if it prevents fixing damage or coverage |
| Egg supply is frequent | Test whether the displayed set effect creates a repeatable loop |
| Egg supply is scarce | Avoid buying unsupported pieces only for an assumed future threshold |
| Merchant accepts eggs | Compare immediate purchase value with the shield and Hatchmon value forgone |
Eggs stop being one-dimensional
With a verified Lovely Legion effect, an egg can represent a future companion, set progress, or survival. Choose the result that fixes the current constraint. If shields are already abundant, converting every remaining decision into more shields may lower the run’s overall power.
Separate set direction from exact math
The footage supports the visible egg-and-shield loop, not a permanent formula. Use the current tooltip for activation requirements and count the observed shield returns over several rooms before making the loop your only defense.
Which Hatchmon fits my current build?
Match a Hatchmon to the action your build already performs safely. A short-range weapon benefits from autonomous coverage that reaches awkward enemies. A slow heavy weapon may value control or cleanup between attacks. A summon or egg engine values effects explicitly tied to Hatchmon count, obtaining eggs, hatching, awakening, or combining—but only when the live wording confirms that trigger.
| Current build | Look for | Avoid forcing |
|---|---|---|
| Close-range weapon | Remote coverage, control, or safe cleanup | Another effect that requires unsafe contact |
| Long-range weapon | Protection near the player or pressure on blind spots | Coverage that never reaches the active lane |
| Slow attack pattern | Companion uptime between attacks | A trigger requiring rapid weapon hits unless proven workable |
| Hatchmon-heavy run | Shared egg, hatch, awaken, combine, or count triggers | Pieces with only visual companion theming |
| Low-survival run | Reliable shield, control, or recovery value | Speculative evolution at the cost of immediate safety |
Faith can redirect the plan
Faith can interact with rewards, shops, Hatchmon recruitment, and risk choices. Recheck the egg plan after choosing a Faith direction. A Faith benefit that rewards granting or hatching eggs can turn an ordinary action into an engine, while changing direction can remove that reason to hoard.
Co-op companions remain personal build pieces
Players can carry personal Hatchmon and effects, so coordinate jobs rather than demanding identical companions. One player can provide companion coverage while another preserves eggs or resources for a different engine. Confirm any pickup ownership rule in the live session before allocating a contested reward.
How should I verify a Hatchmon entry in version 1.0?
A useful Hatchmon entry needs evidence, not only a name. Record the egg or source, displayed companion name, visible ability wording, attack or utility behavior, evolution requirement, resulting form, related items or Faith, game version, and a reproducible room test. Leave rarity, damage, cooldown, and hidden targeting rules TBA / Unverified when the interface does not show them.
- Do01Capture the full tooltip without cropping the condition
- Do02Record the game version and whether the run is solo or co-op
- Do03Identify obtaining, hatching, awakening, and combining as separate triggers
- Do04Test targeting in an ordinary room and uptime against a durable enemy
- Do05Record exact evolution inputs and resulting form
- Do06Do not infer damage numbers from particles or one critical hit
- Do07Retest after a balance update before preserving old values
Keep observations reproducible
“It felt strong” cannot be checked. “The companion reached the upper target while the weapon stayed on the floor lane” is reproducible. Record the room, weapon, Agent, relevant items, Faith, and other Hatchmon so later tests can isolate the same behavior.
Use unknowns honestly
A partial table with explicit unknowns is more useful than a complete-looking list built from old footage. Version 1.0 changed systems and sets; preserving the verification boundary keeps the guide accurate when values move.
What else should I know about Hatchmon?
Should I hatch every egg immediately?
No. Hatch when immediate companion value or a verified hatch trigger beats the egg’s next known merchant, Faith, recruitment, or set use.
Do all Hatchmon evolve the same way?
No universal evolution rule is verified here. Check the current companion interface and record exact inputs, conditions, and resulting form.
Is Lovely Legion a Hatchmon set?
Lovely Legion is documented as an egg-focused set direction whose version 1.0 presentation connects eggs with shields. Exact pieces, thresholds, and values should be read from the current set panels.
What should I read after this Hatchmon guide?
Then spend Faith with a Temple plan, compare companion triggers with items, or return to the beginner guide for the full run loop.
Related pages
Matched by build plan, shared topics, and guide progression — not random related links.