Panda breeding does not work as intended. Breeding two pandas create offspring with multiple genes different from its parent, as if it were randomized.
CONTEXT:
Pandas have two genes - a main gene (expressed through panda's appearance and behavior), and a hidden gene (can only be discovered by breeding). 2 random genes from the parents get passed onto the offspring and the main gene is expressed as the texture of the panda. Normal, angry, lazy, playful and worried are dominant personality genes. A brown and weak panda is recessive and can only appear if its genes are the same.
"A brown variant is recessive and can only appear if its main and hidden gene are both brown." In the game, breeding two brown pandas creates different panda variant offspring. The expected result should only be a brown panda, with a 3% chance of mutation of a different variant. The actual results are different panda variants such as lazy, playful, aggressive, etc.
Steps to Reproduce:
Create flat world in creative mode
Use spawn panda egg until 2 Brown Pandas appear
Lure the 2 Brown Pandas into a fenced area with bamboo
Place at least eight bamboo blocks within a five-block radius of the 2 pandas
Breed both of the Brown Pandas using bamboo
Observe the offspring variant and Repeat steps 4 to 5.
Expected Results:
Offspring is a brown panda variant.
Observed Results:
Offspring variants are completely randomized
[media]Panda offspring after breeding for 5 times. Offspring variants shown are normal, worried and weak.
Notes:
This doesn't only happen to brown pandas. Panda genes are randomized when breeding with other panda variants. I only used the brown panda as an example because it is easy to show the bug. I have marked this as a bug because this would mean that the "genetics component" of the game is broken, and any mob added to the game in the future with the genetics component will also be broken in Bedrock Edition.
I have tested this on Java and the results are what I expected - brown pandas give birth to brown pandas. Other panda variants also have the expected offspring.
This bug has now been fixed in the 1.17 update