Talk:Swift (move): Difference between revisions
Happizelpom (talk | contribs) No edit summary |
(→Dive: Generation I and II: new section) |
||
| Line 10: | Line 10: | ||
well it cant hit whats not there there now can it? it means like as long as the opposing pokemon is on the field it will always hit even if it uses double team or smokescreen. [[User:Happizelpom|<span style="color:#FF7070">Happi</span>]][[User talk:Happizelpom|<span style="color:#FF8000">zel</span>]][[Special:Contributions/Happizelpom|<span style="color:#660099">pom</span>]] 23:11, 11 August 2008 (UTC)Happizelpom | well it cant hit whats not there there now can it? it means like as long as the opposing pokemon is on the field it will always hit even if it uses double team or smokescreen. [[User:Happizelpom|<span style="color:#FF7070">Happi</span>]][[User talk:Happizelpom|<span style="color:#FF8000">zel</span>]][[Special:Contributions/Happizelpom|<span style="color:#660099">pom</span>]] 23:11, 11 August 2008 (UTC)Happizelpom | ||
== Dive: Generation I and II == | |||
Dive does not exist in Generation I or II, so mentioning it in the description for the attack under those headings is inaccurate. | |||
Revision as of 14:08, 6 December 2008
Never misses?
Since the second or third generation swift has had the tendency to miss if the user digs or flies - it's happened a lot to me with swift and other unmissable attacks. It's happened in several of my games so it can't just be a fluke. --Woodland Mudkip ☆XXpx 14:45, 1 December 2007 (UTC)
Sorry, it already says this. It still seems like a false statement to say it never misses though--Woodland Mudkip ☆XXpx 14:48, 1 December 2007 (UTC)
For some reason, I am significantly contributing to Swift(move). Pikachu610
well it cant hit whats not there there now can it? it means like as long as the opposing pokemon is on the field it will always hit even if it uses double team or smokescreen. Happizelpom 23:11, 11 August 2008 (UTC)Happizelpom
Dive: Generation I and II
Dive does not exist in Generation I or II, so mentioning it in the description for the attack under those headings is inaccurate.
