Ticket #20 (closed data bug: fixed)

Opened 3 years ago

Last modified 2 years ago

Evolution chain bases are inconsistent

Reported by: eevee Owned by: eevee
Priority: major Component: pokedex
Keywords: pokemon page Cc: <Default>
Difficulty: involved

Description

I think a base is the lowest form that is NOT an egg. D/P thinks a base is the lowest form, period. This led to problems when I imported new Pokemon and new moves; bases are off and a lot of rows in pokemoves are duplicated. Figure out which way works better and fix it. Given that I now have a flag for whether a Pokemon is a baby, changing it shouldn't be a problem, but grep anyway.

This bug is what's causing egg moves to be doubled for a lot of Stage 1 Pokemon that have baby forms.

Attachments

Change History

Changed 3 years ago by anonymous

Another complication is #50: e.g., Munchlax and Snorlax have different egg moves, since an egg can contain either.

Changed 3 years ago by eevee

Baseform egg moves no longer show as of r276, which partially addresses this and fixes the comment. The moves themselves will still need rearranging, though.

Changed 2 years ago by eevee

Egg moves fixed in r355. Still looking to see where evchains.base is used in the code and why; any quirks from that are the only bits left.

Changed 2 years ago by eevee

  • status changed from new to closed
  • resolution set to fixed

Last use of said column removed by r356. Only other base-related problems I know about are covered by #88. Closing, finally!

Add/Change #20 (Evolution chain bases are inconsistent)

Author


E-mail address and user name can be saved in the Preferences.


Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.