I wrote up a really long post explaining how I thought the compatibility checker worked, how there are possibly 3 different groups relating to the breeding bug, and how those groups are related. Site reset wiped out the version I had typed out last night (bad) and then Peyp's examples broke my understanding (good). I'm not going to edit anything, but I'm still going to post how I thought the checker code worked - so now we know how it doesn't work!
I put it in collapsed quotes so it doesn't eat up the thread's space. Images are tiny but they're all clickable.
Edit: Some info removed because it was bordering too close for comfort to reverse engineering the breeding algorithm. Sorry if you missed it!
I put it in collapsed quotes so it doesn't eat up the thread's space. Images are tiny but they're all clickable.
Edit: Some info removed because it was bordering too close for comfort to reverse engineering the breeding algorithm. Sorry if you missed it!
Previous explanation wrote:
Quote:
Quote:
Quote:
Quote:
I believe that there are three types of categories that may or may not be related bugs. I've been using the charts because I've noticed that whether a dragon is male or female sometimes plays into it. I haven't often checked differing generational levels, but I probably should do more.
First, I want to explain how the compatibility checker seems to currently work in general, at least with regular dragons who themselves don't appear to be bugged. It acts as if dragons A and B will breed and then checks for duplicates in the potential offspring's 5-generational family tree. However, it skips over both grandfathers' grandparents. So, A and B can breed even if B happens to also be in the leftmost big blue box.
Males are on the left and females are on the right. Orange boxes are checked for duplicates, and blue boxes are not. The black box is the potential offspring. The bottom row of tiny boxes is correctly unchecked.
The three categories I see are:
1. Any dragon can breed with its own great-great grandparents. Some dragons from different generational levels can also breed early, but I don't have a succinct way to say that.
This is the current 'normal' behavior of the compatibility checker, which is the orange-blue tree above. It's definitely a bug, but it's also 'normal', so who knows if it even needs a name.
The resulting offspring I guess are technically inbred, but the same dragon may not appear in its 5-generation family tree twice. If the bug is fixed, they would probably remain fertile.
2. Infertile dragons that arose from the old compatibility checking code that has since been patched.
Here is a random infertile dragon I grabbed,
[examples removed]
In all three of them,you can see that the common ancestor falls into what would be orange boxes both times. This is why they are currently still infertile and will always remain that way.
My initial theory was that the compatibility checker functioned similar to how it does now, but that it just messed up one generation earlier. This also seemed to make sense because Mutron said that the current bug (1) is related to (2).
[image removed]
Yeah, I don't really know at all how the checker used to work to make infertile dragons. I don't know if I can ever find out. It doesn't matter too much anymore though, since the code has been changed.
3. Inbred dragons, such as the dual lineage Ignis G5s.
These dragons are definitely inbred, and Ignis appears in their family trees twice. If the bug is fixed, my guess is the same as Malis's - they might end up infertile.
[examples removed]
I don't know how these dragons are able to breed in the first place. Trying to replicate this with different bloodlines has had no success, and in fact seems to break my orange-blue algorithm.
[example removed]
I would venture a guess that this group is the 'patched' version of infertile dragons. Like infertiles, a common ancestor appears twice in the 5-generational family tree. Unlike infertiles, they can still breed for some reason. I also can't figure out why the parents of both of these groups were able to breed in the first place, which is what makes me think they may be similar.
[example removed], but @/Alyxsandre's Moyolehuani fits into the 'normal' pattern.
[removed], but the Ignis example also fits into the 'normal' pattern.
I believe I understand in general how the compatibility checker works. Both of those final two trees still fit into my orange-blue checking algorithm. Group (1) is basically the current behavior. I can't figure out how group (2) was created, but they remain infertile and are consistent with my proposed algorithm's behavior. However, there is definitely something more here at play because my algorithm seems to completely fall apart for Ignis's descendants in (3).
My guess is that the future potential fix for (1) will make dragons like in (3) become infertile due to [information removed]. But all of this is based on the inherent behavior of the compatibility checking algorithm alone. If (3) actually happens due to a glitch with a specific dragon in Ignis's bloodline and not because of the checker itself, then I don't think we can know what will happen until it happens.
tl;dr:
First, I want to explain how the compatibility checker seems to currently work in general, at least with regular dragons who themselves don't appear to be bugged. It acts as if dragons A and B will breed and then checks for duplicates in the potential offspring's 5-generational family tree. However, it skips over both grandfathers' grandparents. So, A and B can breed even if B happens to also be in the leftmost big blue box.
Males are on the left and females are on the right. Orange boxes are checked for duplicates, and blue boxes are not. The black box is the potential offspring. The bottom row of tiny boxes is correctly unchecked.
The three categories I see are:
1. Any dragon can breed with its own great-great grandparents. Some dragons from different generational levels can also breed early, but I don't have a succinct way to say that.
This is the current 'normal' behavior of the compatibility checker, which is the orange-blue tree above. It's definitely a bug, but it's also 'normal', so who knows if it even needs a name.
The resulting offspring I guess are technically inbred, but the same dragon may not appear in its 5-generation family tree twice. If the bug is fixed, they would probably remain fertile.
2. Infertile dragons that arose from the old compatibility checking code that has since been patched.
[examples removed
]In all three of them,
My initial theory was that the compatibility checker functioned similar to how it does now, but that it just messed up one generation earlier. This also seemed to make sense because Mutron said that the current bug (1) is related to (2).
[image removed
]Yeah, I don't really know at all how the checker used to work to make infertile dragons. I don't know if I can ever find out. It doesn't matter too much anymore though, since the code has been changed.
3. Inbred dragons, such as the dual lineage Ignis G5s.
These dragons are definitely inbred, and Ignis appears in their family trees twice. If the bug is fixed, my guess is the same as Malis's - they might end up infertile.
[examples removed
]I don't know how these dragons are able to breed in the first place. Trying to replicate this with different bloodlines has had no success, and in fact seems to break my orange-blue algorithm.
[example removed
]I would venture a guess that this group is the 'patched' version of infertile dragons. Like infertiles, a common ancestor appears twice in the 5-generational family tree. Unlike infertiles, they can still breed for some reason. I also can't figure out why the parents of both of these groups were able to breed in the first place, which is what makes me think they may be similar.
[example removed
], but @/Alyxsandre's Moyolehuani fits into the 'normal' pattern.[removed
], but the Ignis example also fits into the 'normal' pattern.I believe I understand in general how the compatibility checker works. Both of those final two trees still fit into my orange-blue checking algorithm. Group (1) is basically the current behavior. I can't figure out how group (2) was created, but they remain infertile and are consistent with my proposed algorithm's behavior. However, there is definitely something more here at play because my algorithm seems to completely fall apart for Ignis's descendants in (3).
My guess is that the future potential fix for (1) will make dragons like in (3) become infertile due to [information removed
]. But all of this is based on the inherent behavior of the compatibility checking algorithm alone. If (3) actually happens due to a glitch with a specific dragon in Ignis's bloodline and not because of the checker itself, then I don't think we can know what will happen until it happens.tl;dr:
- I think there's 3 types of breeding bugs: Inbred type A, infertile, and inbred type B.
- You already know the drill with infertiles - they cannot be made anymore, but they still exist.
- Inbred type A is the current 'normal' behavior.
- Inbred type B is whatever's going on with Ignis's descendants.
- Inbred types A and B could be related, or they could not be - I can't tell. If the bug causing type A is fixed, then something will happen with type B - I just don't know what.
- My opinion is that inbred type B is the patched version of infertiles
Peyp's examples breaking it wrote:
Quote:
Quote:
Quote:
Quote:
And since I started writing this, there's been more posts, so I'm just throwing this in at the bottom.
Here's Peyp's mentioned dragons, which makes me completely lose confidence in my algorithm, which is a good thing! It's good to know when things are wrong! It just might invalidate a lot of what I've typed above and I'm not going back to edit.
For Idol&Yaimei, it looks like maybe Zinovia's parents are skipped, because she's skipped. But Talos and his parents (who are the same as Zinovia's) might be checked.
[image removed]
But for Queen it's the same, just that Talos and Nebula are moved two boxes to the left. They can't breed, so my algorithm is broken for sure.
[image removed]
Ramiser&Chelan seem to fit in with the same explanation as Idol&Yaimei, except it's all moot now.
[image removed]
At this point, the only thing I'm sure of anymore is that there's an imbalance in the checking, but I don't know how it works at all!
Here's Peyp's mentioned dragons, which makes me completely lose confidence in my algorithm, which is a good thing! It's good to know when things are wrong! It just might invalidate a lot of what I've typed above and I'm not going back to edit.
For Idol&Yaimei, it looks like maybe Zinovia's parents are skipped, because she's skipped. But Talos and his parents (who are the same as Zinovia's) might be checked.
[image removed
]But for Queen it's the same, just that Talos and Nebula are moved two boxes to the left. They can't breed, so my algorithm is broken for sure.
[image removed
]Ramiser&Chelan seem to fit in with the same explanation as Idol&Yaimei, except it's all moot now.
[image removed
]At this point, the only thing I'm sure of anymore is that there's an imbalance in the checking, but I don't know how it works at all!
