Pedigree Possibility

I don’t know if this has been suggested before or if it already exists (there are a lot of posts after all and I’ve been gone from the site for several years due to lack of internet) but I was thinking it might be helpful to have an option where you check to see if there is any cross over of the same horse(s) between a pair of horses chosen to be breed together. 

It’s perfectly easy to check with short lines and there is the inbreeding block but anything over (I believe) third generation is no longer blocked and for the horses that have very long lines it can get difficult (and possibly confusing) to check for any cross over.

Is this something anyone else would be interested in?

Theoretically, duplicate horses are highlighted in a pedigree. But I've seen more instances where this feature isn't working than where it is.

Last edited on 2020-09-22 at 17:51:04 by Sonoma

There is the Inbreeding Checker Tool that is located in the Help section under breeding. 

But you're right it blocks the following:

Parent x Child
Sibling x Sibling
Uncle/Aunt x Niece/Nephew
Grandparent x Grandchild

I'd like to avoid line breeding at least for the first full pedigree page just to try and keep it as diverse as possible. Maybe something along the lines of the inbreeding tool, but for the full generations? Not sure how difficult that would be to code, but it would be helpful in the instance you're talking about.

Last edited on 2020-09-22 at 19:26:26 by Niner

@Sonoma - The red color indications are certainly very helpful, but it’s still difficult with very long lines, especially if both the sire and the dam have rather long lines. Personally I’m not sure if it’s a bug or if that part of the coding that only highlights the same horse per pedigree page; I would need to keep track of it more to determine before I could get a better idea if it should be submitted as a bug.

@Niner - While I’m not so sure on the coding, there is something already in place with the Inbreeding Checking Tool that could perhaps be added to and tweaked for the heritage of both horses. I think it would really depend on how both the pedigree pages and the Tool Checker are currently coded. It would probably be based on a ‘if then else’ concept I imagine but I could be wrong. I think this site used PHP and I’m not as familiar with that as I am HTML and CSS.

If the something isn't working properly- like the duplicate names in the pedigree, please report in the bug zapper with examples. 


I'm not sure if I can see much of a benefit for this personally when it's already possible to check albeit a bit lengthy and annoying in some cases. Thinking also of when searching the user log it's incredibly laggy looking through those entries, and riding school lag where sending multiple requests to the game, I can only imagine how long it would take to search super long pedigrees in the game and return results. 

Not to mention I think it would be a bit moot if you want to avoid inbreeding in old lines, as pretty much every single pedigree existing before this version is inbred to some degree. You would probably have an easier time checking lines started on this version. Just my opinion, it'd be more of a hindrance to breeding to me than a positive addition. 

Hm, I didn’t take lag into consideration but it certainly should be considered. Perhaps if the “Tool Checker” or whatever it would hypothetically be called would have a warning about the lag and thus needing to wait for the results? Maybe a loading indication to show that it’s actually checking so people don’t click/submit/etc again? I think if it’s only going to lag for the individual player then that might be acceptable to them as long as they’re aware that the “tool” is checking. On the other hand if it causes the whole site to lag that would be a problem. Perhaps in that case more user input per say could reduce the lag to acceptable level - how to do that would have to be flushed out more of course. Maybe only check horses from a certain date onwards, for example every horse from when V2 went live and nothing from before. I’m not sure if that option would reduce or increase the lag though; I suppose it might depend on how it’s coded.

Last edited on 2020-09-24 at 04:40:06 by RM