Anubis Breeding Combos and Parent Guide

Reliable ways to breed Anubis

Anubis has 234 parent records in the current v26 table. Older pre-1.0 guides commonly recommend Bushi plus Penking, but that pair now returns Sibelyx in this data version rather than Anubis. Use the live list above instead of carrying an old combination into a new save.

When two accessible pairs are available, compare the full breeding project rather than the species names. A clean parent line usually saves more cake and incubation attempts than a nominally easier pair with many unwanted traits.

Worker Anubis versus combat Anubis

Anubis is valued as a base worker because of strong Handiwork and useful Mining and Transporting coverage. A crafting-focused Anubis benefits from work-speed traits when it stays at a production station. A mobile base role may benefit from movement or uptime traits because travel and task switching consume part of the work cycle.

A combat Anubis needs a different plan. Attack, cooldown reduction, durability and Earth-focused traits can all be useful, but the best four depend on active skills and the fights you intend to run. Do not pollute a strong worker line with combat passives unless the same parent is deliberately serving as a trait carrier.

Step-by-step Anubis breeding plan

Define the final role before selecting parents. Then search Anubis and shortlist parent pairs you can obtain. Inspect both parents' passives and keep alternate pairs when the main line produces a poor gender balance or noisy traits.

1. 1
   Choose the role

   Separate worker, combat and trait-carrier goals.

2. 2
   Search all pairs

   Do not stop at the first combo copied from an old guide.

3. 3
   Select clean parents

   Prefer the pair carrying only relevant passives.

4. 4
   Keep useful intermediates

   Store clean Anubis hatches even if their IVs are not final.

5. 5
   Condense only at the end

   Finish the trait line before spending heavily on rank upgrades.

Why an Anubis result can differ

First verify the exact parent variants. A base species and an elemental variant are separate entries. Next compare the calculator's data version with your game build. Finally, remember that child species and passive results are separate: getting Anubis with the wrong passives does not mean the species combination failed.

The current page uses PalCalc v26 and an exact pair table. It does not infer Anubis only from an average breeding-power formula.

Current v26 Anubis pair examples

The live search is the source of truth, but examples make the 1.0 change concrete. Current records include Univolt Cryst plus Moldron Cryst, Beakon Cryst plus Moldron Cryst, Relaxaurus Lux plus Jormuntide Ignis, Moldron plus Jormuntide Ignis, and Anubis plus Anubis. These examples use exact variants; dropping a suffix changes the row.

Do not assume the first listed pair is the easiest. Some examples involve variants from later progression, while another pair in the 234-record list may match your box. Search the target, compare accessible parents, and then choose the cleanest passive pool.

Migrating an early-access Anubis line

If an old plan starts with Bushi and Penking, stop before baking a batch. That pair now produces Sibelyx in v26. Keep any useful passives on those Pals, but transfer them through a parent that appears in the current Anubis results rather than expecting the historical child.

Rebuild from the target backward. Select Anubis in the live search, find a current pair containing one accessible trait carrier, and use the one-parent mode to identify the required mate. If neither side is available, add your owned Pals to the route planner and create one current direct parent first. This preserves the useful parts of the old trait plan while correcting the species route.

With 234 current records, filtering is more valuable than reading every pair equally. Divide candidates into owned, directly capturable and multi-generation groups. Remove pairs whose exact variants are unavailable, then compare the remaining passive pools. If two pairs are equally accessible, prefer the one that reuses a clean carrier for another planned target; this spreads setup cost across several projects.

Keep the first correct Anubis of each useful gender even when it is not the final build. Anubis plus Anubis remains a valid current pair, so a clean self-breeding line can gradually replace the temporary species parents used to enter the project. Once both sides are Anubis, species verification becomes simple and trait refinement is easier to track.

Review current Anubis breeding pair data

Current Anubis breeding pair data is only the first input in the total project cost. Count how many parents must be captured or produced, whether the exact variants are available, which genders the next generation requires and how many unwanted passives enter the final pool. A pair using common names can still be expensive when both parents need several cleanup generations.

Score shortlisted pairs on access, passive quality and reuse. An owned parent with two clean worker traits may justify an extra intermediate because that carrier can support future base Pals. For combat Anubis, a different pair may preserve attack or cooldown traits more cleanly. Keep those projects separate so a positive worker trait does not become noise in the combat line.

After the first correct egg, replace temporary species parents one at a time. Keep a clean Anubis of each useful gender and compare every replacement batch against the previous pool. Once Anubis plus Anubis becomes the active pair, the species result is easy to verify and the remaining work can focus on passives, IVs and backups.