Talk:List of Pokémon with unique type combinations: Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
No edit summary
Line 16: Line 16:
:You missed the Nidos♥ Otherwise, no comment--[[Blastoise (Pokémon)|<font color="green">K</font>]][[Gary's Blastoise|<font color="green">kl</font>]][[Blastoise (TCG)|<font color="black">l</font>]][[User:Kkllnn|<font color="pink">nn</font>]] <small>[[User Talk:Kkllnn| blastoise]]</small> 20:24, 19 October 2008 (UTC)
:You missed the Nidos♥ Otherwise, no comment--[[Blastoise (Pokémon)|<font color="green">K</font>]][[Gary's Blastoise|<font color="green">kl</font>]][[Blastoise (TCG)|<font color="black">l</font>]][[User:Kkllnn|<font color="pink">nn</font>]] <small>[[User Talk:Kkllnn| blastoise]]</small> 20:24, 19 October 2008 (UTC)
::I agree, Solrock/Lunatone and Latios/Latias and the Nidos shouldn't be considered families, since they don't evolve from or to each other. Maybe there should be a section for unique counterpart groups? Although, then you have the issue whether there are other counterparts (like seviper/zangoose) that could/should be included. It might be best if they're just removed. :-/ [[User:Jazzmoth|Jazzmoth]] 18:58, 25 December 2008 (UTC)
::I agree, Solrock/Lunatone and Latios/Latias and the Nidos shouldn't be considered families, since they don't evolve from or to each other. Maybe there should be a section for unique counterpart groups? Although, then you have the issue whether there are other counterparts (like seviper/zangoose) that could/should be included. It might be best if they're just removed. :-/ [[User:Jazzmoth|Jazzmoth]] 18:58, 25 December 2008 (UTC)
:::But wait-In the case of the Nidos, they are technically related, considering that , when Nidoran(F)(Can't make female sign) breeds, it could be either Nidoran, like how any multi-gendered pokemon breeds, it could be either gender. They're only separated by Gen I's lack of genders. Me and my fellow torchics agree on this - Sk8torchic 16:39, 22 February 2009 (UTC)

Revision as of 16:39, 22 February 2009

Should we list Pokémon here twice? Like Surksit would be both under "Bug" and "Water"? Or would that be a bad idea? --Someone Else 11:36, 23 March 2008 (UTC)

I think it should be listed only under its first type (Such as Bug with Surskit..) but that's just me. Tina δ281 15:46, 23 March 2008 (UTC}


Question

Is Aron not there because there is already a Rock/Steel type?? And is rhyhorn not listed beciz there already is Rock/Ground?? I accidentally added rhyperior and others... like Aron and family is the only steel/rock... but beciz there is already rock/steel should it be added...?--Wowy 09:15, 16 September 2008 (UTC)


Families

Do solrock/lunatone and latias/latios really count as families? They aren't evolution families just counterparts. We wouldn't say that zangoose/seviper are the same family. Or the electabuzz and magmar lines seeing as how they are usually represented together (normally only available in oppositely paired games, recieved same evolutionary families in same generation) So shouldn't the solrock/lunatone and latias/latios be removed? TheAlmightyChris 20:20, 19 October 2008 (UTC)

You missed the Nidos♥ Otherwise, no comment--Kkllnn blastoise 20:24, 19 October 2008 (UTC)
I agree, Solrock/Lunatone and Latios/Latias and the Nidos shouldn't be considered families, since they don't evolve from or to each other. Maybe there should be a section for unique counterpart groups? Although, then you have the issue whether there are other counterparts (like seviper/zangoose) that could/should be included. It might be best if they're just removed. :-/ Jazzmoth 18:58, 25 December 2008 (UTC)
But wait-In the case of the Nidos, they are technically related, considering that , when Nidoran(F)(Can't make female sign) breeds, it could be either Nidoran, like how any multi-gendered pokemon breeds, it could be either gender. They're only separated by Gen I's lack of genders. Me and my fellow torchics agree on this - Sk8torchic 16:39, 22 February 2009 (UTC)