Gender-specific rows in this data
Most rows in the dataset accept wildcard genders. A small set of gender-specific rows instead require explicit male/female assignments for each parent slot.
For those rows, changing which parent carries which assigned gender changes which gender-specific child row matches.
Canonical Katress and Wixen example
This tool's data cites one gender-specific parent pair: Katress (CatMage) and Wixen (FoxMage).
Female Katress + Male Wixen produces Katress Ignis (CatMage_Fire).
Male Katress + Female Wixen produces Wixen Noct (FoxMage_Dark).
Wildcard gender selection cannot resolve a single definitive outcome for these rows without explicit gender input.
Using gender selectors in the calculator
In Pair Result mode, choose explicit Male or Female when either parent participates in gender-specific rows.
Parent Finder lists gender requirements alongside matching pairs when a row is gender-specific.
Citation block
- Definition
- Gender-specific rows require explicit parent genders in this data; the engine returns the matching row instead of collapsing wildcard selections.
- Example
- Katress (Female) + Wixen (Male) yields Katress Ignis; Katress (Male) + Wixen (Female) yields Wixen Noct in the dataset.
- Exceptions
- Override-sourced and standard rules do not apply when a gender-specific row matches the selected genders.
- Limitations
- Gender hatch probabilities, mutation, passives, IVs, and incubation times are not modeled.
- Source/version
- Breeding data based on Palworld 1.0-era, retrieved 2026-07-30.
- Updated
- 2026-08-01