Template talk:UniqueType

Pre-implementation opinions

Rotom

I like the way the forms are grouped together, but would it be possible to have Normal Rotom seperate from the other Electric/Ghost forms? The way it's shown now has all of the Electric/Ghost forms shown as being in Generation V. Vuvuzela2010 Δ 09:19, 6 November 2011 (UTC)

Is it good that way, or should I remove Normal Rotom from the form cluster? --SnorlaxMonster 09:35, 6 November 2011 (UTC)

It's good as it is, but if Normal Rotom can be removed from the cluster without any bad effect on the template, it would be better. Vuvuzela2010 Δ 09:47, 6 November 2011 (UTC)

It works fine, but my intention was for merged groups to be all forms, and unmerged groups to be indivdual forms, and removing Rotom would mess that up. --SnorlaxMonster 10:00, 6 November 2011 (UTC)

Lack of something I don't have a word for

Not a fan of this layout. For the pokémon who stop becoming uniquely typed, there's nothing here saying who edged them out. If I have to got to another page to be reminded that Nincada stopped being unique because of an alt form Wormadam, others will, too. In that regard, it's only half informative (since it's a matching point if you're going to mention former unique types). Having a way to column sift groups by generation would be nice, too, but that's just me. Luna Tiger * the Arc Toraph 13:04, 5 December 2011 (UTC)

Well, it is a lot better than the current layout. I really have no idea how we would list who knocks them off though. --SnorlaxMonster 16:26, 2 January 2012 (UTC)

Updating template

Three changes should be made to update this template.

1) In the header line that ends in | Generation, add one to the # in colspan="#".

2) After the last generation header (above </noinclude>|- style="text-align:center; background:#fff"), add a new header.

! style="background:#{{abcdefg color}}" | {{color2|fff|Generation MMMM|MMMM}}

• Replace abcdefg with the name of the new generation color (for example "kanto").
• Replace MMMM with the Roman numerals for the generation (for example, "I").

3) Above the first form line |-{{#if:{{{form2|}}}||style="display:none"}}, add the following code:

| style="background:#{{#ifeq: {{{####|no}}}|no|FFF|{{#if: {{{MMMM|}}}|{{galar color}}|{{abcdefg color light}}}}}}; color: #{{#if: {{{MMMM|}}}|0B9A0B|FFF}}" {{#if: {{{MMMM|}}}|width="20px"|width="40px" colspan="1"}} rowspan="{{{forms|1}}}" | '''{{#if: {{{MMMM|}}}|{{tt|{{color|{{abcdefg color dark}}|{{#ifeq: {{{####|}}}|no| |{{{####|}}}}}}}|MMMM}}|{{{####|}}}}}'''

• Replace #### with the next parameter (or the generation plus 5; for example, the parameter for generation IX (9) is "14").
• Replace MMMM with the Roman numerals for the generation (for example, "IX").
• Replace abcdefg with the name of the new generation color (for example "paldea").

(FYI, I'm putting this on the talk page so that when you copy code into the template, that code is the only place that ####, MMMM, and abcdefg should be found. If these instructions were in the noinclude part of the template, a find/replace would be complicated by the instructions themselves.)

Tiddlywinks (talk) 06:36, 22 November 2022 (UTC)