Palworld 1.0 Breeding Guide & Data Changes

Executive summary

This report describes the breeding data currently used by PalBreed Planner for Palworld 1.0. The selector has 300 distinct entries. That total includes exact selectable identities rather than collapsing every variant into a base species: 85 entries are recorded as variants, and 72 entries carry the New in 1.0 label. All 300 entries can be used as parents and searched as targets in this snapshot.

With self-pairing included and parent order ignored, 300 entries produce 45,150 unique pair keys: 300 × 301 ÷ 2. Each key has one default child result in the forward index. Reverse search has 45,151 child-to-pair associations, one more than the forward key count, because Wixen plus Katress has two legitimate outcomes determined by which species is female and which is male.

The current dataset identifies 80 matrix-confirmed special outcomes across 79 parent-pair keys. These labels cross-check exact combinations already present in the imported 1.0 matrix; they are not a separate formula layered over it. Across all 45,150 forward rows, 11,685 default results point to an entry marked new in version 1.0. That is 25.88% of current rows. It is a useful measure of how often the new roster appears as an output in this matrix; it is not a measurement of how many pre-1.0 combinations changed.

Current data figures and their definitions

Measure	Count	What it means
Selectable entries	300	Exact roster selections available as Parent A or Parent B.
Entries marked new in 1.0	72	Roster entries whose introduction label is version 1.0.0.
Variants	85	Selections linked to a base entry but kept distinct for breeding lookup.
Unordered pair keys	45,150	Every two-parent combination counted once, including a Pal paired with itself.
Reverse child associations	45,151	Child-to-parent records used by target search, including both gendered Wixen/Katress outcomes.
Special outcomes	80	Matrix-confirmed exact outcomes cross-checked against 79 parent-pair keys.
New-default-result rows	11,685 (25.88%)	Forward rows whose default child carries the New in 1.0 label.

These definitions matter when comparing figures from different tools. A site that counts only numbered base species will report a smaller roster than one that preserves variants and collaboration creatures as separate selections. A directed table that stores A + B and B + A separately will report nearly twice as many rows as this unordered index. Neither number is meaningful without its counting rule.

Most common default children in the current matrix

The distribution below was counted from the 45,150 deployed forward rows, including rows labeled as special outcomes. It shows how many unordered parent keys have each Pal as their default child. It does not show an egg probability, popularity among players, or the chance of inheriting a passive skill.

Rank	Default child	Parent-pair keys	1.0 label
1	Felbat	1,280	Earlier roster entry
2	Vanwyrm	1,229	Earlier roster entry
3	Azurobe	1,090	Earlier roster entry
4	Valentail	1,021	New in 1.0
5	Warsect	866	Earlier roster entry

Felbat is the most frequent default child in this snapshot with 1,280 pair keys, followed by Vanwyrm with 1,229 and Azurobe with 1,090. Valentail is the highest-ranked New in 1.0 result at 1,021 keys. Counts can be affected by breeding-power neighborhoods, ties, roster composition, and exact special cases, so the table should be cited with the dataset version and review date.

Why 45,150 forward keys become 45,151 reverse associations

Ordinary parent order does not change the child, so each pair needs one forward key. Wixen and Katress are the exception that adds a second reverse association. Female Wixen plus male Katress produces Wixen Noct. Female Katress plus male Wixen produces Katress Ignis. The species pair is still one unordered forward key, but both children must list that key in reverse search with the relevant gender roles.

This distinction also explains why the compact shortest-chain list remains at 45,150 keys. It stores one default edge for each unordered pair. Direct and reverse result views carry the extra gender detail needed to display both valid outcomes. A player copying this pair should record the parent genders as part of the recipe rather than treating Wixen + Katress as sufficient instructions.

What the evidence can—and cannot—say about 1.0 changes

The current snapshot can prove its own roster size, pair-key coverage, result distribution, reverse associations, special-rule count, and internal consistency. The official 1.0 release material indicates that breeding combinations were reviewed, and the current matrix can be used to verify any exact pair a player plans to breed now.

PalBreed Planner does not currently have a pinned, complete pre-1.0 breeding matrix with matching identifiers and provenance. Without that baseline, a row-by-row comparison cannot distinguish an unchanged old result from a changed result across the full chart. For that reason, this report deliberately makes no claim such as “X old combinations changed” or “Y percent of pre-1.0 routes are invalid.” The 25.88% figure above is the share of current rows that lead to a New in 1.0 default child, not a historical change rate.

An old route may still work. The responsible check is narrow: enter the exact two parents, confirm their variants and any gender roles, compare the data review date with the game build, and test one egg before committing to later generations. A verified example can support a statement about that pair; it should not be generalized to the full pre-1.0 matrix.

How the snapshot was prepared and checked

Normalize the roster. Exact 1.0 names and identifiers are retained for base species, variants, supported special entries, and collaboration creatures. Duplicate IDs and slugs are rejected.
Build unordered keys. Every entry is paired with itself and every later entry once, producing 45,150 keys without duplicating swapped parents.
Identify and cross-check exact outcomes. The 80 matrix-confirmed special outcomes are checked across 79 parent-pair keys. The Wixen/Katress key also retains both gender-dependent results.
Create search indexes. Forward lookup resolves two parents to a child; reverse lookup groups parent pairs under each child; the compact pair list supports chain planning.
Cross-check the artifacts. Build checks confirm roster totals, key uniqueness, known Pal references, forward/reverse agreement, special labels, portraits, and the published metadata counts.

The reviewed source list, current data version, usage terms, and stable citation are published on the Palworld 1.0 breeding dataset page. That page should accompany a quoted statistic so readers can recover the definitions and review date instead of seeing a detached number.

How to use this report for an actual breeding route

Use Find a Child when both parents are known. Use Find Parents when you know the target and want alternatives. Use Plan a Chain when the final parents are missing from your Palbox. Exact names matter in every mode because a base Pal and its variant are separate entries. A result is a species outcome; it does not guarantee gender, passive inheritance, individual values, mutations, work bonuses, or a particular number of eggs.

For a costly route, verify from the end backward. First confirm the final pair and special conditions. Then check whether you own either final parent. Compare reverse options, choose intermediates that fit the Pals and useful traits you already have, and test the first egg at every important step. A mathematically short species route may be worse than a slightly longer route that preserves a prepared passive carrier.

If an in-game result differs, report both complete parent names, their variants, gender roles when applicable, the observed child, platform, game build, and a screenshot if possible. A precise discrepancy can be checked in the forward index, reverse index, and source matrix without requiring a login or a complete save file.

Limitations and update policy

The report is tied to data version 1.0.0.100427-2026-07-15.1, reviewed July 15, 2026. A later hotfix may require a new snapshot.
New in 1.0 labels describe roster introduction, not rarity, strength, breedability, or whether a result changed from a prior version.
Default-child frequency counts parent keys, not egg odds or player behavior.
Species routing does not model the probability of inheriting passives, IVs, gender, mutations, or work bonuses.
No complete pinned pre-1.0 matrix is available for a defensible full historical diff.

Corrections are logged by updating the public data version or review date after the reported row is checked. The media resources page explains the project-level correction policy, while the contact page lists the details needed for a reproducible data report.

Use this Palworld 1.0 breeding guide to check a current route

This Palworld 1.0 breeding guide starts with the task you are trying to finish. Use Find a Child when two parents are known, Find Parents when a child is the goal, and Plan a Chain when you want a route from your current collection. Confirm exact names, portraits, variant labels, and the July 2026 update date before starting. Those details are more useful than a vague claim that a chart is current.

Do not rebuild every old breeding plan at once. Check the pair or target you intend to use today. A current result can confirm that an old route still works or show a different option without making unsupported claims about every combination in the game.

Check why an older combination appears wrong

Begin with the simplest causes. Confirm both full species names, including variants, and make sure the screenshot or guide refers to the same game release. Check any gender role shown for a special pair. Then enter the pair in the forward calculator and compare the child. A wrong selection can look like a changed formula even when the intended combination is fine.

If the names are exact and the game still produces another child, record the observed result rather than repeatedly trying the same pair. Platform, build, and a screenshot help distinguish a current rule from an old source or modified game.

Choose between forward, reverse, and chain planning

Forward calculation is a one-pair check. It is fastest when strong parents are already selected. Reverse search shows alternatives for one target, making it better when the recommended parents are missing from your Palbox. Chain planning solves the remaining gap by arranging intermediate children from species you own.

Move between these views as the question changes. A reverse result may reveal the best final pair, while a chain produces those parents. The forward view can then verify every step. Using the same names and current combinations across all three views prevents a route from becoming a collection of unrelated screenshots.

Handle standard and special combinations differently

An ordinary pair can be explored through the general chart. A gender-specific combination must be copied with the displayed roles. In version 1.0, female Wixen plus male Katress produces Wixen Noct, while female Katress plus male Wixen produces Katress Ignis. Reversing the genders changes the child even though the two species names are unchanged.

When a target has no parent results, check its exact variant and acquisition method rather than proposing a guessed pair. An empty result can also mean that the selected Palbox cannot reach the target within the chosen chain depth, so inspect direct parents before concluding the species is impossible.

Plan species first and inherited traits second

A breeding calculator determines the child species for a pair. It does not guarantee passive skills, individual values, gender, mutations, or work bonuses. Choose a reliable species route first. Then examine which parents and intermediate children can carry the qualities you want. Expect additional eggs when a final build matters.

The shortest species route can be poor for inheritance if it uses parents with unwanted traits. Compare it with a slightly longer route that keeps a prepared carrier in the line. Save both plans so you can decide whether time, access, or trait quality is the stronger constraint.

Use a simple pre-breeding checklist

Before starting, confirm the target, both final parents, variants, special conditions, current version, and page update date. Check that each intermediate child appears before it is used. Decide whether route depth or total operations matters more. Keep space for extra offspring when inherited quality is important.

After the first egg from an important pair, compare the observed child with the plan. If it differs, stop the later stages and report the exact pair. This small test protects resources and produces a clear example that can be checked without sharing a full save file.

Frequently asked questions

Do all pre-1.0 breeding combinations fail?

Do not assume that. Verify the exact pair you plan to use. A current check can confirm an unchanged result or identify a different child without turning a limited example into a claim about the entire chart.

What is the fastest way to verify an old pair?

Select the exact two parents in Find a Child, including variants and any required gender roles. Compare the displayed update date and test one egg in the current game before committing to a long inheritance project.

Should I use reverse search or a shortest chain?

Use reverse search to compare direct parent pairs. Use the chain planner when you do not own the selected parents and need intermediate steps from your current Palbox.

Does the shortest route give the best passive result?

No. It optimizes the species route according to displayed path costs. A longer route can be better for passive inheritance when it includes prepared parents or avoids unwanted traits.

What information belongs in an error report?

Include both parent names, variants, gender roles when relevant, observed child, platform, game build, and a screenshot if available. Do not include account credentials or an entire save file.