Thread:Sylvandyr/@comment-81.108.48.117-20130216114307/@comment-4830404-20130216170238

I'll summarize/expand on the reasons here.

1) With the introduction of Heart dragons, the current format is now out of date.  The Breeding Charts were created with two major assumptions:


 * Any listed color counts as one color towards Diamond breeding. This is no longer true of the Heart color, which counts as zero colors.  The most correct way to respond would be to list LeftHeart and RightHeart in the same group as Athletic (Red/Blue).  However, this would be confusing because we all know that LeftHeart and RightHeart have "three" colors with Heart included.


 * All dragons can be bred based upon color pool alone. The Passion Dragon renders this statement false.  It can only be bred using the LeftHeart and RightHeart dragon together, but every other offspring in the red/blue color pool does not require LeftHeart + RightHeart specifically.  With the current table format, it is impossible to display the distinction for the Passion Dragon correctly.  Using a new table format that *can* display this distinction will make the page even more unwieldy than it already is, and the size of the page is already a problem.

2) The Breeding Charts were originally built as an undesirable but necessary alternative to the Breeding Calculator, which is forced to use javascript by wikia.  However, Hyper ch has built a much better tool off-site here, which does not suffer the limitations of javascript and thus can be run regardless of whether javascript is disabled.  Since it provides much more accurate info than the Breeding Charts in a less load/scroll-intensive fashion, the existence of the Breeding Charts only serves to confuse people and provide incorrect info.

3) Although mentioned before, it requires more stressing.  The Breeding Charts were getting incredibly long due to all the new rules and increasing size of color pools.  Accommodating the Heart dragons would require a complete change to the already-minimized-but-still-gargantuan format, adding even more load time and more ridiculous scrolling, which was literally unusable on my iPhone.  It would be much better to direct people with javascript issues off-site to Hyper ch's tool.