negative numbers in lineage?

[HeatherMarie]

I've been going through *all* my dragon's lineages in the process of making a few new groups, and I've noticed this a few times now. At first I thought it had something to do with dead dragons in the lineage, but now I'm seeing it on lineages where there are no dead dragons. This dragon shows this:

 

 

 

Any idea why this happens, and is it a bug or some sort of feature?

 

edit: Another example of negative gens in lineage, strangely also Dorkface-related.

Edited January 2, 2018 by Marie19R

[tiktokism]

Found more, Both Dorkface and Not. This topic is giving me a sense of déjà vu, but I didn't come up with any similar topics when I searched. 

 

 I checked the lineage of one of the "0" dragons from my last example, and that lineage page labels the dragon as gen 12 (Here's that lineage; it has a dead-and-blank ancestor that accounts for the irregularity of its own lineage).

 

In doing more fiddling around looking into this, it appears that my longest lineaged dragon, which I never manually checked, is mislabeled as 37th generation when AOND reports it is 40th generation.

 

It looks like some very old generations aren't being counted accurately in general.  

[Confused Cat]

It looks like it often (always?) starts with a wild dragon with one CB and one lineaged parent, and somehow the wild dragon's lineaged parent is counted as CB (generation 1).

In @Marie19R's first example, this is first (oldest) dragon with negative numbers in his lineage: https://dragcave.net/lineage/TD1f

 

His mother is a 7th gen, and her lineage... um wait. His lineage. The mother is a male dragon. o_O Who has no offspring. (Recycled code, I guess.) Anyway, the mother/father's lineage looks correct:

https://dragcave.net/lineage/2Uqf

 

In @tiktokism's first example, it starts with this dragon: https://dragcave.net/lineage/pFuL

Which is also a wild dragon with one CB and one lineaged parent.

 

2nd example starts here: https://dragcave.net/lineage/228x

Another wild dragon from CB x lineaged. (Not on the Dorkface side of the lineage, so I think Dorkfaces don't directly affect the error.)

 

In the 3rd example, the CB (?) parent of the wild dragon is dead: https://dragcave.net/lineage/zAbf

Its father is this female White dragon: https://dragcave.net/lineage/zGVX

(I expected her lineage to be correct, but there's an error earlier in it, too. https://dragcave.net/lineage/Izux I think it's not directly linked to the other one though. Maybe it is the same glitch, but it just happened to occur twice in one lineage.)

 

[Ruby Eyes]

8 hours ago, tiktokism said:

This topic is giving me a sense of déjà vu, but I didn't come up with any similar topics when I searched. 

You might remember this one:

https://forums.dragcave.net/topic/169995-tiny-little-questions/?do=findComment&comment=9597824

[Imago]

I vaguely remember that it used to be the case that codes of wild/deceased (?) dragons were recycled after some time, leading to problems with already existing lineages and producing dragons with male mothers and/or female fathers. This might also explain the wrong numbering - the original parent might have been CB and the system somehow still remembers this, but displays the "overridden" dragon.

[StarSea]

I think that the concept of it having to do with recycled codes might be what it is but maybe not?
If you look at this dragon, the mother was born in 2010 while the child was born in 2008. (also... the "mother" is male......)
But then you have ones like this one where there don't appear to be any issues between the birth dates of any ancestors and their children in the lineage.

As far as the system remembering whether a parent was CB or not, there's no need. It just records the egg's generation when it's laid. The negative numbers in the lineage counter, I'm assuming, is completely visual as it'd just take the generation number for the dragon you're viewing and count backwards.

Pairings had laid several kids with issues like this and then all the sudden kids that had no issue at all, as well, though (such as that split's parents), making the thought that it is from code recycling odd. If I'm being completely honest, I think we may have two completely different instances in time where the bug happened that may not be related to each other at all.


Also @Confused Cat  I don't think Izux's lineage is a bug. Dead dragon ancestry still count in the lineage counter, so that dead dragon was probably a 5th gen dragon.

Edited January 6, 2018 by StarSea

[maratrekkan]

I have also seen lineages with no generation 1, if I remember right it is a TW dragon completely even gen but it starts in the 2 postition. Really odd that one. 

[HeatherMarie]

Okay, now I'm just starting to think that lineage gen-numbers are screwed up in general. No negative numbers in this one, but it's still numbered wrongly... Shows 1st-gen at the far-right, but it should be 4th-gen, as can be seen by clicking 'Divine Illusions of Dorkface'. 

[Whirlaway]

I think this can all be chalked up to some kind of glitch, really. I've noticed oddities with the lineage bar a few times.