Template talk:Moveheader/Breed: Difference between revisions
Carmenstar97 (talk | contribs) mNo edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 19: | Line 19: | ||
! style="{{#ifexpr: {{{2|1}}}>5|display:none;|}} background:#6BAECE; color: #FFF; line-height: 1em" colspan="2" | [[Generation V|<span style="color:#fff">V</span>]] | ! style="{{#ifexpr: {{{2|1}}}>5|display:none;|}} background:#6BAECE; color: #FFF; line-height: 1em" colspan="2" | [[Generation V|<span style="color:#fff">V</span>]] | ||
! style="background:#CB0B4F; color: #FFF; line-height: 1em;" colspan="2" | [[Generation VI|<span style="color:#fff">VI</span>]] | ! style="background:#CB0B4F; color: #FFF; line-height: 1em;" colspan="2" | [[Generation VI|<span style="color:#fff">VI</span>]] | ||
|} | |} | ||
::I like that idea! I think I might prefer having it as Parent{{tt|*|Father in Generations II-V}} though - it's closer to the notes used for Pokemon that had a more complex way of getting an egg move in certain generations, but became simpler in later ones. I think that the standard practice in cases like this is to use current terminology with notes as well (but I'm not completely sure). [[User:VioletPumpkin|VioletPumpkin]] ([[User talk:VioletPumpkin|talk]]) 17:44, 28 June 2016 (UTC) | ::I like that idea! I think I might prefer having it as Parent{{tt|*|Father in Generations II-V}} though - it's closer to the notes used for Pokemon that had a more complex way of getting an egg move in certain generations, but became simpler in later ones. I think that the standard practice in cases like this is to use current terminology with notes as well (but I'm not completely sure). [[User:VioletPumpkin|VioletPumpkin]] ([[User talk:VioletPumpkin|talk]]) 17:44, 28 June 2016 (UTC) | ||
:::That would work too, and I guess be more current. Either way would be fine with me personally. [[User:Litwick96|<span style="color:purple">Litwick</span>]]<small>[[User Talk:Litwick96|<span style="color:grey">96</span>]]</small> 19:34, 28 June 2016 (UTC) | |||
Latest revision as of 17:55, 23 December 2016
I think, this template should be wider becouce it is stretched (moves from I and II Generations), when is used on the move's pages.--Dominikololo (talk) 13:08, 27 June 2014 (UTC)
- Wide how? I see no problems with it, they look how they are suppose to be.--ForceFire 13:53, 28 June 2014 (UTC)
Father → Parent?
Since mothers can pass down egg moves as of Gen VI, should this column title be changed? There are many Pokemon that have a move in both their level-up list and their egg move list after all (and are thus one of the fastest ways to 'pass' the move). I suppose the biggest issue is that this is a multi-generation table, since the templates for individual species pages use Parent in Gen VI, but Father on the others. Changing this could make it vague/misleading for older generations, but for current/future generations, it's arguably just plain incorrect. VioletPumpkin (talk) 00:18, 28 June 2016 (UTC)
| # | Pokémon | Type | Father* | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| II | III | IV | V | VI | ||||||||||
- I like that idea! I think I might prefer having it as Parent* though - it's closer to the notes used for Pokemon that had a more complex way of getting an egg move in certain generations, but became simpler in later ones. I think that the standard practice in cases like this is to use current terminology with notes as well (but I'm not completely sure). VioletPumpkin (talk) 17:44, 28 June 2016 (UTC)
