Bulbapedia - User contributions [en]

Talk:Tera Raid Battle

2023-03-20T01:35:02Z

Koetsu: /* Moves with different effects? */ new section

== Badges ==

In encounter section, are the 'Badges' Gym Badges or just any Badges? [[User:CrazyPikmin|CrazyPikmin]] ([[User talk:CrazyPikmin|talk]]) 09:29, 7 February 2023 (UTC)

I would assume gym badges, since those one control the level cap. [[User:Dot455|Dot455]] ([[User talk:Dot455|talk]]) 17:27, 7 February 2023 (UTC)

One thing that happened to me in my playthrough is that I didn't get 4 star raids until I had 7 gym badges, instead of the 6 listed on the page. --[[User:XarrotD|XarrotD]] ([[User talk:XarrotD|talk]]) 19:23, 9 March 2023 (UTC)

That can also be bad luck. Something else I saw was that the coloms for after 3 and after 6 are not 100% (20+40+30=90) (20+30+30=80). That also has to be completed. [[User:CrazyPikmin|Crazy]][[User talk:CrazyPikmin|Pikmin]] ([[Special: Contributions/CrazyPikmin|My Edits]]) 07:59, 10 March 2023 (UTC)

== Moves with different effects? ==

I noticed the move Ruination, which should be similar to Super Fang, only does a little damage in Tera Raid Battles. What is it doing instead? I see mention of some moves which behave differently but it seems there are more, such as these "cut HP in half" moves.
--[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 01:35, 20 March 2023 (UTC)

Talk:Repel

2022-01-04T05:44:07Z

Koetsu: /* Repel for Trainers */

==Cleanse Tag doesn't do what it should==
"Prevents Pokémon with a lower level than the holder from appearing if the holder is first member in the player's party." That's the listed effect. However, being in an article about Repel, it doesn't repel Pokémon as it should! I'm sick of walking through grass with my '''Level 68''' Typlosion and get attacked by lower levels while it is holding the Cleanse Tag. I'd like to take it out; however, I doubt myself, so I want others to try it out, too. [[User:Link of Hyrule|I LOVE ZELDA, TOO. (Link of Hyrule)]] 17:31, 27 May 2010 (UTC)
:It merely lowers the encounter rate, as opposed to eliminating wild encounters altogether like a Repel would. I'm not sure by how much, though. ▫▫'''[[User:Tina|ティナ]]'''[[User talk:Tina|♫]][[Special:Contributions/Tina|★]] 17:50, 27 May 2010 (UTC)
::I agree. Putting the Cleanse Tag here is like putting the [[Poké Flute]] on the [[Flute]] page; it's similar, but this should be about the sprays, not anything which lowers wild encounter rates (or we may as well put the Black Flute here too). --[[User:SnorlaxMonster|'''Snorlax''']][[User talk:SnorlaxMonster|'''Monster''']] 07:00, 19 March 2011 (UTC)

== Blaclk & White Glitch? ==

Sometimes, if you use a Repel before entering a room it wont repell Pokemon, but until it wears off you cannot use another Repel, has this happened to anyone else? Or are there places where the repels don't work? For me its happened in Giant Hole (cave) and Mistralton Cave (bit before Cobalion), to name a couple. '''X'''[[User:Vuvuzela2010|'''Vuvuzela2010''']]'''X''' 15:54, 3 May 2011 (UTC)
:If your lead Pokémon is an equal or lower level than the wild Pokémon in the area, wild Pokémon can still appear. You sure it's not that? [[User:Blazios|Blazios]] 15:58, 3 May 2011 (UTC)
::I actually had no idea about that. So, since I was trying to level-up weaker Pokemon, yes, that's obviously whats happened. '''X'''[[User:Vuvuzela2010|'''Vuvuzela2010''']]'''X''' 20:23, 3 May 2011 (UTC)

== Scott from Battle Frontier ==

I saw Scott from Batlle Frontier show a repel in the anime on the episode Sceptile began to obey Ash in order to avoid Beedrils, i think we should post an image from that-- Posted By Robin Maximo[[User:Robin Maximo|Robin Maximo]] ([[User talk:Robin Maximo|talk]]) 14:53, 19 June 2016 (UTC) 14:52, 19 June 2016 (UTC)

== Repel for Trainers ==

Repel works to avoid trainer battles? Since when has this been a thing? Here's a clip of Repel avoiding a trainer battle in Pokemon Brilliant Diamond.
https://streamable.com/1kq0q6
[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 04:26, 1 January 2022 (UTC)
:I cannot replicate this behavior (with other Trainers). [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 14:54, 2 January 2022 (UTC)
::I couldn't either with another trainer I forgot to battle on a different route. I wonder if it was a bug that was since patched out? That recording was taken before the most recent update as of now. [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 00:51, 3 January 2022 (UTC)
:::In BDSP, I noticed that the positions of both the Trainer and the NPC (if it's moving) seem to be adjusted after the battle to the centers of the tiles they were positioned on. (Which has the odd side-effect of sometimes having to walk towards NPCs directly after the battle in order to talk to them again.)
:::In [https://www.youtube.com/watch?v=w-0BcOgEVqo this playthrough video], at around 13:30, the battle is initiated after the Trainer sees the player, when the player walks in from the left. After the battle, you can see that it is only triggered on the rightmost of the three tiles in that path.
:::In the streamable video, the player walks in the middle of the path. We just established that that's not in range, that it won't trigger the battle.
:::When the battle finally is triggered secodns later, I assume the player still technically is on the tile top-left of the NPC (not directly left of him). Too bad it cuts off before the end of the battle.
:::Anyway, this should be independent of Repel. [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 19:53, 3 January 2022 (UTC)
::::Going by that playthrough video actually, it seems you can't not be within range of the Psychic up ahead. I have another clip that happens after the first clip that shows once again the player passing by the trainer undetected, even while being in range. No exclamation mark appears, meaning the battle had to be manually initiated. https://streamable.com/v8hjrk. Does this prove it any more than the other? I wish it was just possible to retry it on this route on the same update of the game. [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 05:44, 4 January 2022 (UTC)

Talk:Repel

2022-01-03T00:51:17Z

Koetsu: /* Repel for Trainers */

Talk:Repel

2022-01-01T04:26:40Z

Koetsu: /* Repel for Trainers */ new section

Talk:Catch rate

2020-08-27T05:00:29Z

Koetsu: /* Catch rate for Gen 8 */

==Untitled==
The computer science term for "Floor" is, in fact, "int(", which simply truncates the number. "round(" would make a value like 6.9 become 7; "int(" would make it 6. I believe Zhen is correct in this case. ~Evan
:What was that in reference to? - Jshadias
::Zhen's edit and your subsequent reversion, if I read the history right. ~Evan
:::He was just editing it to make it consistent with my other changes. In any case, the after revision is the right-side column. In any case, trunc() and floor() are the same, but int() is ambiguous. It simply means conversion to integer, which could be rounding or truncating. Wish I could get TeX-rendering working... - [[User:Zhen Lin|刘 (劉) 振霖]] 09:40, 12 Feb 2005 (GMT)

== Is this formula accurate? ==

When using the formula

Chance = floor (((( TotalHP * 4 ) - ( CurrentHP * 2 )) * CatchRate ) / TotalHP ) + Status + 1

with Pokémon with high catch rates (ex. Pidgey and Rattata), the formula says that there should be about a 200% chance to catch a Pidgey at 100% HP. But there isn't a 200% chance or even a 100% chance. I caught 5 Pokémon on Route 1 of FireRed without weakening any of them and I used 15 Pokéballs. Despite the sample size, the fact that the Pokémon escaped even once is enough to raise concern about the formula. Any other thoughts on the matter? -Wild Eep

:Experimental data isn't the same as theoretical results. But then again, methinks you might be misinterpreting the results of using this formula. The formula does not return a percentage, it returns a number, and in order to capture a Pokémon, the randomly generated number between 0 and 255 (or possibly a higher number than that, say, 511) has to be below the number you obtain from this formula. But I'm not the game mechanics expert. - [[User:Zhen Lin|振霖]][[User talk:Zhen Lin|T]] 02:16, 25 November 2005 (CST)

Hmm. . . using the formula for any pokémon at any level with full HP and no status ailments with a catch rate of 255 gives an output of 511. Every site I could find has the exact same formula, and they all say the random number is between 0-255. Those that site sources site [[user:Meowth346|Meowth346]] as their source, so maybe he knows, or can find out. [[User:Slim|Slim]] 15:54, 29 November 2005 (CST)

:Indeed, there seems to be something off with either this formula or the listed CatchRates. Trying to catch a Pokemon simply by chucking a normal Pokeball at it (that is, no damage done, no status changes) simplifies as so:

:Chance = floor (Poké Ball * (((( TotalHP * 4 ) - ( CurrentHP * 2 )) * CatchRate ) / TotalHP ) + Status + 1)

:Chance = floor (1 * (((( TotalHP * 4 ) - ( TotalHP * 2 )) * CatchRate ) / TotalHP ) + 0 + 1)

:Chance = floor ((( TotalHP * 2 * CatchRate ) / TotalHP ) + 1)

:Chance = floor (( 2 * CatchRate ) + 1)

:For any CatchRate of 128 or higher, Chance is at least 257. The random number between 0 and 255 this is compared to will always be less than this, and as a result any Pokemon with a CatchRate of 128 or higher should always be caught simply by chucking a Pokeball at it. Yet this does not seem to be the case -- you can't always catch an Abra this way, despite them having a CatchRate of 200. This should give them a Chance of 401, and thus a 100% catch rate. [[User:Wild Eep|Wild Eep]] and [[User:Slim|Slim]] seem to have noticed the same thing. [[User:Opaopa13|Opaopa13]] 05:12, 27 April 2007 (UTC)

::I just noticed something -- note the following line in the article:
:::'''CurrentHP''' is either the wild Pokémon's current HP, or if its current HP is greater than 255, use ''floor ( '''CurrentHP''' / 4)''.
::It doesn't make sense to simply replace '''CurrentHP''' with ''floor ( '''CurrentHP''' / 4)'' -- that would make for a very strange function, where a Pokemon with 256 HP would be easier to catch than one with 68. Replacing all of ''('''CurrentHP''' * 2 )'' just makes the problem worse. This suggests a typographical error somewhere in either the formula or its explanation.

::I had a hunch, and replaced ''(( '''TotalHP''' * 4 ) - ( '''CurrentHP''' * 2 ))'' with ''(( '''TotalHP''' / 4 ) - ( '''CurrentHP''' / 2 ))''. Unfortunately, that's not right either -- according to that forumla, a Pokemon above 50% health will have a negative Chance value and thus can NEVER be caught. We know that is not the case. However, I suspect something along those lines is the solution. Perhaps one of those multiplications is supposed to be a division instead. Is there any healthy chunk of experimental data to look at? [[User:Opaopa13|Opaopa13]] 05:24, 28 April 2007 (UTC)

The sensible thing to do is to ask someone who knows how to use a debugger/disassembler to investigate this. Unfortunately, the only person I know who can do this is pika. - [[User:Zhen Lin|振霖]][[User talk:Zhen Lin|T]] 06:57, 28 April 2007 (UTC)

Examining an emulated copy of Pokemon Red, I did, indeed, find it impossible to NOT catch any Rattata or Pidgey I threw a Pokeball at. I was more than ready to believe this formula were true. But, as Opaopa13 said, we know it isn't, because anyone who has played the Red or Blue versions knows Abra is not so easy to catch.

Interestingly, I tried the same thing on a Pidgey in an emulated copy of the Gold version (throwing a ball at it when it was at full health), and failed to capture it until my third try.

I JUST DON'T KNOW WHAT TO BELIEVE! - Pineapple

:It would be easy to explain this if Abra's catch rate was just wrong, but the catch rates must have been data-mined, so that's out. Allow me to be completely speculative here, but perhaps it's something like a rare few Pokemon having an additional chance to escape capture? Or certain catch rates that are influenced by what badges you have? It would be odd to have something like that when the programmers could just alter something's catch rate instead, though...

:Well, we _know_ we get the wrong results for Abra. I'm guessing there was some minor typo somewhere, or else some minor modifier to the formula we aren't aware of.

:On a side-note, I'm still really confused by the "if CurrentHP > 256, use (CurrentHP / 4) instead" thing. I just can't imagine any reason, technical or modelling-wise, where "use CurrentHP = 255" doesn't work just as well or better. Or at least divide by 2! (Pokemon HP never exceeds 1024, right? Thinking in terms of the number of bits it takes to represent these numbers...). [[User:Opaopa13|Opaopa13]] 19:22, 7 May 2007 (UTC)

I think, we should just remove the formula from the page until we can get some authoritative analysis, or otherwise from experimental data. - [[User:Zhen Lin|振霖]][[User talk:Zhen Lin|T]] 06:17, 8 May 2007 (UTC)

I strongly suspect that the only problem with the formula on the site is the 2. I know that's how the old equation simplifies, so the original was probably off as well. 1+INT(B*(2-P)*C+S) makes perfect sense. Then a Pidgey or other Pokemon with a catch rate of 255 is guaranteed to be caught, since at full health and no ailments, you get 256. Any number from 0-255 will be lower than that, so you'll always catch it. On the other hand, a legendary Pokemon with 1/10th of its health left, paralyzed, with an ultra ball thrown an it, is 1+INT(2*1.9*3+5), or 17. 17/256 (since it's a less than roll, not less than or equal to) is about 6.6% (1 in 15). That seems about right, given that it's taken an average of 15-20 ultra balls for me to catch most of the legendaries. The current formula says it would be 28/256, or 10.9% (about 1 in 9), which is definitely not right. Easiest way to test would be to repeatedly try catching something with a catch rate around 120, using a standard ball, and see if it happens about half the time. [[User:Arrkhal|Arrkhal]] 03:50, 20 May 2007 (UTC)

== The correct formula ==

Apparently someone at Smogon found an extremely complex formula on a Japanese website. A good friend of mine simplified it and it seems to be 100% Accurate:

( ( 1 - CurHP * 2 / ( MaxHP * 3 ) ) * Catch * Ball * Status ) / 256

Status:
*1 for Normal
*1.5 for Poisoned, Paralyzed, or Burned
*2 for Asleep or Frozen

Examples:
*A level 2 Rattata, with 13/13 HP, catch rate 255, using a Pokeball. No status effects.
**( ( 1 - 13 * 2 / ( 13 * 3 ) ) * 255 * 1 * 1 ) / 256
**= 0.33203125
**~ 33%
*A level 70 Regigigas, with 1/234 HP, frozen, catch rate 3, using a Dusk ball.
**( ( 1 - 1 * 2 / ( 234 * 3 ) ) * 3 * 4 * 2 ) / 256
**= 0.093482906
**~ 9%

[[User:DanPMK|MK]] 05:51, 20 May 2007 (UTC)
:This does appear to be more reasonable, however, I would like to see this so-called "extremely complex" formula. There may be some rounding going on which affects the precision of the results. - [[User:Zhen Lin|振霖]][[User talk:Zhen Lin|T]] 12:05, 22 May 2007 (UTC)
::The original site had gone down, but thank god for Google cache. [http://209.85.165.104/search?q=cache:2tdg8lVDQ8wJ:no2.pic.bz/document/ball.html+http://no2.pic.bz/document/ball.html&hl=en&ct=clnk&cd=1&gl=us Here]. It appears my friend was a bit exaggerating when he said complex; it's actually just a tad redundant. He reduced it to a simpler form is all. Cheers. [[User:DanPMK|MK]] 08:04, 1 June 2007 (UTC)
:::As I suspected, there is more to it. It seems that the formula result is interpreted in two different ways depending on what the value is. - [[User:Zhen Lin|振霖]][[User talk:Zhen Lin|T]] 12:25, 1 June 2007 (UTC)

== Formula is nowhere near correct ==

I just tried catching a Lv. 13 Feebas at full health (30 HP). I threw three dusk balls at it (while in the cavern, of course), and they all broke. On the fourth try I was able to catch it. It has a catch rate of 255, so according to this formula I have maybe a 400% chance of catching it at full health. Even going by the catch rate alone, I should have had a 100% chance of catching it. This wasn't an atypical situation either. I tried catching a few more before and after this one, and I generally wasn't able to capture them until I weakened them (I caught maybe one or two without hurting it). Once I threw an ultra ball at one, and it immediately broke. I think the pokemon's HP ratio definitely has a lot more to do with catching it than what this formula suggests.

If there are any sources on that other function that someone submitted in here (I don't know how to reply to comments, sorry :<), then that would be really nice. But I tried that equation on the above-mentioned feebas and got (1-(30*2)/(30*3))*255*4*1)/256 (the pokeball page on here says that the dusk ball is 4x in caverns, and Wikipedia says it's twice as good as an ultraball, so I'm going with 4x), which equals 340/256, or 1.328125. This is still above a 100% catch rate on something that seemed like it was maybe 50%. Even going with the assumption that the dusk ball is only 3x better than a pokeball, I still got 255/256, which awfully close to 100%. So unless the dusk ball didn't have its 3x/4x effect (maybe from me fishing in the cavern instead of walking in the cavern?), I don't think this function is true either.

--[[User:Stele007|Stele007]] 18:59, 21 May 2007 (UTC)
:Were you surfing by any chance? There has to be some way to explain this. Feebas is extremely easy to capture regardless. My friend caught several using Quick balls (4x for the first 5 turns) immediately at the start of battle and none of them missed. If you were, perhaps the Dusk balls did not work because of surfing. I know they do work while fishing... [[User:DanPMK|MK]] 06:25, 22 May 2007 (UTC)
:And by several I mean over a dozen. [[User:DanPMK|MK]] 06:28, 22 May 2007 (UTC)

==Safari Zone==

There's something I'd like to ask. In the [[Safari Zone]], you can throw bait and mud in [[Generation IV]]. These are said to make Pokémon easier to catch. However, does anybody know of how EXACTLY do they change the catch rate (Or make them easier to catch somehow)? Thank you. - [[User:JMS|JMS]] 21:27, 22 December 2007 (UTC)
:Actually, I think they alter the percent chance that the Pokémon'll run for it/accuracy of the ball. '''[[User:TTEchidna|''TTE'']][[User talk:TTEchidna|chidna]][[User:TTEchidna/GSDS|GSDS!]]''' 22:53, 22 December 2007 (UTC)

::Actually, the equation is posted on the Japanese wikipage for Capture Rate:
::Solve for S (S = Safari)

::S=(Capture Rate×100)÷1275×Rock Compensation÷Food Compensation

::Rock Compensation = Times rock/mud is thrown at Pokémon × 2
::Food Compensation = Times food is thrown at Pokémon × 2

::Then solve for a, which is a special equation for this time around:

::a=(S×1275)÷100

::Just keep in mind that the more mud/rocks you throw, the easier it is to capture, but the easier it is to run away. The more food you throw, the harder it is to capture but it'll stay around longer. - [[User:Gimmetokyo|GimmeTOKYO]]

== Trivia... ==

''The appearances of Pokémon such as Nosepass, Tropius, Carnivine, etc., would suggest that their catch rate is low.''
What the hell?!?!? '''{{Colored link|:User:Origamiguy|ff8000|Lord}} of {{Colored link|:User_talk:Origamiguy|ff8000|Ori}}{{Colored link|Special:Contributions/Origamiguy|ff8000|gami}}''' 18:44, 24 June 2008 (UTC)

:Yeah... I don't know what that means, either. ~[[User:SaturnYoshi|'''$aturn''']][[User:SaturnYoshi|'''¥oshi''']] [[User talk:SaturnYoshi|THE VOICES]] 18:49, 24 June 2008 (UTC)

::remove it because it makes no sense? i had thought dialga had a low catch rate when i got the game, and it turns out to be 30, quite high for a legendary... '''{{Colored link|:User:Origamiguy|ff8000|Lord}} of {{Colored link|:User_talk:Origamiguy|ff8000|Ori}}{{Colored link|Special:Contributions/Origamiguy|ff8000|gami}}''' 18:50, 24 June 2008 (UTC)
:::I know what it's saying: They look like the kind of Pokémon that would have a lower catch rate than they actually do. That's still based on the player's conjecture and probably not worth noting. --[[User:Fabu-Vinny|FabuVinny]] |[[User talk:Fabu-Vinny|Talk Page]]| 18:54, 24 June 2008 (UTC)

What I believe it was saying is that the rarity of these pokémon would suggest they have a low catch rate, just like one of a kind pokémon do. However, they actually have quite high catch rates. Does this seem right? [[User:Da Rammo|Da Rammo]] 06:34, 22 April 2009 (UTC)

: I put a note in the lede to try to address this last interpretation. [[User:AySz88|AySz88]] 11:50, 24 December 2009 (UTC)

== Easier explanation? ==

I think there should be an easier explanation included in this article, something of a tl;dr section. To me, this is all mathematical mumbo-jumbo, and I commonly fail anything and everything algebraic. I could honestly care less how the game determines how a pokemon is caught, I just know that I need to lower the HP of the wild Pokémon and possibly inflict a status problem on it to catch it. Also, on major thing that's missing from the article is it doesn't explain if a higher number for a catch rate is better or worse. It may be a dumb question to ask (but I don't honestly get it, either) but you quite often have to write for the five-year-old poké-tards that will be here.
:Higher number for catch rate increases likelihood of capture. It's why Mewtwo's is 3. '''[[User:TTEchidna|''TTE'']][[User talk:TTEchidna|chidna]]''' 04:39, 28 June 2008 (UTC)

My brain hurts... too much math... [[User:Diachronos|Diachronos]] 16:55, 1 October 2008 (UTC)

Will you please make this article in a way that actually makes sense? It tells me nothing helpful. [[User:Alakazam 2|Alakazam 2]]
:I agree, a simplified, even if less informative, version of this article would probably be more helpful to a lot more users.[[User:Gastly's mama|Gastly's mama]] 15:36, 7 December 2008 (UTC)

: I tried to write a more accessible way to interpret the formula. Also see Reworking the ''a'' term below.... [[User:AySz88|AySz88]] 11:51, 24 December 2009 (UTC)

== CatchRate Calculator ==

I have written a small catch-rate calculator program. You put in details of the opponent's HP,Max HP, Base CatchRate,status ailment, and choose which ball you are using (along with ball-specific factors), and it tells you the chances of catching the pokemon. Should i include a link on the page? '''{{Colored link|:User:Origamiguy|f80|Lord}} of {{Colored link|:User_talk:Origamiguy|f80|Ori}}{{Colored link|User:Origamiguy/Mudkipz|08f|gami}}''' 12:06, 10 January 2009 (UTC)
:I think so. Where does all this come from anyways? O_O [[User:Sivart345|--Sivart]][[User talk:Sivart345|3]][[Special:Contributions/Sivart345|4]][[User:Firestorm|'''5''']] 01:58, 27 March 2009 (UTC)

== Heavy Ball ==

How does it work into the formula if the ball bonus adds instead of multiplying? Does it add before or after the status bonus? --[[User:Kaoz|Kaoz]] 16:29, 28 September 2009 (UTC)
:Order of operations. Multiplication first. [[User:Ht14|'''''ht''''']][[User talk:Ht14|''14'']] 16:42, 28 September 2009 (UTC)
::Are you sure? Because if it works just like I think you're saying, you just replace the Ball Multiplier with a flat "+30" rate (or whatever technically applies). I calculated the catch rate of Groudon using a Heavy Ball VS a Great Ball, and the Great Ball outperformed the specialty Poké Ball. If that's the case, Heavy Balls are pretty useless.--[[User:Purimpopoie|Purimpopoie]] 13:33, 18 October 2009 (UTC)
:: I doubt that "order of operations" applies here; it's relatively easy to just apply the +30 before the multiplications coding-wise (much like using parenthesis). One would need to look at the game code somehow, probably, to see for certain. [[User:AySz88|AySz88]] 12:07, 24 December 2009 (UTC)

== Luxury or Friendly? ==

Which is more effective? [[User:Ht14|'''''ht''''']][[User talk:Ht14|''14'']] 01:05, 29 September 2009 (UTC)
:it depends, i know squat about the catch rate, but i do know the luxury ball increases how fast the pokemon's friendship raises while the friendly(?) ball gives an immediate boost... by how much i'm not quite sure. - [[User:Geomexis|Geomexis]] 12:59, 18 January 2010 (UTC)
::Luxury Balls increase the rate at which your pokemon becomes friendly from actions as outlined in the [[Happiness]] article. Friend Balls automatically set the pokemon's happiness to 200 (instead of the usual 70) when caught. Both poke balls have a catch rate of 1x. Max happiness is 255 and happiness-based evolutions happen at 220+ so usually the Friend Ball will get you there quickly for cheap. ~[[User:mjblink|mjblink]]{{Unsigned|mjblink}}

== Reworking the ''a'' term ==

In every location in this article that I can tell, it would be clearer if ''a'' were already divided by 255, i.e. substituting ''a''/255 = ''a''/(2^8 - 1) in each formula with a new variable. (Even that odd-looking 16711680 is 255 * 65536 .) Then ''a'' simply becomes equal to the approximation to ''p'' and there is an obvious intuitive meaning to it. I used this idea in the new lede, and it'd probably be clearer to do this in the rest of the article as well.

Is there some reason why ''a'' was defined this way that I don't know of? [[User:AySz88|AySz88]] 11:39, 24 December 2009 (UTC)

== Trivia on HP ==

There's a bit in the "Trivia" section about high-HP Pokémon being easier to catch at 1 HP than lower-HP ones. This is true, but it also states that "Pokémon with higher HP stats (such as Chansey) are easier to capture when their HP is reduced, despite low catch rates compared to others." But there isn't a big-enough effect to overwhelm the catch rate except at very very low HP levels. The equation in the current article can be reorganized this way:
a = catch_rate * ball_bonus * status_bonus * (1 - 2/3 * (currentHP / maxHP) )
And at 1 HP:
a = catch_rate * ball_bonus * status_bonus * (1 - 2/(3 * maxHP))
And comparing the HP penalties at 1 HP:
* 10 HP max: 1 - 2/(3 * 10) = 1 - 2/30 = 6.7% penalty (i.e. 0.933x)
* 20 HP max: 1 - 2/(3 * 20) = 1 - 2/60 = 3.3% penalty
* 100HP max: 1 - 2/(3 * 100) = 1 - 2/300 = 0.66% penalty
* 200HP max: 1 - 2/(3 * 200) = 1 - 2/600 = 0.33% penalty
... Once you get past 20ish HP, shaving off bits of that last 3% of (multiplicative) penalty is pretty negligible, equivalent to around 7 points of catch rate at most (3% of 255). [[User:AySz88|AySz88]] 10:40, 25 December 2009 (UTC)

== Generation I? ==

In Generation I, the mechanisms are somewhat different. For example, the number of shakes doesn't seem to be determined randomly and a Poké Ball can even entirely miss a target. Do the Gen. I games also use a completely different formula or does it work the same way as currently described in the article? {{unsigned|Socob}}
:The formula is definitely different in Generation I - I think Pokémon with very high catch rate (like Pidgey) were more difficult to catch, and Pokémon with very low catch rate (like Articuno) were easier to catch. By the way, the number of shakes has not been determined randomly since at least the beginning of Generation IV. [[User:Ultraflame|Ultraflame]] 16:06, 16 May 2010 (UTC)
::I thought so. It would be nice if we had some information about this, but I don't think that's very easy to get. About the shaking - I'm not sure if that's also what you meant, but what I was referring to by "not randomly" in Generation I is that a Ball will always shake the same amount of times on a Pokémon as long as you don't change its HP/status condition (unless it's caught). -- [[User:Socob|Socob]] ( [[User_talk:Socob|Talk]] | [[Special:Contributions/Socob|Contribs]] ) 10:22, 21 May 2010 (UTC)
:::Actually, I just thought of this: You can try asking Pokémon ROM hacking communities about Generation I catch rate mechanics. [http://www.pokecommunity.com The PokéCommunity] is one of the few Pokémon sites that has a dedicated sub-forum for ROM hacking discussion. [[User:Ultraflame|Ultraflame]] 19:32, 21 May 2010 (UTC)
:I have put up a complete analysis of the R/B/Y capture algorithm on [http://www.dragonflycave.com/rbycapture.aspx my website], based on the actual code. Something about it should at least probably be included on the page. [[User:Dragonfree|Dragonfree]] 09:00, 25 February 2011 (UTC)

== Trivia ==
Somewhere else on this site, I read that the lowest possible catch rate is 3 since if it were any lower, the Master ball would have a chance of failing. http://bulbapedia.bulbagarden.net/wiki/List_of_Pokemon_by_catch_rate#Trivia [[User:KurosakisTwin|KurosakisTwin]] 17:22, 5 August 2010 (UTC)
:False. The Master Ball bypasses the formula entirely, so even if the catch rate were 0, the it would still catch the Pokémon. --[[User:A magical me|a_magical_me]] 23:09, 5 August 2010 (UTC)
::How do you know that? As far as I know, the Master Ball simply uses a value of 255 for the 'BonusBall' variable in the formula.
::With this, if all the other factors in the formula multiplied would result in a number less than one, 'a' would be less than 255 and thus, the Pokémon would have a chance of escaping. Quoting from the article, "The minimum value for 'a' (for a Pokémon with full health) would be ⅓ × catch rate." Since the result of the formula without the BonusBall component has to be at least one for the Master Ball to work reliably, this means that the catch rate must at least be 3 (as ⅓ × 3 = 1).
::This seems to be reasonable evidence to me as to why we've never seen catch rates lower than 3. -- [[User:Socob|Socob]] ( [[User_talk:Socob|Talk]] | [[Special:Contributions/Socob|Contribs]] ) 12:29, 7 August 2010 (UTC)
:::Also, I'm pretty sure that the game wouldn't make an exception for the master ball. That would result in a lot more code, and therefore it's just easier to not make more code and make the lowest catch rate 3 so that the Master Ball can catch anything. [[User:KurosakisTwin|KurosakisTwin]] 09:01, 11 August 2010 (UTC)
::::Socob, I know because it's what [http://upokecenter.com/games/rs/guides/catchrate.php UPC says] and it's what [http://no2.pic.bz/document/ball.html the reference] in [[Catch rate#References|the article]] says. Also because I have read the relevant code in both Diamond and HeartGold, and I can tell you that the Master Ball is simply not implemented in the way you suggest.
:::: KurosakisTwin, it does not require "a lot more code", just a couple lines—a small <code>if</code> statement—and is what any sane programmer would do.
:::: And here is something to think about: the lowest catch rate has been 3 since the beginning, way back in Red and Blue, when a [http://upokecenter.com/games/rby/guides/catchrate.php completely different algorithm] was used. --[[User:A magical me|a_magical_me]] 07:33, 21 August 2010 (UTC)
:::::Even UPC and the reference have their sources (which might be false), and even if they aren't, no matter how it's actually calculated in the games' codes, the Master Ball works without fail, so the statements on UPC don't necessarily indicate the actual calculations.
:::::Still, if you have viewed the code as you say, there's not much I can argue against that. All of what I've said above was, of course, simply evidence that pointed in the direction of a Master Ball with a value of 255. Naturally, the catch rates of 3 might be there to prevent "a" from being below 1 for entirely different reasons. If "a" is actually rounded down to an integer (which is actually stated in the article), then it would have to be at least 1 for the formula to work. However, this seems strange considering your last statement about the algorithm in Generation I. I haven't looked at it closely, but I guess it also needed catch rates of at least 3. I wonder, though, why the developers would go through the trouble of changing the algorithm, but leaving in the necessity of those catch rates of three or higher.
:::::Long story short: You looked at the code, I didn't, so you're probably right. -- [[User:Socob|Socob]] ( [[User_talk:Socob|Talk]] | [[Special:Contributions/Socob|Contribs]] ) 15:28, 24 August 2010 (UTC)
== Critical Capture ==
Should we write about critical capture, of black and white, here?--[[User:Kantenoh|Kantenoh]] 21:56, 18 December 2010 (UTC)

I belive from what i've read and when it happened to me,that there's a not so small chance (I don't know how high), that the pokeball will, when thrown, let out a woosh (a higher pitched on than normaly), absorb a pokemon, let out a metalic sound (ping a little like its captured), shake(a fast shake not a roll) in mid-air, fall down like usualy, then shake only once (not 3 times like usually), and have because of that idk probably about 3 times the capture ratio i suppose.
[[User:Codebracker|Codebracker]]

== Trainer pokemon level ==

I've been thinking about it for quite some time now, but pokemon are easier to capture depending on the level of the pokemon you battle it with.

I tried to catch a pokemon with a lv.5 and lv.8 pokemon and i couldn't catch it with ultraballs in 5 tries, than i swaped it for lv.75 pokemon and it worked on first try.

So could the level of the trainer's pokemon also apply somewhere in the formula?
[[User:Codebracker|Codebracker]]

:5 tries is not NEARLY enough trials to draw any kind of conclusion from. If you really want to test this, you're going to have to set up a comprehensive experiment and run it thousands of times. Alternatively, someone who has read the source code can tell you for sure. --[[User:Toksyuryel|Toksyuryel]] 04:40, 9 January 2011 (UTC)
::I haven't read the code, but the people who wrote this article have. The only time your Pokémon's level is factored in is when you are using a [[Level Ball]]. This was actually recently brought up on the forums. --[[User:SnorlaxMonster|'''Snorlax''']][[User talk:SnorlaxMonster|'''Monster''']] 04:41, 9 January 2011 (UTC)

== Critical Capture Rate ==

What is the rate of a Critical Capture in Generation V? --[[User:Nathan2055|Nathan2055]][[User Talk:Nathan2055|talk]] 21:22, 27 February 2011 (UTC)
That's what I want to know in Gen 6.--[[User:Hydreigonfan1|Hydreigonfan1]] ([[User talk:Hydreigonfan1|talk]]) 14:02, 19 December 2013 (UTC)

== High or low? ==

It should say in the very beginning whether a high or low number makes it easier/harder for a Pokémon to catch. I don't even think it's ever in the article. - [[User:Colorshade|Colorshade]] 22:20, 13 April 2011 (UTC)
: Good suggestion; I've added that. :) [[User:AySz88|AySz88]] 17:29, 18 May 2011 (UTC)

== Critical capture ambiguity ==

In the Critical Capture section right now, it says "A random number is generated, and if it is less than the modified value, a critical capture occurs." But what range is the random number in? [[User:AySz88|AySz88]] 20:38, 18 May 2011 (UTC)
:It seems sensible for the range to be 0 to 255 inclusive, since that is the base of the modified value. [[User:Naokohiro|Naokohiro]] 23:54, 7 May 2012 (UTC)

== Catch chance ==
Can anybody tell me whether the chance to catch a Pokémon in Generation I is equal to them in Generation II (and the others) or the chance is different? E.g. I throw an ordinary ball to a full-healthy Weedle. Is the chance to catch it in all generations identically (according to [[Weedle]] 33,3%) despite the fact the capture methods are different? I'm sorry again for my bad English! --[[User:LaBumm|LaBumm]] 04:29, 24 September 2011 (UTC)

== Doubt Generation III Algorithm ==
I'm starting to doubt the generation III algorithm. These are my findings in FireRed. I calculated for a paralyzed lvl 50 Moltres at 1 HP (exactly 1 HP due to endure) with a maximum HPmax of 165 (courtesy of Pokemon.Marriland.com) and a capture rate of 3 with an Ultra Ball. 
A = (3x165-2x1)x3x2/3/156x1.5 = 8 (rounded down) 
B = (2^16-1)xA^(1/4)/(255)^(1/4) = 27581 (rounded down) 
This gives a success rate of: 
(27581 / 65535)^4 = 0.031 (rounded down) or 3.1% 
At the moment I have thrown 400 (FOUR HUNDRED!) Ultra Balls, and still not captured it. 
The chance of that happening would be (1-0.031)^400 = 0.000002902 or 1:344550 
Please tell me I made a mistake in my calculation. It lies rather far outside the normal 0.05 error margin for experimental testing of hypotheses. 
I redid the same sort of testing for Zapdos, I didn't calculate my exact chances, this time I didn't manage to catch it in 200 tries. 
[[User:Ghostbird|Ghostbird]] 00:11, 25 November 2011 (UTC) EDITED: [[User:Ghostbird|Ghostbird]] 12:41, 28 November 2011 (UTC)

I retried catching Moltres and this time I caught it after 15-20 tries. (I wasn't counting) 
The only differences I knew of:
* I had defeated team rocket in Saffron and Giovanni in Viridian's gym.
* I was facing it with a pokémon over lvl 50. (However I caught Articuno using a lvl 30-ish pokemon)
* It was at more than 1 HP (he had a two pixel health bar).

I retried catching Zapdos and this time I did 200 fruitless tries. I noticed that though it had very little health left, it almost always broke free at the first check. 
Something that you should know:
* I've been using a state reload system to quickly retry catching when the capture failed. (Otherwise these capture tests, which require as much attempts as possible, are infeasible.)

I managed to Capture Zapdos on try 41 after reloading the original save (not a state save), (re)initiating combat and then using the reload state method. This time it generally broke free much later, often passing two shake checks and only breaking free at the last check, until I captured it. 

Hypothesis:
* There's something that influences catch rate, which kicks in before you are at the [Use|Cancel] screen after selecting the capture device (Ultra Ball). 
[[User:Ghostbird|Ghostbird]] 17:55, 28 November 2011 (UTC)

* I believe your problem is the fact that you are using the same save state over and over. Typically, random number generators (RNG) initialize with a single random number called the seed and derive subsequent random values using a mathematical formula. When you save a state on your emulator, you are also saving the current state of the RNG used. So theoretically, you are asking the RNG for a random number in the same exact state each time, resulting in the same result every time you reload. I think this is why you managed to capture your Zapados some time after reloading the original save (new random seed). I'm not sure exactly how you used the reload state method after reinitializing combat. Did you have to hard reload the game 41 times or did you reload once and use the save state 41 times? Please elaborate on this. [[User:Invgamma|Invgamma]] 20:45, 23 December 2011 (UTC)

== Investigation of the RNG ==

I recently thought about the specific cases where the catch formula does not seem to describe the behavior of certain Pokemon. On review, I noticed that the catch formula assumes that every random number generated is completely independent of every other random number. If the random number were using some sort of non-deterministic input to calculate a new seed every time a number is requested, this certainly would be true; however, this is normally not the case.

Consider the case of an encounter with a rare Pokemon with a somewhat high catch rate. Assume that the game finds a new random seed whenever an encounter is supposed to happen (probably sometime before) and uses that number to both determine the Pokemon encountered and to seed further random numbers. When you ask the RNG to generate the next couple random numbers, they are completely dependent on the algorithm used and the seed. With a rare Pokemon, the number of random seeded values that result in an encounter with it is sizable, but smaller than a common Pokemon. If the RNG is not reseeded, the number of possible scenarios (with strings of random numbers) greatly decreases. In this case, it could simply be a mathematical oddity (of the algorithm) where the select few seeds that allows an encounter with a rare Pokemon has subsequent random values that allow it to easily be caught (or even possibly more difficult to catch).

If this is the case, then the rarity of each Pokemon can easily influence catch probabilities by "shaping" the subsequent numbers (by pure mathematical accident). Some random values might even be impossible for, let's say, the first pokeball thrown right after an encounter of a rarer Pokemon.
[[User:Invgamma|Invgamma]] 21:02, 23 December 2011 (UTC)

* Just ran a couple of scenarios on an emulated version of Pokemon White. If I load save states right before encountering a Pokemon (a legendary that you can approach), you can get different random seeds for the battle (first action resulted differently each time). This probably means that the seed for the battle is determined based on conditions right when you encounter the pokemon. [[User:Invgamma|Invgamma]] 23:58, 23 December 2011 (UTC)

:Just to let you know, I've done the investigation already :) Check Smogon's RNG Research thread[http://www.smogon.com/forums/showpost.php?p=3698857&postcount=765] to get filled in on how the game seeds the battle RNG and (approximately) does the majority of battle RNG operations. RNG is only reseeded between battles. Every game uses 4 random numbers for the shake calculations, the only thing new in gen 5 is the critical capture calc.
:First it calculates if critical capture, then the shake/capture values. If result < CV, pass check. Total of 4 for regular catch, 1 for CC.
:Come ask about the battle RNG in IRC, synirc #smogonwifi

== A comment on Critical Capture ==

Having read through the article and especially the section describing the critical capture, it occurred to me that since it usually uses three shake checks, it is cubing the base probability of capture. By only using one shake check, it does not get cubed, which is why it allows capture to occur easier. However, the amount it increases capture rate is dependent on how difficult it is to capture in the first place. Another way to think about what I previously said is to take any specific set of conditions (a species in the wild, how much HP it has out of its total HP, and if it has any status ailments) and calculate the probability of catching it with any one type of ball. You could then take that final probability and, assuming that the same exact conditions and ball are used, a critical capture will increase the chances of capture to the cube root of the capture probability without a critical capture. This relationship means that the lower the capture rate is in specific conditions, the more difference a critical will make in the probability of catching it.

A couple examples would be if a legendary pokemon is attempting to be caught in specific conditions that would create a normal capture probability of 1%, if it is instead a critical capture, that will increase to a 21.5% capture probability. However, at higher capture probability this difference is much smaller. If there is an easily captured pokemon at low health, with a status ailment, and the normal capture probability is 90%, a critical capture in the same circumstances would mean a 96.5% capture probability.

Is this worth adding into the article, or am I just having too much fun with the math?[[User:Morranr|Mor'ranr]] 16:07, 19 January 2012 (UTC)

:It would be cool to see the adjusted probability of that helping, but I don't think it would be one dimensional because of the different critical capture rates.
: If critical capture calc passes, shake check once; else thrice.
:[[User:Kaphotics|Kaphotics]] 00:04, 2 February 2012 (UTC)

:I definitely think it is useful to point out the relationship, and the difference in effect between Pokémon with low rates and high rates. But it might be better to use "realistic" numbers for any examples in the article (i.e. 3/255 instead of 1%). [[User:AySz88|AySz88]] 05:07, 24 February 2012 (UTC)
:<s>Wait, shouldn't it be fourth root? The article says there's needs to be one shake check to pass instead of ''four'' normally. [[User:AySz88|AySz88]] 05:14, 24 February 2012 (UTC)</s>
:: Oops, no, was accidentally looking at a different generation. [[User:AySz88|AySz88]] 07:40, 25 February 2012 (UTC)
::: Fourth roots and third roots never happen in game. The b equation listed is just a probability of you catching (ie all the shake compares lumped together). It does a*0x100 > rand(0,65535) for a pass shake calc. 4 times for gen 3-4, 3x for gen 5 after criticalcapture. That's the one gripe I have about this page, the mathematical approximations aren't what the game does. [[User:Kaphotics|Kaphotics]] 19:22, 25 February 2012 (UTC)
:::: I'm not sure what you're saying here. Yes, the algorithm used for a shake check is not literally a third or fourth root. But while it's nice to document the exact algorithm somewhere, it's probably much more useful to explain the practical results of the algorithm - thus why there are the approximations used in the lede (and occasionally sprinkled elsewhere). You can be sure that when the game designers were playing with formulas, they were doing it in general terms, not caring about whether the RNG was 16-bit or whether a division rounded up or down. The algorithms in the code are crafted to follow their intent. (The difference is famously illustrated in that [https://www.google.com/search?q=pokemon+serious+business old "Pokémon: Serious Business" image] that had an old version of this article - indeed, it's what inspired me to craft the new lede in the first place.) Let's keep our audience in mind.
:::: Though, that does bring up something else: it might be a good idea to more clearly separate the exact algorithms from the approximate interpretations, instead of the hodgepodge mix in the article currently. [[User:AySz88|AySz88]] 05:23, 26 February 2012 (UTC)

:::: Kaphotics (or, anyone), could you elaborate on "It does a*0x100 > rand(0,65535) for a pass shake calc."? I don't understand how multiplying by 256 is equivalent to 65536 / (255/''a'')(1/4) as listed in the article. —[[User:Naokohiro|Naokohiro]] 10:55, 8 May 2012 (UTC)
::::: When I wrote that I wasn't thinking clearly, it does keep the 4th root and such. For every check it does - rand(0xFFFF) and compares it to b. If it is less than b, it passes the wiggle calc and checks again until it either fails or the wiggles result in capture. [[User:Kaphotics|Kaphotics]] 17:45, 22 May 2012 (UTC)

== Generation V -- Interesting Probabilities ==

Since we are still getting the 4th root of the initial probability a and doing 3 shake checks, that makes the chance of capture when the critical capture chance is 0 equal to a3/4.

This takes what would normally be a linear probability always equal to a and puts it on an exponential curve.

If we have more than 30 in the dex, the probability now changes. There is a (a*m)*a1/4 chance of getting a critical capture and then succeeding in capture. Let m be the multiplier for critical capture which is based on the amount caught in the Pokédex. There's also a (1 - a*m)*a3/4 chance of getting a normal capture. So, the total chance of getting a capture is now (a*m)*a1/4 + (1 - a*m)*a3/4 (with m=0, 0.5, 1, 1.5, 2, or 2.5 respectively).

What this does is make an increasingly steeper curve the higher the value of m, but the curve always starts at (0, 0) and ends at (1, 1).
Actually, in the higher values for m, the curve actually gets so steep that it begins to increase a by more than 100% for part of the curve, which suggests a higher chance of capture when the Pokémon isn't completely at its weakest.
I just thought this information was interesting. It's almost like catching Pokémon has its own level up system. [[User:Naokohiro|Naokohiro]] 00:55, 8 May 2012 (UTC)

:Is this something worth mentioning in the article? —[[User:Naokohiro|Naokohiro]] 00:58, 8 May 2012 (UTC)
::I haven't had Critical Capture debugged, but I noticed that what is currently the going theory on the page wasn't matching up with the battle RNG. The critical capture section is really... empty, so why not? If you want to put it in the article be sure to have an image of it! [[User:Kaphotics|Kaphotics]] 17:45, 22 May 2012 (UTC)

==Gen V Shake Rate==
Isn't the Gen V shake rate listed functionally the same as the Gen IV one? It seems slightly redundant having both formulas up, claiming to be different...[[User:Unknowen900|Unknowen900]] ([[User talk:Unknowen900|talk]]) 08:33, 23 July 2012 (UTC)

== Level ball ==

The formula seems to be flawed for the Level Ball. I'm playing HeartGold and I was trying to catch a level 4 Aipom (full health) using my level 58 Crobat. According the the formula, I should have had a 140% chance of catch the Aipom with a Level Ball. I threw 3 or 4 level balls at the Aipom and all of them broke. I've generally found most Pokémon to be more difficult to catch than this formula and their catch rates indicated that they should be, but the Level Ball, in particular, doesn't seem to increase catch rates significantly, if at all. [[User:RS89|RS89]] ([[User talk:RS89|talk]]) 01:59, 27 November 2012 (UTC)
:The number is 140, Then it generates a random number from 0-255, and it does something else. It's not a percentage. I think. --[[User:Abcboy|Abcboy]] ([[User talk:Abcboy|talk]]) 02:21, 27 November 2012 (UTC)
::Nevermind. I just realized I missed a step. [[User:RS89|RS89]] ([[User talk:RS89|talk]]) 02:39, 27 November 2012 (UTC)

== The Formula Simplified (as much as possible) ==
Here's the simple explanation (in Gen V): Your chances to catch a Pokemon are based on 5 things normally (6, if you count capture power, but that is not a normal thing).

'''1st. Species Specific Catch Chance:''' Meaning some pokemon are super easy to catch and come are super hard. The only way to look get this is to just look up the Pokemon, it's Catch Rate is listed in it's info box (on a scale of 0 to 255). So, if it has a 255, you will catch it.
:Pretty much a 100% chance. If it is a 45 (like Celibi) then you only have a 6% chance to catch it before any other factors.

'''2nd. It's Current Health:''' If the creature is at full HP, than your normal chances are cut to 1/3. This means that a 255 would be a 33% chance with a Pokeball at full HP and a Celibi would be a 2% chance. This continues to decrease all the way to 1 HP,
:which gives you between 99% and 99.9% of your normal. Meaning the HP basically no longer negatively affects your catch chance at 1 HP.

'''3rd. The Type of Ball Used:''' You have a normal chance with a Pokeball. Your chance is multiplied by 1.5x for a Great Ball, 2x for an Ultra Ball, 3x for a Repeat or Net Ball, 3.5x for Dive or Dusk Ball, 4x for a Timer or Nest Ball (at max), and 5x for a Quick Ball.
:These all assume you are using them correctly (i.e. Dusk in caves, Repeat on owned Pokemon, and Quick in round 1). Timer and Nest balls can multiply your chances by everything from 1x to 4x (including 3.2134x or some other random number).
:Nest Balls are 4x for a level 1 Pokemon, 3x for a level 11, 2x for a level 21, and 1x for everything above level 30. Timer balls are 1x in the first round, 2x after 10 rounds, 3x after 20, and 4x after 30 rounds.
:This means, if you are trying to catch a pokemon with a catch rate of 255 (easiest possible) at full HP with a Great Ball your chances would start at 100% for the 255, drop to 33% because he is at full HP, and then would increase back to 50% with a Great Ball ((((255 * .33) * 1.5) = 114.75) 114.75/255 = 0.495).
:The same Pokemon would be a 100% chance of catching it with a Quick, Dive, or Dusk Ball (also 100% with a Nest or Timer Ball at max conditions). It is still a 99% chance with a Repeat or Net Ball. It is only a 66% chance; however, with an Ultra Ball or a 50% chance with a Great Ball.
:It would be a 33% chance with a normal Pokeball (Basically normal, Great, and Ultra Balls suck).

'''4th. Status Ailments:''' This is simple, and it stacks multiplicity. Meaning if the pokemon is Paralyzed, Poisoned, or Burned then your chances are 1.5x and if it is Slept or Frozen, then your chances are 2.5x.
:So, in the above example, a 255 Pokemon (100%) at full HP (33%) using a Great Ball (1.5x) gives you a 50% chance. If that same Pokemon is Paralyzed then your chances increase to 75%. If it is Paralyzed AND Poisoned then your chances are 100%.
:Also, if it was JUST Asleep (no Poison or Paralysis) then your chances are still 100% ((255 (Catch Rate) * 0.33 (Full HP) = 84.15) (84.15 * 1.5 (Great Ball) = 126.225) (126.225 * 2.5 = 315.5625) That is higher than 255 so you have a 100% chance).

'''5th. Dark Grass:''' Basically this means that if your encounter is in Dark Grass it is harder to catch the Pokemon based on how far through the game you are. In the beginning of the game, it will further decrease the penalty for it's HP by up to half and at the end of the game you will have full chances.
:100% normal chance if you have more than 600 Completed Pokedex Entries (not just seen, but caught). You will have a 90% of your normal chance if you have between 451 and 600 completed Pokedex entries, 80% for 301 to 450 entries, 70% for 151 to 300 entries, 60% for 30 to 151 entries,
:and 50% of your normal chance if you have less than 30 completed Pokedex entries. Meaning, almost the entire game you will sit at 60% in dark grass. This means that if you have a Pokemon with a Catch Rate of 255 at full HP and you tried to catch him with a normal Pokeball then normally you have a 33% chance.
:If it happens in Dark Grass you have a 16.6% chance. If you used an Ultra Ball, normally you would have a 66% chance, in Dark Grass you would have a 33% chance. The math is a little longer to show here but ...
:Here: (250HP x3 = 750 - (250x2) = 250) <- 1st half of the HP formula. now ((250 * .5 (Dark Grass)) = 125), then (125 * 2 (Ultra Ball) = 250) and Finally ((250/(250 * 3)) = 0.333) <- 2nd half of the HP formula.

I know that is sort of long, but I hope that makes more sense.
[[User:Degrelecence|Degrelecence]] ([[User talk:Degrelecence|talk]]) 06:18, 17 June 2013 (UTC)

EDIT: Sorry forgot that whole Capture Power thing. The 6th factor is Capture Power. The catch rate is multiplied by 1.1x if Capture Power ↑ is active, 1.2x if ↑↑ is active, or 1.3x if ↑↑↑, Capture Power S, or Capture Power MAX is active. [[User:Degrelecence|Degrelecence]] ([[User talk:Degrelecence|talk]]) 06:34, 17 June 2013 (UTC)

:You said that for <30 and 30-151 the percent chances are capture in dark grass are 50% and 60% respectively, but the table provided in the article says these values are 30% and 50% at these intervals. Which one is correct? --[[User:Skit7548|Skit7548]] ([[User talk:Skit7548|talk]]) 05:28, 28 October 2013 (UTC)

== Generation V shake checks ==

The article currently states that three shake checks occur for a regular capture in the Generation V games. This is contradicted by Kaphotics on Smogon (and earlier on this page), who claims that four shake checks occur. Which is correct? [[User:Arcorann|Arcorann]] ([[User talk:Arcorann|talk]]) 08:31, 17 June 2013 (UTC)

== Critical Capture chances? ==

How rare is it to get a Critical Capture?
I'm really confused with this. We could put this on the Critical Capture section. I know the more you capture Pokemon in your Pokedex the more chance you'll catch a Pokemon and it usually always works without fail except if you don't catch Pokemon a lot. But I want to know how rare it is. I got 3 Critical Captures in 1 Day and 2 of them were one after another. How rare is it so we can put it on the Critical Capture area?--[[User:Hydreigonfan1|Hydreigonfan1]] ([[User talk:Hydreigonfan1|talk]]) 14:00, 19 December 2013 (UTC)
:It says how rare it is. To be simple: whatever number the final catch rate is, that number is multiplied by 0, 0.5, 1, 1.5, 2 or 2.5 (depending on how many Pokémon you caught), and then a random number is generated. If it's lower than the number received by multiplying final catch rate, critical capture occurs. [[User:Uploader|Uploader]] ([[User talk:Uploader|talk]]) 14:12, 19 December 2013 (UTC) PS. The only thing missing is what's the interval for that random number. The critical catch success otherwise is based on how likely you are to catch mon (and isn't a guaranteed catch unless you would catch it anyway). [[User:Uploader|Uploader]] ([[User talk:Uploader|talk]]) 14:14, 19 December 2013 (UTC)

== Generation II Shake Probability table ==

Why isn't [[Catch_rate#Generation II 2|this]] an actual table? --[[User:Det|Det]] ([[User talk:Det|talk]]) 08:36, 13 January 2014 (UTC)
:It is, actually. It just doesn't have any pretty borders. ...Also, it's arguably formatted badly (text alignment).
:I did something to it. I experimented with the styles that are on other tables on the page, but it didn't look good to me, so I kept it dead simple. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 09:27, 13 January 2014 (UTC)

== Critical Catch ==

The example can't be right. It says, that catching Kyurem with catch rate 3 with max HP and Pokéball has a probability of 0.4%, which is right. For a critical capture the value 25.03% is given, which is (0.4%)^(1/4) or the forth-root of the chance, respectively. But why should it be the forth-root instead of third-root? Remember that in Gen V only THREE shake checks are performed. The example would be right for Gen IV, but not for Kyurem. Or is there something I do not understand? - Pokémon [[User:Pokémon|Questions?]] -- 23:37, 18 January 2014 (UTC)

:I have checked the version history now. In fact this example has been done before finding out that since Generation V only three shakes are performed (or one for a critical capture). It must be a wrong example. Otherwise I has no mathmatical sense. It's almost like saying 1/3 * 4 = 1. You cannot have only three shakes, but set a single shake to the extend of 4 to get the whole capture chance p. The real chance of this example has to be 15.77%.- Pokémon [[User:Pokémon|Questions?]] -- 00:36, 19 January 2014 (UTC)

== The nearest 1/4096 ==

"and then rounded to the nearest multiple of 1/4096"

I always read this, but... what does it mean?!? The first multiple is 4096 to get a whole number, so if I have numbers between 0 and 255 I always would round them to 1. Nonsence. I just don't understand this expression. - Pokémon [[User:Pokémon|Questions?]] -- 03:34, 19 January 2014 (UTC)

:I believe it means the game uses 12 fractional bits. If the program is executed in the order shown, "(3*HP_MAX - 2*HP_Current)*rate*ball/3/HP_MAX*status", the "/3" will round the result then "/HP_Max" will round the result again. If we were only dealing with int data types, each division would round the result to the next lowest integer (1/3 = 0, 13/10 = 1, 9000/4096 = 2). The fractional bits ensure a calculation like 400/3 yields 546133/4096 (133.33325) instead of just 133 - an error of .006% instead .25%. Is it going to make much of a difference after you round to the nearest whole number? Not really. But when you have the memory and the processing power, this becomes a trivial process, so why not. [[User:Rulingsword|Rulingsword]] ([[User talk:Rulingsword|talk]]) 04:47, 21 January 2014 (UTC)

== Generation VI Catch Rate Formula ==

I think that we can say with certainty that the catch rate formula has changed drastically in Generation VI. [[Zygarde]] has a catch rate of 0 which would mean that it could not be captured except with a Master Ball. This is assuming that the catch rate given is correct. {{unsigned|Mudmaster97}}
:Most Gen VI Pokémon's catch rate aren't known, so it says 0. [[User:Glik|Glik]] ([[User talk:Glik|talk]]) 15:54, 12 February 2014 (UTC)

== Blowing into the microphone ==
In generation IV it was rumored that blowing into the microphone increased your chances of catching the Pokémon. I know to take rumors with a pinch of salt, but it appeared as an official tip in the Official Nintendo Magazine a few years ago. --[[User:Evacino|'''evacino''']][[User talk:Evacino|''' (talk)''']] 19:51, 19 February 2014 (GMT)

== This page confuses people horribly ==

After browsing through a bunch of catch rate-related questions on PokémonDB, I have come to the conclusion that this page is frightfully confusing for the average fan. People scroll down to the later generations, see the single big formula graphic for the modified catch rate in generations III-IV, plug in the numbers, get something that looks vaguely like it could be a percentage and then assume that's it. This could probably be avoided or mitigated by rewriting or at least rearranging the page so that the shake probability calculation is at least closer to the modified catch rate, so people see that there is more to it than that one formula, but I'm open to suggestions. Any thoughts?{{unsigned|Dragonfree}}

== Gen V Shake-Break Comment ==

In BW2 the 1 shake-brake comment is exactly like it is execpt with "Aww" not "Aww" also the 2 shake-break comment isnt listed but I will find out what it is ( sry I havent been signing my comments I keep forgetting) [[User:Pokemonisawesome2|Pokemonisawesome2]] ([[User talk:Pokemonisawesome2|talk]]) 02:42, 19 July 2014 (UTC)
:The 2 shake comment is not listed, because it doesn't exist. In Generation V, a Poké Ball will ''never'' shake two times. While speaking of this; since the game performs 3 checks instead of four, doesn't that make Pokémon more likely to be caught? [[User:Eridanus|Eridanus]] ([[User talk:Eridanus|talk]]) 10:13, 23 August 2014 (UTC)
::thats exactly what i was getting at I have caught nearly every pokemon in white 2 and have never seen it shake twice however I am not sure that this means it only checks 3 time perhaps it checks twice before one of the other shakes? (Like it mabey theres a hidden check that it dosent show?) But if it is just the fact that it only shakes 3 time that would sigfigantly lower the catch rates [[User:Pokemonisawesome2|Pokemonisawesome2]] ([[User talk:Pokemonisawesome2|talk]]) 16:27, 24 August 2014 (UTC)
:::Likely there are only 3 checks for some reason, since it's Generation V, and probably people have simply ripped out code from theame itself. Also, I am sure 3 checks would actually make Pokémon ''easier'' to catch. Checking for eg. a 3/255 four times gives a lower chance than checking for it three times. [[User:Eridanus|Eridanus]] ([[User talk:Eridanus|talk]]) 16:34, 24 August 2014 (UTC)

== Is the Information for Generation VI Truly Missing? ==

I may be mistaken with regard to most of this, but in my experience, the Generation VI games ''seem'' to use basically the same formula to calculate modified catch rate as Generation V, except for the following differences: there are no longer Pass Powers that increase catch rate, but instead an [[O-Power]] can increase catch rate using different coefficients applied in the same part of the formula; and there is no longer a dark grass factor (maybe a flower factor in X and Y?). I know that Pokémon are able to break out of Poké Balls after two shakes, suggesting that the game performs four shake checks, but is there evidence to suggest that the formula that calculates shake probability is different in Generation VI than it was in Generations III-V?
Now, what I'm trying to figure out by posting this topic is what we suspect works in ways we do not understand in Generation VI. What is there to research, and how would we go about doing this research? I would happily help out with this research in any way I can. [[User:Superbreeder|Super]][[User talk:Superbreeder|breeder]] 23:53, 3 December 2014 (UTC)
:The issue isn't that we suspect it works differently somehow; it's that nobody has analyzed the capture routine in the code for the sixth-generation games, so we can't actually know how it works the way we do for the previous games. It's quite likely that it works exactly as you suggest, with the same method as gen V except with four shake checks, but probabilistic formulas are essentially impossible to figure out reliably by experimentation. That said, it could be useful to gather a lot of data just to see if the probabilities seem to match up with what we'd expect if it's gen V with four shake checks. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 02:32, 4 December 2014 (UTC)
::Thank you for your thorough reply, Dragonfree. Your suggestion to test if the probability is what it would be if Generation V performed a fourth shake check is probably the best path we can take, so I might try to do the experimentation on my own as I like to think I have a fair bit of skill when it comes to collecting, managing, and analyzing data. I think I may use a Pokémon which I may find easily and which has a fairly low catch rate to test so that it won't be guaranteed to be caught in a Quick Ball (i.e. I can attract {{p|Skarmory}} by leading with a Pokémon with {{a|Magnet Pull}}, and Skarmory's catch rate is low for a non-legendary Pokémon at 25). Also, I can record the number of shake checks the ball passes in each attempt just in case there was a change to how the games calculate that. I don't know exactly how many data points I'll collect, but probably between 1,000 and 5,000 to reduce error as much as possible. If I get conclusive data, I'll put my findings under this talk page topic. Perhaps there are other users who would like to help test this as well? [[User:Superbreeder|Super]][[User talk:Superbreeder|breeder]] 07:40, 4 December 2014 (UTC)

== Critical catch shakes in Gen VI ==

[http://bulbapedia.bulbagarden.net/w/index.php?title=Catch_rate&diff=2212060&oldid=2209174 Recently] the critical capture section was edited to say that Gen VI has two shake checks on a critical capture. Either someone must have looked at the code/debugged the process, or someone saw two shakes on a critical capture. I doubt it was the former, though (and if it was, the source should be cited). Which leaves the latter...

I can't see how it could be the latter, though. As far as I remember, critical capture in X/Y did one shake. Did ORAS perhaps change this? Can someone with ORAS confidently say how many times the ball shakes on a critical capture? [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 16:43, 9 December 2014 (UTC)

:Critical captures in ORAS definitely only do one shake, like in Gen V. However, do note that when normally when a ball shakes once and then breaks, it means the ball failed the ''second'' shake check - the first happens before any shakes. This is unlike Gen V critical captures, where the ball always shakes once and only then does the single shake check. So it is possible that a) the editor is right and the sixth-generation games perform a shake check both before and after the shake on a critical capture (and thus a failed critical capture can either fail ''before'' or ''after'' the shake), or b) the one shake simply confused the editor into thinking two shake checks were involved based on their understanding of what shakes normally mean. Presumably it would be best to ask them. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 17:36, 9 December 2014 (UTC)
::Since {{u|Pokémon}} visited my talk page to inform me of a comment [[User talk:Dragonfree#Critical Captures|on Dragonfree's talk page]] responding to this issue, I would like to "move" it here so that any of us (or anyone else) can freely respond without having to do so on a single user's talk page.
<blockquote><code>
''Well, my source is my own experience. I saw Pokémon several times breaking out after two shakes though critical capture. The first time I was surprised, because I read on this page before that with one shake the capture would be sure. But I definitely saw Pokémon breaking out while critical captures after both first and second shakes, so it's clear to me, that there must be two shake checks. 
''(Furthermore I saw them breaking out within all four different shake steps, so there must be also four all in all.) 
''But what [[User:Tiddlywinks|Tiddlywinks]] recently has done is muddle. He also changed the probability for the non-critical capture for different generations which should be wrong. Regardless of three or four shakes - the whole probability remains the same. (0.39% in the example)
''--- Pokémon [[User:Pokémon|Questions?]] -- 13:45, 10 December 2014 (UTC)
</code></blockquote>
::First off: I cannot help but doubt what you think you saw. I can only think you are mistaken that it was a critical capture. I would like to hear from someone else that it is possible for two shakes to occur in a critical capture. (Also, can you say whether you saw it in XY or in ORAS?)
::(FWIW: the 0.39% thing has reared its head again on a new comment from Pokémon [[User talk:Tiddlywinks#Critical Captures|on my talk page]]. I will attempt to address it there.) [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 15:38, 10 December 2014 (UTC)

The editor - me - has seen both situations while critical capture: breaking after one and after two shakes. It would also make sense, because there are totally four checks again. I saw that in X & Y. But I see, as I have no solid proof... 
So and why should the formula of b in GenV contain 65536 (=2^16) instead of 65535 (=2^16-1) like it always does? 65536 also is inconsistent with the other generations.--- Pokémon [[User:Pokémon|Questions?]] -- 15:56, 10 December 2014 (UTC)
:Alright, if you want to discuss 65536 vs 65535 here... I agree with you. Thank you for pointing out the "other generations" this time. The Gen III-IV formula is the same as the Gen V formula (after some transformation, and ignoring 65536 vs 65535), so I agree that it should probably be 65535. If you had pointed this out in your edit comment instead of just suggesting that there's hardly any difference (which, by itself, is not at all a good reason to make a change), I wouldn't have reverted your edit, so please try to take more care in the future. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 16:03, 10 December 2014 (UTC)

::Uhm, I just copied my statement, so indeed I already pointed the "other generations" out. And just for my understanding, where did I suggest "that there's hardly any difference"? --- Pokémon [[User:Pokémon|Questions?]] -- 18:21, 10 December 2014 (UTC)

::No, it's definitely 6553'''6''' in the fifth generation, not 65535. The b formula also definitely does take a fourth root (actually two square roots), not a third root, despite that there are only three shake checks. This is information gleaned from reading the actual game code; [http://upokecenter.dreamhosters.com/articles/pokemon-video-games/pokemon-black-version-and-pokemon-white-version-in-depth-guides/pokemon-black-version-and-pokemon-white-version-catch-rate-formula/ Ultimate Pokémon Center] did the original analysis, and a_magical_me later independently did another full analysis and corrected a couple of mistakes. [http://www.dragonflycave.com/gen5capture.aspx My website's explanation] incorporates magical's corrections. Please don't make edits based on vague common-sense feelings about what seems right when there are known facts at hand.
::Meanwhile, Pokémon, you do realize critical captures that ''succeed'' only show one shake? Are you suggesting it sometimes shows a whole extra shake only if you fail? That sounds quite unlikely, especially since if they ''did'' want to incorporate two shake checks into critical captures, the logical way to do it would be like with regular shake checks, where one happens before the first shake and the second happens just after it. I'm sorry, but unless you can provide something more solid than anecdotal experience, it's more likely that you just mistook a non-critical capture for a critical, one way or another. I've seen people swear they personally saw completely impossible things on their Pokémon games hundreds of times before, so I'm inclined to take "This happened to me once" stories with a grain of salt - nothing against you personally, but human perception and memory can be pretty flawed. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 18:34, 10 December 2014 (UTC)
:::Sorry, Dragonfree. It's not much of an excuse, but I didn't really know where I could find a reliable reference.
:::@Pokémon: I meant that you didn't point out "other generations" in your edit summary; but in your comments afterwards, you have. Your edit summary said, ''"Seriously, the fraction is so tiny, nobody can read it without grand zooming..."'' The only sense I could make of that comment was that the difference between 65536 and 65535 was very small. But perhaps that's not what you meant. Regardless, it's not really important now. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 19:01, 10 December 2014 (UTC)
::::I meant the size of the fraction. :) Just the size. It's too tiny to read.
::::@Dragonfree: Thank you for the pages, that's what I wanted to see. Although I do not understand why the catch rate calculator on your website needs the level of the Pokémon? The level is absent in the formula. --- Pokémon [[User:Pokémon|Questions?]] -- 19:54, 10 December 2014 (UTC)
:::::The calculator uses the level to calculate the Pokémon's actual HP, mostly significant if you select the "Exactly 1 HP" option - it makes a bit of a difference whether the Pokémon has one out of 20 HP or one out of 200 HP. Not much of one (in the newer games, anyway; in the second-generation games there is some glorious wonkiness involving underflows where the exact HP can make a massive difference), but I like precision. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 20:58, 10 December 2014 (UTC)
::::::From the level alone you can't know the max HP, thats no precision. And percent is percent, neither it is needed to know the exactly HP nor the level. The whole formula has no level inside, so it can't make a difference. And if it makes a difference, it must be explained right here in this article. --- Pokémon [[User:Pokémon|Questions?]] -- 23:40, 10 December 2014 (UTC)
:::::::It's not the level alone - we also know the species, and thus its base HP, and wild Pokémon's EVs are always zero. The only remaining variable needed to determine the max HP is the IV, and the calculator calculates the result for each of the 32 possible IVs. By default the calculator then averages the results, since each IV is generally equally likely, but if you check the "Show detailed report?" box, you'll see the exact results for each HP IV.
:::::::Percent is percent, yes, but 1 out of 20 HP is 5%, while 1 out of 200 HP is 0.5%. Like I said, it's only actually significant at exactly 1 HP. Usually you don't actually know the Pokémon's exact current HP, so there's an unavoidable margin of error there either way, but by calculating the actual max HP we can get guaranteed exact results at full and 1 HP (this is why I have a special "exactly 1 HP" option, separate from "1%"). And while the results at full HP will be pretty much identical no matter what the actual max HP is, there are rounding errors that this allows for taking into account accurately, which I like to do because as I said, I like precision.
:::::::Please consider that maybe I know what I'm talking about. I've spent a ''lot'' of time on these pages and calculators; I assure you I didn't just throw the level in there for no reason. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 00:18, 11 December 2014 (UTC)
::::::::Of course I know what you mean. For 1 HP remaining the level is a factor. But as long as you don't know the IV exactly, it's not precise, right? ;) Yes, it's close enough. 
::::::::But I wonder why the result is also influenced, when I set neither 100% nor 1 HP but e.g. 40%? A percentage is already most precise and independent from the level! I have seen there differences of over three percent between level 1 and 100 which is a large amount and no rounding errors. Just want to understand that phenomenon and why I can't calculate these results with the formulas on Bulbapedia... --- Pokémon [[User:Pokémon|Questions?]] -- 11:29, 11 December 2014 (UTC)
:::::::::Ah, that's just because when you set a percentage, the calculator uses it to come up with an actual integer current HP value to use in the calculation, and at very low max HPs that can introduce a slightly significant error. So, rounding errors, but not in the formula per se. (Actually, it was a bigger rounding error than it needed to be; I just made a small change that reduces it.) In general it's always going to be a bit fuzzy when you're not at 100% or exactly one HP, because both the HP bar itself and the player's approximation of how much of it is filled inevitably introduce a degree of error. I'd rather have it show the actual results for a reasonable guess at the exact HP than make up a general fuzzy result for that percentage of HP, though. The calculators simulate the calculations the game performs very exactly; having the HP part just rely on it being roughly such-and-such kind of defeats the point. (Besides, of course, that this way the result is exact at 100% or exactly 1 HP without having to special-case it.) [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 13:14, 11 December 2014 (UTC)

== Just caught a Lugia in red health underwater after using Dive in a Dive Ball. ==

I just caught Lugia in red health in ORAS so you have to use dive to catch it and it worked first time in a Dive Ball. Does anyone know the chances of this happening? --[[User:Hydreigonfan1|Hydreigonfan1]] ([[User talk:Hydreigonfan1|talk]]) 18:47, 10 December 2014 (UTC)
:Since it's in Gen VI, technically: No, not for sure. But it's very likely the same as Gen V. This might be a better question for the forums, though... [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 19:04, 10 December 2014 (UTC)
::I'd say it's more likely to be the same or just about the same as in Gen IV, actually, since it does look like Gen VI does four shake checks on a regular capture like Gen IV. But yes, the exact mechanics of capture in the sixth-generation games are currently unknown. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 00:21, 11 December 2014 (UTC)

== rounding of a ==

Is the value for "a", the modified catch rate, rounded down/up before put into the equation for "b", the shake probability?

For example, If a great ball is used on a Kyogre (catch rate=5) with full health, the equation becomes a=5*1.5/3=2.5

would a=2.5, or be rounded down to 2, or up to 3 before put into the equation for b. [[User:Zombiedude347|Zombiedude347]] ([[User talk:Zombiedude347|talk]]) 22:12, 28 December 2014 (UTC)
:Rounding in the games usually happens down. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 22:16, 28 December 2014 (UTC)
:The final result of a is always rounded down to the nearest integer. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 22:28, 28 December 2014 (UTC)
::Note, however, that if you're thinking of ORAS, they changed Groudon and Kyogre's catch rate to 3. And if you're thinking of R/S/E, the value is rounded down at every intermediate step in the calculation as well. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 22:33, 28 December 2014 (UTC)
:::In OR/AS, <var>a</var> is rounded to the nearest multiple of 1/4096. --[[User:A magical me|a_magical_me]] ([[User talk:A magical me|talk]]) 00:25, 29 December 2014 (UTC)
::::Right, yeah, I misremembered. Was probably thinking of the critical capture value. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 01:09, 29 December 2014 (UTC)

::::So, in my example, for a would equal 2.5=(2+2048/4096), or if using the current catch rate, a=3*1.5/3=1.5=(1+2048/4096)[[User:Zombiedude347|Zombiedude347]] ([[User talk:Zombiedude347|talk]]) 15:46, 29 December 2014 (UTC)
:::::Yes, that's the gist of it. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 19:06, 29 December 2014 (UTC)

== Are we sure the shake probabilities for Gen III-VI are correct? ==

And I don't mean just numerically correct--I ask because, the formula written down for Gen III-IV is:
'''''b'' = 1048560 / sqrt(sqrt(16711680/''a''))''';
which is weird, since it uses numbers that require 3-bytes to represent. It is made even weirder when you consider that the formula there is ''exactly'' equivalent to:
'''''b'' = 65535 / sqrt(sqrt(255/''a''))''';
which takes numbers of no more than 2-bytes, which makes a lot more sense, and unless the former was ripped straight from the code, seems closer to what the function actually would be (since it takes up less memory and uses numbers on a similar scale found elsewhere in the mechanics).

This also makes me want to ask if the shake probabilities on Gen V and Gen VI don't have a small typo, since both have similar formulas to the above (though Gen VI has a denominator of (255/''a'')^0.1875), but instead of 65535, they have 65536, which is 1 off, but is 17-bit to 65535's 16-bits and that would be...inelegant. It would break the symmetry, since if it's 65535, then Gen III-V would all have the same shake probability function, and it seems a little silly to tweak it by 1 in a way that would require an extra byte of memory for the input, and right before a more substantial tweak in the very next gen.
But I don't know--for all I know, that could be faithfully ripped straight from the source code.

[[User:Xovvo|Xovvo]] ([[User talk:Xovvo|talk]]) 20:46, 23 February 2015 (UTC)
:Yes, they are correct, and all of these numbers are indeed taken straight from the actual code.

:Your Gen III/IV alternative formula is actually ''not'' exactly equivalent, because the square roots and divisions prior to Gen V are integer operations, i.e. they always round down: if they used the shorter version, then any ''a'' of 16 or above would actually give the same ''b'', which would be completely absurd. (255/16 gets rounded down to 15, the square root of which is rounded down to 3, the square root of which is rounded down to 1, and we end up with a ''b'' of 65535, exactly like if ''a'' were 255.) Effectively, Game Freak took the formula they wanted and multiplied by 16 both above and below the line, in order to have bigger numbers to work with in the calculation that would result in less drastic rounding errors. (There are still fairly major rounding errors, mind you; any ''a'' of 200 or above still results in a ''b'' of 65535.)

:The reason Gen V-VI use 65536 and not 65535 is that there is a tiny chance for the Pokémon not to be caught if ''b'' is 65535; presumably they ''wanted'' ''b'' to be able to be 65536 all along but originally used 65535 exactly because 65536 can't be stored in a two-byte register. In Gen V onwards they're using bigger fixed-precision numbers where they can fit 65536 in just fine anyway. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 00:21, 24 February 2015 (UTC)

== Trivia First Bullet Point is Vague and Needs Explaining ==

I made an edit by adding <nowiki>{{incomplete}}</nowiki> to the trivia section that needs further explanation of how the button presses affect catch rate in [[Generation I]] games. [[User:Abcboy]] removed claiming he clarified it but I see no clarification. Needs specifics or citations if the article will state such a claim! Why does catch rate get affected by button combinations? Which button combinations work? How much does it affect catch rate? Which games does it work for if not all? --[[User:Wildgoosespeeder|Wildgoosespeeder]] ([[User talk:Wildgoosespeeder|talk]]) 01:45, 17 March 2015 (UTC)
:There are no specific button combinations that affect catch rate in any specific way; it's simply that in the first-generation games, the random number generator is advanced when buttons are pressed, so if you want the random number generator to hit a particular number when it does the calculation ''and you know which numbers are coming up when'', such as when doing a tool-assisted speedrun, pressing buttons will advance the RNG further. It's not something that's ever relevant to normal gameplay in any fashion. [[User:Dragonfree|Dragonfree]] ([[User talk:Dragonfree|talk]]) 02:01, 17 March 2015 (UTC)
::Also, FWIW, I kind of want to add that the Trivia section may be the ''last'' place that should have an "incomplete" template anyway. It's called Trivia for a reason. If it were me, the talk page here would have been my first resort. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 02:15, 17 March 2015 (UTC)
:::Also, what ABCboy added was, pretty much, "as button input could slightly influence the random number generation in the catch rate formulas". This was his attempt at clarification. The entire trivia point is Greek to me, personally, as a casual player only, but I can see how it would be of interest to the right party. I was also going to comment that we don't put "incomplete" in the trivia section, but all the edit conflicts (I got two) got Tiddlywinks' pointing it out in first. [[User:CycloneGU|CycloneGU]] ([[User talk:CycloneGU|talk]]) 02:17, 17 March 2015 (UTC)

== 'Status value' in Generation I ==

In the Generation 1 algorithm, step four is

: Otherwise, if N minus the '''status value''' is greater than the Pokémon's catch rate, the Pokémon breaks free.

What is the status value? It isn't mentioned anywhere else in the page.

The only thing I saw that I think it could be referring to is the numbers in step three:

: The Pokémon is caught if...
:: It is asleep or frozen and N is less than 25.
:: It is paralyzed, burned, or poisoned and N is less than 12.

If that is the case, step three can definitely be worded better. [[User:Meemo16|Meemo16]] ([[User talk:Meemo16|talk]]) 20:34, 8 March 2016 (UTC)
:Problem should now be fixed. [[User:SirFinkleBottom|Sir]][[Special:Contributions/SirFinkleBottom|Finkle]][[User talk:SirFinkleBottom|Bottom]] 21:29, 8 March 2016 (UTC)

== Number of shakes in Gen 1 ==

In gen 1, I saw Pokémon who broke free when they were supposed to get caught. I don't get it. Does that mean they can break free at the fourth shake ? -- [[User:Braviapert|Bravia]][[User talk:Braviapert|per]][[Special:Contributions/Braviapert|t]] 15:20, 24 April 2016 (UTC)
:In Generation I, there are only two states as far as I know: the Pokemon is caught or it breaks after a fixed amount of shakes (or it outright avoids the Ball if it's really low). If it breaks, the amount of shakes is dependent on how likely you are to capture it. [[User:Eridanus|Eridanus]] ([[User talk:Eridanus|talk]]) 14:01, 25 April 2016 (UTC)

== Catch rates for SM ==

Does anyone have any info on the formula used for Sun or Moon? [[User:Prowlcorp|Prowlcorp]] ([[User talk:Prowlcorp|talk]]) 02:03, 26 January 2017 (UTC)

== How it is calculated ==

Looking at page I can't understand much so I ask a question. How do you calculate probablility for catching Pokemon with a Poke Ball and full health? Just give me a formula with catch rate written as x.--[[User:Dominikololo|Dominikololo]] ([[User talk:Dominikololo|talk]]) 18:25, 19 September 2017 (UTC)

I can't belive it's so easy (x/765).--[[User:Dominikololo|Dominikololo]] ([[User talk:Dominikololo|talk]]) 17:16, 23 September 2017 (UTC)

== Generation III-IV Shake Probability ==

In the [https://bulbapedia.bulbagarden.net/wiki/Catch_rate#Shake_probability_3 Shake Probability] formula for Gen III-IV I see the ''sqrt'' used twice. Is this because the game actually does it like that or could it be written like a ''root 4'' of the given division?
[[User:Fkbm|Fkbm]] ([[User talk:Fkbm|talk]]) 09:10, 16 April 2019 (UTC)
fkbm

: The game actually does it that way. It ''can'' be replaced by a fourth root, since the result is identical (the intermediate flooring to an integer never changes the final result), but the game only has a square root function. [[User:Aaaaaa123456789|Aaaaaa123456789]] ([[User talk:Aaaaaa123456789|talk]]) 09:21, 16 April 2019 (UTC)

== Catch rate for Gen 8 ==
So it's pretty obvious the catch rate is different in Gen 8. Does anyone know how it really works? The level of the Pokemon definitely matters to the point where it's sometimes impossible to catch a Pokemon even 1 level above you. And for that matter, how do Raid Battle catch rates work? Are they predetermined at some point or something?
--[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 21:04, 8 December 2019 (UTC)
: This definitely requires more research -- after playing through the game I never once got any "obvious" impression of the catch rate being different from previous generations. (Of course, I was usually about level-matched with the wild Pokemon in question.) [[Max Raid Battle]] catch rates are (by now) documented on their own page, with the host having a higher catch rate than guests and the base rate being different for Gigantamax forms. --''[[User:Stratelier|Stratelier]]'' 02:06, 23 August 2020 (UTC)
: Okay, here is a "quick" experiment:
::* Given: postgame (8 Gym badges & Champion status)
::* Lead Pokemon: a Lv.100 Noctowl
::* Area: [[Galar Route 1]]
::* Target(s): any visible wild Pokemon ({{p|Rookidee}}, {{p|Skwovet}}, {{p|Wooloo}}, {{p|Nickit}})
:::These Pokemon all have a catch rate = 255 (expected catch probability: 44% per throw)
::* Throwing a standard Poke Ball on turn 1 until caught

: After throwing 100 Poke Balls, my data:
:: Normal throws (catch/miss ratio): 55:7 (88% success)
:: Critical throws: 36:2, or 95%

: This was approximately 2x the expected catch rate. Hmm...
: --''[[User:Stratelier|Stratelier]]'' 04:03, 23 August 2020 (UTC)

Time for experiment #2. This one involves a LOT more setup, but:
:* Area: [[Wild Area]], [[Bridge Field]]
:* Target: Lv.60 {{p|Zigzagoon}} (catch rate = 255)
:* Lead Pokemon: any Lv.1 Pokemon (I have the Pokemon Nursery set up with a breeding pair for this purpose)
:* Other party members (in case this is relevant): a Lv.45-50 {{p|Coalossal}}
:* Throwing a Poke Ball on turn 1 until caught (or unless lead Pokemon faints)

And my data as follows (using 100 standard Poke Balls)
: Normal throws (catch/miss ratio) = 42:44 (49%)
: Critical throws = 12:2 (85%)

Which is close to the expected catch rate. Also note a much lower incidence of critical throws this time (1:7 versus 2:5). Hmmm...

(This also gives me a huge supply of Lv.60 Zigzagoons for performing a level-matched experiment later)
--''[[User:Stratelier|Stratelier]]'' 20:29, 26 August 2020 (UTC)

So if I'm understanding this correctly, the level is affecting the catch rate? Doesn't crit rate increase the more the Pokedex is filled? Would the results skew to more misses if you have a very incomplete Pokedex, or does it just affect the chance of a crit happening?
--[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 05:00, 27 August 2020 (UTC)

Talk:Disguise (Ability)

2020-07-19T02:07:32Z

Koetsu: /* Disguise, Confused, and Substitute */ new section

==Mummy interaction already added==
Can the "Incomplete Article" header be removed here? It seems as though someone provided the interaction with Mummy already. [[User:BurningKirby|BurningKirby]] ([[User talk:BurningKirby|talk]]) 18:21, 28 July 2017 (UTC)
:Done. In the future, feel free to remove the "incomplete" template yourself if you're sure it's not needed anymore. [[User:Pumpkinking0192|Pumpkinking0192]] ([[User talk:Pumpkinking0192|talk]]) 18:41, 28 July 2017 (UTC)
::Sure, thank you. I wasn't sure if someone had kept it around for some reason, otherwise I would have done it. [[User:BurningKirby|BurningKirby]] ([[User talk:BurningKirby|talk]]) 20:05, 28 July 2017 (UTC)

== Disguise, Confused, and Substitute ==

I'm not sure why this hasn't come up before, but I think it should be worth mentioning. If Mimikyu hits itself in confusion while behind a substitute, Disguise will still be busted through it. Does anything else that hit through substitute break disguise this way as well?

Talk:Catch rate

2019-12-08T21:04:31Z

Koetsu:

Talk:Battle Tree/Pokémon (001-251)

2017-09-03T17:22:24Z

Koetsu: Created page with " == Hidden Abilities == Can all hidden abilities appear? I know the starters sometimes come out with hidden abilities, but what about others that can have 3 abilities? I know..."

== Hidden Abilities ==
Can all hidden abilities appear? I know the starters sometimes come out with hidden abilities, but what about others that can have 3 abilities? I know I fought a Power of Alchemy Alolan Muk. Would the chances of that happening be just as likely as the other 2 abilities.

Talk:Future Sight (move)

2017-07-22T05:57:10Z

Koetsu: /* Double Battle Behavior */

== Tyranitar ==

Why did it affect my Tyranitar if it was Psychic Type? '''[[User:Optimus35|Agent]] [[User:Optimus35/Mission|4]][[User:Optimus35/Emerald|4]][[Gallade (Pokémon)|8]][[User talk:Optimus35|Talk]] | [[User:Optimus35/Diamond&Pearl|DP]]''' 02:51, 13 October 2007 (UTC)
:I'm pretty sure it doesn't take type into account. I remember using it on a Fighting-type to no super-effectiveness.--[[User:Urutapu|Ｌｏｖｅはドコ？]] ([[User talk:Urutapu|talk]] • [[Special:Contributions/Urutapu|contribs]]) 03:20, 13 October 2007 (UTC)
::Yeah, it and Doom Desire are calculated differently. '''[[User:TTEchidna|TTE]][[User talk:TTEchidna|chidna]]''' 05:30, 13 October 2007 (UTC)
:::The in-game data may have a Power, but I think that is calculated differently as well. When I was capturing Azelf, I used a level 23 {{tt|Kricketune|Don't Ask Why... XD}}. Each time I tried, Azelf used this attack and each time it hit Kricketune it took off different amounts each time. Sometimes Kricketune would faint, sometimes it would only take off a little. [[User:Tesh|'''TESHIGIGAS''']] 17:54, 16 January 2008 (UTC)
::::Did it use Nasty Plot? --[[User:PLA|PLA]] 12:36, 19 May 2010 (UTC)

== STAB ==

So, Future Sight do not take type into account. What about STAB? [[User:Tenno Seremel|Tenno Seremel]] 09:30, 6 January 2009 (UTC)
:Nope. Because it is technically typeless, it does not get STAB, hits all Pokémon and bypasses Wonder Guard. — [[User talk:The dark lord trombonator|THE TROM]] — 09:40, 6 January 2009 (UTC)
::Thought so. I didn't know about Wonder Guard though. I'll need to check this. Thanks. [[User:Tenno Seremel|Tenno Seremel]] 11:56, 6 January 2009 (UTC)

== Focus Sash ==

Focus Sash in the “In-battle effect item” description says otherwise:

<blockquote>Can also protect against multiple-strike moves such as Fury Attack and Triple Kick, recoil damage, and self-inflicted confusion damage, '''but not Future Sight and Doom Desire'''.</blockquote>

Which one is correct?

— [[User:Tenno Seremel|Tenno Seremel]] 07:19, 18 May 2009 (UTC)

== Twistedspoon ==

Because it is technically typeless, does it take items like Twistedspoon into account? It shouldn't... [[User:FrozenStrategy|FrozenStrategy]] 23:08, 17 July 2010 (UTC)

== Psychic type. ==

As it's no longer typeless, can it still hit through Wonder Guard? I suppose it will also be resisted by Psychic, Steel and Dark now. [[User:PLA|PLA]] 12:54, 13 January 2011 (UTC)

== Kirlia? ==

Can someone add http://bulbapedia.bulbagarden.net/wiki/Melodi Melodi's Kirlia to the anime list please?[[User:Emeraldben|Emeraldben]] 12:17, 4 November 2011 (UTC)
:I added it. '''[[User:LimeGreenCharizard|LimeGreen]]''[[User talk:LimeGreenCharizard|Charizard]]'''''[[Special:Contributions/LimeGreenCharizard|♂]] 13:03, 4 November 2011 (UTC)
::Apparently its not actually Future Sight, so both pages have been changed accordingly. [[User:Vuvuzela2010|'''Vuvuzela2010''']][[Latios (Pokémon)| Δ ]] 13:18, 4 November 2011 (UTC)
*She does actually say use future sight though dont she?[[User:Emeraldben|Emeraldben]] 21:19, 4 November 2011 (UTC)
:No, it just looks into the future using its Psychic powers, but it isn't Future sight. [[User:Littlmiget123|Littlmiget123]] 14:40, 10 November 2011 (UTC)

== Fails if User Faints? ==

I've noticed that when my Swoobat faints after having used Future Sight (but before the actual attack hits) that Future Sight doesn't seem to connect to the target Pokémon. Is this normal or a change made in Gen 5? -[[User:Yourlilemogirl|Yourlilemogirl]] 05:40, 10 November 2011 (UTC)

== Shell Bell ==

How does Future Sight interact with [[Shell Bell]], if at all? {{unsigned|Krychek}}

== Accuracy and Evasion ==
I got asked by a friend, and didn't know the answer (nor was it on the site): how do Accuracy and Evasion work for this move? Is it the same as Sp Atk/Def? (Is this a detail worth adding, if someone knows?) [[User:Magnema|Fix my stuff if it needs it, I don't have much editing XP.]] ([[User talk:Magnema|talk]]) 21:25, 2 February 2017 (UTC)
:According to [http://upcarchive.playker.info/0/upokecenter/dex/index.html%3Flang=en&move=248.html UPC], accuracy check is done when this attack lands (with the values at that point in time), in every generation. I wouldn't oppose that being added. [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 17:11, 3 February 2017 (UTC)

== Only One ==

From my testing in Pokemon Showdown, I discovered that:
*Only one Future Sight may be active at any given time per player. (even if used by separate pokemon) — [[User:Zyra|Zyra]] 01:57, 4 June 2017 (UTC)
::Please understand that Pokémon Showdown is coded from scratch and thus could easily have errors that are not consistent with the actual Pokémon games. For this reason, if you want to test mechanics, they ''must'' be tested in the actual games. [[User:Pumpkinking0192|Pumpkinking0192]] ([[User talk:Pumpkinking0192|talk]]) 02:11, 4 June 2017 (UTC)
:::Ok, I understand. — [[User:Zyra|Zyra]] 02:39, 4 June 2017 (UTC)
::::For the record, I have tested this in-game myself before, and this is consistent with the games. However, Pumpkinking is entirely correct about the unreliable nature of Showdown for determining game mechanics. --[[User:SnorlaxMonster|'''Snorlax''']][[User talk:SnorlaxMonster|'''Monster''']] 03:01, 4 June 2017 (UTC)
:::::I'm pretty sure it's what the article says: not one Future Sight ''per player'', but one Future Sight or Doom Desire ''per target slot''. (I think I even tested that.) Actually, I believe that's even consistent with Showdown (and most specifically, even their move description). [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 15:49, 9 June 2017 (UTC)

== Double Battle Behavior ==
There are some important distinctions with this move in Double Battles that I think could be mentioned on this page.
I've only gotten to try this in Gen VII. Unlike most other moves, if there is no Pokémon in the targeted slot, the move will still initialize on the targeted slot without redirecting. This will cause the camera to clip through the middle of the stage because there is no target Pokémon. The timer still counts down on that slot and if a Pokémon fills it in later, the timer doesn't reset. However, if there is no Pokémon in the slot by the time the attack is due to hit, it will vanish without a message.

You can also have multiple Future Sights set up: one on both enemies, and your ally.

[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 01:55, 15 July 2017 (UTC)
:I agree it should be mentioned. I think the article already mentions some of it, but not all of it. Please feel free to add what you have (both here and at {{m|Doom Desire}}). [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 12:32, 15 July 2017 (UTC)

::I'd like to know how consistent this behavior is first though. I don't have any previous-gen games to test it on and see when this started. And I wouldn't have a Jirachi to test Doom Desire with (though it likely behaves the same way).[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 03:42, 16 July 2017 (UTC)
:::You're absolutely right! Good thinking.
:::Apart from the camera clipping (which really is minor IMO), [http://upcarchive.playker.info/0/upokecenter/dex/index.html%3Flang=en&move=248.html this] (and [http://upcarchive.playker.info/0/upokecenter/dex/index.html%3Flang=en&move=353.html this]) might give you the information you need: that it has always been the case. (I believe I once tested/confirmed it for a few games, including Generation VI; but I certainly didn't watch out for the camera.)
:::Anyway, what you ''could also'' test (when you're interested) is what happens when the Double Battle turns into a single battle during Future Sight's duration (i.e., target an opponent slot and then faint the Pokémon at it, have all but one of yours faint as well, and see whether Future Sight strikes the remaining opponent; this ''could'' even differ depending on whether it's the left or right slot.) [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 09:28, 16 July 2017 (UTC)

:::::The page is quite technical, but if I understood it correctly, ''Remains in effect even if user or the opposing Pokémon leaves the battle '', confirms it? Because even in single battles, if the move is used, and the target switches out or faints, then the move will still hit whoever is there. The reason I mention the camera is because it makes it seem like a situation that wasn't properly accounted for and looks unintentional.
:::::Also, when does a battle actually become a single battle? The fainted targets remain even when there is one Pokémon on each side in a double battle. I tested on an SOS battle and when the empty slot was targeted and nothing filled it, the attack vanished after the turns passed. [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 17:18, 16 July 2017 (UTC)
::::::I worked with that site a lot, so I'm quite used to their wording, and I underestimate how difficult it was to parse it when I started. (Sorry.) The most important line for what you described seems to be ''If there is a Pokémon at the target's position''.
::::::I'm not entirely sure how it works in SOS Battles, but in Doubles, once it's a 1-on-1, it behaves like a single battle (no more target choice, no more {{DL|Damage|Damage calculation|"Targets" penalty for moves like Earthquake}}, etc. [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 17:40, 16 July 2017 (UTC)
:::::::When does it actually do that though? I think even in Trainer battles, when it's down to a 1 on 1, it's still technically a double battle because you still have a choice for target. Even Earthquake seems weaker and the hit marks can still be seen on the empty slots. If a double battle does transform into a single battle, then I don't know what would happen. [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 04:40, 17 July 2017 (UTC)
{{indent}} [[Double Battle#Effects on moves]] says when "there is only one target at the time the move is executed", Earthquake etc. do regular/greater damage. I believe that's still the case, but admittedly introducing the new SOS Battle mechanic might have changed things.

I might try to hunt down what I asked for in the following days myself (as you have no access to different generations); I wanted to test {{m|Leech Seed}} in Doubles for ages, so maybe it's an opportunity to combine these two. (If I do, I'll also try to replicate what you observed, and hunt down when exactly that occurs.) Regardless of the question I had, and whatever its answer is, I believe you may already add what you initially came here for. [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 15:29, 17 July 2017 (UTC)

:Okay. I will add what I know with the expectation that it will be revised for accuracy later. {{unsigned|Koetsu}}
::Thanks.
::In addition to what I just added to the actual article, I also found that the target selection is only omitted in Generation III (there are empty, unselectable slots in Generations IV, empty selectable slots in Generations V and VI, and silhouettes in Generation VII). However, Earthquake etc. apparently do become stronger once it's a 1-on-1 (and they always did).
::(Also, if there's no target at the selected slot, the camera focuses the user in Generation VI. I didn't pay attention in Generation V.) [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 16:22, 21 July 2017 (UTC)

:::Excellent! So now I can see it started with Generation V and that it actually used to redirect in Gen III. The descriptions seem accurate and clearer than before. Now I assume the same goes for Doom Desire?
:::Thanks for looking into this [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 05:56, 22 July 2017 (UTC)

Talk:Future Sight (move)

2017-07-22T05:56:48Z

Koetsu: /* Double Battle Behavior */

== Tyranitar ==

Why did it affect my Tyranitar if it was Psychic Type? '''[[User:Optimus35|Agent]] [[User:Optimus35/Mission|4]][[User:Optimus35/Emerald|4]][[Gallade (Pokémon)|8]][[User talk:Optimus35|Talk]] | [[User:Optimus35/Diamond&Pearl|DP]]''' 02:51, 13 October 2007 (UTC)
:I'm pretty sure it doesn't take type into account. I remember using it on a Fighting-type to no super-effectiveness.--[[User:Urutapu|Ｌｏｖｅはドコ？]] ([[User talk:Urutapu|talk]] • [[Special:Contributions/Urutapu|contribs]]) 03:20, 13 October 2007 (UTC)
::Yeah, it and Doom Desire are calculated differently. '''[[User:TTEchidna|TTE]][[User talk:TTEchidna|chidna]]''' 05:30, 13 October 2007 (UTC)
:::The in-game data may have a Power, but I think that is calculated differently as well. When I was capturing Azelf, I used a level 23 {{tt|Kricketune|Don't Ask Why... XD}}. Each time I tried, Azelf used this attack and each time it hit Kricketune it took off different amounts each time. Sometimes Kricketune would faint, sometimes it would only take off a little. [[User:Tesh|'''TESHIGIGAS''']] 17:54, 16 January 2008 (UTC)
::::Did it use Nasty Plot? --[[User:PLA|PLA]] 12:36, 19 May 2010 (UTC)

== STAB ==

So, Future Sight do not take type into account. What about STAB? [[User:Tenno Seremel|Tenno Seremel]] 09:30, 6 January 2009 (UTC)
:Nope. Because it is technically typeless, it does not get STAB, hits all Pokémon and bypasses Wonder Guard. — [[User talk:The dark lord trombonator|THE TROM]] — 09:40, 6 January 2009 (UTC)
::Thought so. I didn't know about Wonder Guard though. I'll need to check this. Thanks. [[User:Tenno Seremel|Tenno Seremel]] 11:56, 6 January 2009 (UTC)

== Focus Sash ==

Focus Sash in the “In-battle effect item” description says otherwise:

<blockquote>Can also protect against multiple-strike moves such as Fury Attack and Triple Kick, recoil damage, and self-inflicted confusion damage, '''but not Future Sight and Doom Desire'''.</blockquote>

Which one is correct?

— [[User:Tenno Seremel|Tenno Seremel]] 07:19, 18 May 2009 (UTC)

== Twistedspoon ==

Because it is technically typeless, does it take items like Twistedspoon into account? It shouldn't... [[User:FrozenStrategy|FrozenStrategy]] 23:08, 17 July 2010 (UTC)

== Psychic type. ==

As it's no longer typeless, can it still hit through Wonder Guard? I suppose it will also be resisted by Psychic, Steel and Dark now. [[User:PLA|PLA]] 12:54, 13 January 2011 (UTC)

== Kirlia? ==

Can someone add http://bulbapedia.bulbagarden.net/wiki/Melodi Melodi's Kirlia to the anime list please?[[User:Emeraldben|Emeraldben]] 12:17, 4 November 2011 (UTC)
:I added it. '''[[User:LimeGreenCharizard|LimeGreen]]''[[User talk:LimeGreenCharizard|Charizard]]'''''[[Special:Contributions/LimeGreenCharizard|♂]] 13:03, 4 November 2011 (UTC)
::Apparently its not actually Future Sight, so both pages have been changed accordingly. [[User:Vuvuzela2010|'''Vuvuzela2010''']][[Latios (Pokémon)| Δ ]] 13:18, 4 November 2011 (UTC)
*She does actually say use future sight though dont she?[[User:Emeraldben|Emeraldben]] 21:19, 4 November 2011 (UTC)
:No, it just looks into the future using its Psychic powers, but it isn't Future sight. [[User:Littlmiget123|Littlmiget123]] 14:40, 10 November 2011 (UTC)

== Fails if User Faints? ==

I've noticed that when my Swoobat faints after having used Future Sight (but before the actual attack hits) that Future Sight doesn't seem to connect to the target Pokémon. Is this normal or a change made in Gen 5? -[[User:Yourlilemogirl|Yourlilemogirl]] 05:40, 10 November 2011 (UTC)

== Shell Bell ==

How does Future Sight interact with [[Shell Bell]], if at all? {{unsigned|Krychek}}

== Accuracy and Evasion ==
I got asked by a friend, and didn't know the answer (nor was it on the site): how do Accuracy and Evasion work for this move? Is it the same as Sp Atk/Def? (Is this a detail worth adding, if someone knows?) [[User:Magnema|Fix my stuff if it needs it, I don't have much editing XP.]] ([[User talk:Magnema|talk]]) 21:25, 2 February 2017 (UTC)
:According to [http://upcarchive.playker.info/0/upokecenter/dex/index.html%3Flang=en&move=248.html UPC], accuracy check is done when this attack lands (with the values at that point in time), in every generation. I wouldn't oppose that being added. [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 17:11, 3 February 2017 (UTC)

== Only One ==

From my testing in Pokemon Showdown, I discovered that:
*Only one Future Sight may be active at any given time per player. (even if used by separate pokemon) — [[User:Zyra|Zyra]] 01:57, 4 June 2017 (UTC)
::Please understand that Pokémon Showdown is coded from scratch and thus could easily have errors that are not consistent with the actual Pokémon games. For this reason, if you want to test mechanics, they ''must'' be tested in the actual games. [[User:Pumpkinking0192|Pumpkinking0192]] ([[User talk:Pumpkinking0192|talk]]) 02:11, 4 June 2017 (UTC)
:::Ok, I understand. — [[User:Zyra|Zyra]] 02:39, 4 June 2017 (UTC)
::::For the record, I have tested this in-game myself before, and this is consistent with the games. However, Pumpkinking is entirely correct about the unreliable nature of Showdown for determining game mechanics. --[[User:SnorlaxMonster|'''Snorlax''']][[User talk:SnorlaxMonster|'''Monster''']] 03:01, 4 June 2017 (UTC)
:::::I'm pretty sure it's what the article says: not one Future Sight ''per player'', but one Future Sight or Doom Desire ''per target slot''. (I think I even tested that.) Actually, I believe that's even consistent with Showdown (and most specifically, even their move description). [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 15:49, 9 June 2017 (UTC)

== Double Battle Behavior ==
There are some important distinctions with this move in Double Battles that I think could be mentioned on this page.
I've only gotten to try this in Gen VII. Unlike most other moves, if there is no Pokémon in the targeted slot, the move will still initialize on the targeted slot without redirecting. This will cause the camera to clip through the middle of the stage because there is no target Pokémon. The timer still counts down on that slot and if a Pokémon fills it in later, the timer doesn't reset. However, if there is no Pokémon in the slot by the time the attack is due to hit, it will vanish without a message.

You can also have multiple Future Sights set up: one on both enemies, and your ally.

[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 01:55, 15 July 2017 (UTC)
:I agree it should be mentioned. I think the article already mentions some of it, but not all of it. Please feel free to add what you have (both here and at {{m|Doom Desire}}). [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 12:32, 15 July 2017 (UTC)

::I'd like to know how consistent this behavior is first though. I don't have any previous-gen games to test it on and see when this started. And I wouldn't have a Jirachi to test Doom Desire with (though it likely behaves the same way).[[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 03:42, 16 July 2017 (UTC)
:::You're absolutely right! Good thinking.
:::Apart from the camera clipping (which really is minor IMO), [http://upcarchive.playker.info/0/upokecenter/dex/index.html%3Flang=en&move=248.html this] (and [http://upcarchive.playker.info/0/upokecenter/dex/index.html%3Flang=en&move=353.html this]) might give you the information you need: that it has always been the case. (I believe I once tested/confirmed it for a few games, including Generation VI; but I certainly didn't watch out for the camera.)
:::Anyway, what you ''could also'' test (when you're interested) is what happens when the Double Battle turns into a single battle during Future Sight's duration (i.e., target an opponent slot and then faint the Pokémon at it, have all but one of yours faint as well, and see whether Future Sight strikes the remaining opponent; this ''could'' even differ depending on whether it's the left or right slot.) [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 09:28, 16 July 2017 (UTC)

:::::The page is quite technical, but if I understood it correctly, ''Remains in effect even if user or the opposing Pokémon leaves the battle '', confirms it? Because even in single battles, if the move is used, and the target switches out or faints, then the move will still hit whoever is there. The reason I mention the camera is because it makes it seem like a situation that wasn't properly accounted for and looks unintentional.
:::::Also, when does a battle actually become a single battle? The fainted targets remain even when there is one Pokémon on each side in a double battle. I tested on an SOS battle and when the empty slot was targeted and nothing filled it, the attack vanished after the turns passed. [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 17:18, 16 July 2017 (UTC)
::::::I worked with that site a lot, so I'm quite used to their wording, and I underestimate how difficult it was to parse it when I started. (Sorry.) The most important line for what you described seems to be ''If there is a Pokémon at the target's position''.
::::::I'm not entirely sure how it works in SOS Battles, but in Doubles, once it's a 1-on-1, it behaves like a single battle (no more target choice, no more {{DL|Damage|Damage calculation|"Targets" penalty for moves like Earthquake}}, etc. [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 17:40, 16 July 2017 (UTC)
:::::::When does it actually do that though? I think even in Trainer battles, when it's down to a 1 on 1, it's still technically a double battle because you still have a choice for target. Even Earthquake seems weaker and the hit marks can still be seen on the empty slots. If a double battle does transform into a single battle, then I don't know what would happen. [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 04:40, 17 July 2017 (UTC)
{{indent}} [[Double Battle#Effects on moves]] says when "there is only one target at the time the move is executed", Earthquake etc. do regular/greater damage. I believe that's still the case, but admittedly introducing the new SOS Battle mechanic might have changed things.

I might try to hunt down what I asked for in the following days myself (as you have no access to different generations); I wanted to test {{m|Leech Seed}} in Doubles for ages, so maybe it's an opportunity to combine these two. (If I do, I'll also try to replicate what you observed, and hunt down when exactly that occurs.) Regardless of the question I had, and whatever its answer is, I believe you may already add what you initially came here for. [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 15:29, 17 July 2017 (UTC)

:Okay. I will add what I know with the expectation that it will be revised for accuracy later. {{unsigned|Koetsu}}
::Thanks.
::In addition to what I just added to the actual article, I also found that the target selection is only omitted in Generation III (there are empty, unselectable slots in Generations IV, empty selectable slots in Generations V and VI, and silhouettes in Generation VII). However, Earthquake etc. apparently do become stronger once it's a 1-on-1 (and they always did).
::(Also, if there's no target at the selected slot, the camera focuses the user in Generation VI. I didn't pay attention in Generation V.) [[User:Nescientist|Nescientist]] ([[User talk:Nescientist|talk]]) 16:22, 21 July 2017 (UTC)

:::Excellent! So now I can see it started with Generation V and that it actually used to redirect in Gen III. The descriptions seem accurate and clearer than before. Now I assume the same goes for Doom Desire?
Thanks for looking into this [[User:Koetsu|Koetsu]] ([[User talk:Koetsu|talk]]) 05:56, 22 July 2017 (UTC)

Future Sight (move)

2017-07-18T05:35:06Z

Koetsu: /* Effect */ Adding details about how it can target empty slots and still attack. It's probably not completely accurate yet, but it's all I have on it now before more can be verified.

{{bad picture|2=Should be replaced with Generation VII images}}
{{MoveInfobox
|n=248
|name=Future Sight
|jname=みらいよち
|jtrans=Future Sight
|jtranslit=Mirai Yochi
|gameimage=Future Sight VI.png
|gameimage2=Future Sight VI 2.png
|gameimagewidth=300
|type=Psychic
|damagecategory=Special
|basepp={{tt|10|15 in Generations II-IV}}
|maxpp={{tt|16|24 in Generations II-IV}}
|power={{tt|120|80 in Generations II-IV; 100 in Generation V}}
|accuracy={{tt|100|90 in Generations II-IV}}
|gen=II
|category=Smart
|appeal=3
|jam=0
|cdesc=Temporarily stops the crowd from getting excited.
|appealsc=2
|scdesc=Earn +2 if the Pokémon performs first in the turn.
|category6=Clever
|appeal6=2
|jam6=0
|cdesc6=Works well if it is the same type as the move used by the last Pokémon.
|touches=no
|protect=no
|magiccoat=no
|snatch=no
|mirrormove=no
|kingsrock=no
|sound=no
|target=anyadjacent
}}
'''Future Sight''' (Japanese: '''みらいよち''' ''Future Sight'') is a damage-dealing {{type|Psychic}} [[move]] introduced in [[Generation II]].

==Effect==
===Generations II to IV===
On the turn Future Sight is selected, this attack will do nothing other than say that the user has foreseen an attack. Two turns later, Future Sight will do damage against the target.

The damage dealt uses the {{stat|Special Attack}} stat of the user and {{stat|Special Defense}} stat of the target ''at the time of move selection'' (not at the time the attack actually hits; if the target is switched out, the attack will hit its replacement but the damage is based on the original target Pokémon). Damage dealt by Future Sight does not have a type; it is not affected by type effectiveness (so can hit {{type|Dark}} Pokémon), does not receive {{STAB}}, and can hit Pokémon with {{a|Wonder Guard}}.

Future Sight cannot land a [[critical hit]] and its damage is not increased by [[Life Orb]]. Future Sight is not affected by {{cat|protection moves}} or {{m|Endure}}. A Pokémon holding a [[Focus Band]] or [[Focus Sash]] can survive Future Sight.

Future Sight fails when used if the target is already set to be hit by Future Sight or {{m|Doom Desire}}. Future Sight can hit the Pokémon that used the move. If Future Sight misses, the miss will not occur until the third turn, and the game will display that the move "failed" rather than "missed".

Future Sight has a base power of 80.

Future Sight can be used as part of a [[Contest combination|Pokémon Contest combination]], with the user gaining extra three appeal points if a certain move ({{m|Calm Mind}}, {{m|Confusion}}, {{m|Kinesis}} or {{m|Psychic}}) was used in the prior turn.

===Generation V===
Future Sight's power is increased from 80 to 100, its accuracy from 90% to 100%, and its PP is reduced from 15 to 10.

Future Sight now calculates its damage when it hits rather than when it is selected. Future Sight uses the user's Special Attack and the hit Pokémon's Special Defense at the time damage is dealt.

It now inflicts damage as a {{type|Psychic}} move; therefore, it is affected by type effectiveness (so cannot affect {{type|Dark}} Pokémon), can receive {{STAB}}, and will not necessarily hit through {{a|Wonder Guard}}. If the user has {{a|Normalize}} or was affected by {{m|Electrify}} when Future Sight hits, it hits as a {{t|Normal}}- or {{type|Electric}} move respectively (regardless of whether this was the case when the move was used); however, it cannot be redirected by {{a|Lightning Rod}} even if it is an Electric-type move. Future Sight can now land a [[critical hit]].

A Pokémon can now endure Future Sight with {{m|Endure}} or {{a|Sturdy}}, in addition to the [[Focus Sash]] and [[Focus Band]]. Future Sight disappears with no message if it would hit the Pokémon that used the move.

===Generation VI===
Future Sight's power was increased again from 100 to 120.

In contests, the move increases from two appeal to six appeal if the move used by the previous Pokémon that round was also a Psychic-type move. This bonus cannot trigger if used first in the round, even if the move used by the last round's last Pokémon was a Psychic-type move.

===Generation VII===
In Double Battles and SOS Battles, Future Sight can still be initialized even if the selected slot does not have an active Pokémon. If a Pokémon occupies the selected slot before the attack can activate, Future Sight will still attack as intended. Future Sight's turn counter will not be reset if the target switches out or faints.

==Description==
{{movedesc|Psychic}}
{{movedescentry|{{gameabbrevss|Stad2}}|A special <sc>Psychic</sc>-type attack. It strikes the target two turns after it is used.}}
{{movedescentry|{{gameabbrev2|GSC}}|An attack that hits on 3rd turn.}}
{{movedescentry|{{gameabbrev3|RSE}}{{gameabbrevss|Colo}}{{gameabbrevss|XD}}|Heightens inner power to strike 2 turns later.}}
{{movedescentry|{{gameabbrev3|FRLG}}|Two turns after this move is used, the foe is attacked psychically.}}
{{movedescentry|{{gameabbrev4|DPPtHGSS}}{{gameabbrevss|PBR}}|Two turns after this move is used, the foe is attacked with a hunk of psychic energy.}}
{{movedescentry|{{gameabbrev5|BWB2W2}} {{gameabbrev6|XYORAS}} {{gameabbrev7|SM}}|Two turns after this move is used, a hunk of psychic energy attacks the target.}}
|}
|}{{left clear}}

==Learnset==
===By [[Level|leveling up]]===
{{Movehead/Level|Psychic|2}}
{{Moveentry/6|064|Kadabra|type=Psychic|1|Human-Like|Human-Like|31|30|42|48|48{{sup/6|XY}} 43{{sup/6|ORAS}}|43|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|065|Alakazam|type=Psychic|1|Human-Like|Human-Like|31|30|42|48|48{{sup/6|XY}} 43{{sup/6|ORAS}}|43|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|096|Drowzee|type=Psychic|1|Human-Like|Human-Like|45|45{{sup/3|RSE}} 47{{sup/3|FRLG}}|53|61|61|61|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|097|Hypno|type=Psychic|1|Human-Like|Human-Like|60|60{{sup/3|RSE}} 57{{sup/3|FRLG}}|69|61|1, 61|1, 61|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|150|Mewtwo|type=Psychic|1|Undiscovered|Undiscovered|44|44{{sup/3|RSE}} 88{{sup/3|FRLG}}|22|15|15|15|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|177|Natu|type=Psychic|type2=Flying|1|Flying|Flying|30|30|36|36|36{{sup/6|XY}} 44{{sup/6|ORAS}}|44|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|178|Xatu|type=Psychic|type2=Flying|1|Flying|Flying|35|35|42|42|42{{sup/6|XY}} 49{{sup/6|ORAS}}|49|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|196|Espeon|type=Psychic|1|Field|Field|||43|43{{sup/5|BW}} 25{{sup/5|B2W2}}|25|25|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|249|Lugia|type=Psychic|type2=Flying|1|Undiscovered|Undiscovered|99|99|79|79|79|79|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|250|Ho-Oh|type=Fire|type2=Flying|1|Undiscovered|Undiscovered|99|99|79|79|79|79}}
{{Moveentry/6|251|Celebi|type=Psychic|type2=Grass|1|Undiscovered|Undiscovered|30|30|64|64|64|64|STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|280|Ralts|type=Psychic|type2=Fairy|1|Amorphous|Amorphous||36|34|39|39{{sup/6|XY}} 32{{sup/6|ORAS}}|32|STAB='''|note=No STAB in Generations III and IV}}
{{Moveentry/6|281|Kirlia|type=Psychic|type2=Fairy|1|Amorphous|Amorphous||40|39|45|45{{sup/6|XY}} 37{{sup/6|ORAS}}|37|STAB='''|note=No STAB in Generations III and IV}}
{{Moveentry/6|282|Gardevoir|type=Psychic|type2=Fairy|1|Amorphous|Amorphous||42|45|53|53{{sup/6|XY}} 40{{sup/6|ORAS}}|40|STAB='''|note=No STAB in Generations III and IV}}
{{Moveentry/6|337|Lunatone|type=Rock|type2=Psychic|1|Mineral|Mineral||43|53|53{{sup/5|BW}} 45{{sup/5|B2W2}}|45{{sup/6|XY}} 41{{sup/6|ORAS}}|41|STAB='''|note=No STAB in Generations III and IV}}
{{Moveentry/6|339|Barboach|type=Water|type2=Ground|1|Water 2|Water 2||36|43|43|43{{sup/6|XY}} 39{{sup/6|ORAS}}|39}}
{{Moveentry/6|340|Whiscash|type=Water|type2=Ground|1|Water 2|Water 2||46|51|51|51{{sup/6|XY}} 45{{sup/6|ORAS}}|45}}
{{Moveentry/6|355|Duskull|type=Ghost|1|Amorphous|Amorphous||49|46|49|49{{sup/6|XY}} 54{{sup/6|ORAS}}|54}}
{{Moveentry/6|356|Dusclops|type=Ghost|1|Amorphous|Amorphous||58|61|61|61{{sup/6|XY}} 1, 64{{sup/6|ORAS}}|1, 64}}
{{Moveentry/6|359|Absol|type=Dark|1|Field|Field||41|41|41{{sup/5|BW}} 36{{sup/5|B2W2}}|36{{sup/6|XY}} 1, 53{{sup/6|ORAS}}|1, 53}}
{{Moveentry/6|385|Jirachi|type=Steel|type2=Psychic|1|Undiscovered|Undiscovered||40|55|55|55|55|STAB='''|note=No STAB in Generations III and IV}}
{{Moveentry/6|436|Bronzor|type=Steel|type2=Psychic|1|Mineral|Mineral|||37|37{{sup/5|BW}} 29{{sup/5|B2W2}}|29|29|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|437|Bronzong|type=Steel|type2=Psychic|1|Mineral|Mineral|||43|43{{sup/5|BW}} 29{{sup/5|B2W2}}|29|29|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|477|Dusknoir|type=Ghost|1|Amorphous|Amorphous|||61|61|61{{sup/6|XY}} 1, 64{{sup/6|ORAS}}|1, 64}}
{{Moveentry/6|480|Uxie|type=Psychic|1|Undiscovered|Undiscovered|||36|36|36|36|36|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|481|Mesprit|type=Psychic|1|Undiscovered|Undiscovered|||36|36|36|36|36|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|482|Azelf|type=Psychic|1|Undiscovered|Undiscovered|||36|36|36|36|36|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|488|Cresselia|type=Psychic|1|Undiscovered|Undiscovered|||38|38|38|38|38|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|493|Arceus|type=Normal|1|Undiscovered|Undiscovered|||60|60|60|60|60|STAB=''|note=No STAB in Generation IV}}
{{Moveentry/6|517|Munna|type=Psychic|1|Field|Field||||31|31|31|31|STAB='''}}
{{Moveentry/6|527|Woobat|type=Psychic|type2=Flying|2|Field|Flying||||36|36|36|36|STAB='''}}
{{Moveentry/6|528|Swoobat|type=Psychic|type2=Flying|2|Field|Flying||||36|36|36|36|STAB='''}}
{{Moveentry/6|574|Gothita|type=Psychic|1|Human-Like|Human-Like||||31|31|31|31|STAB='''}}
{{Moveentry/6|575|Gothorita|type=Psychic|1|Human-Like|Human-Like||||31|31|31|STAB='''}}
{{Moveentry/6|576|Gothitelle|type=Psychic|1|Human-Like|Human-Like||||31|31|31|STAB='''}}
{{Moveentry/6|577|Solosis|type=Psychic|1|Amorphous|Amorphous||||31|31|31|STAB='''}}
{{Moveentry/6|578|Duosion|type=Psychic|1|Amorphous|Amorphous||||31|31|31|STAB='''}}
{{Moveentry/6|579|Reuniclus|type=Psychic|1|Amorphous|Amorphous||||31|31|31|STAB='''}}
{{Moveentry/6|655|Delphox|type=Fire|type2=Psychic|1|Field|Field|||||1, 69|1, 80|STAB='''}}
{{Moveentry/6|678F|Meowstic|type=Psychic|1|Field|Field|||||50|50|STAB='''|form=Female}}
{{Moveentry/6|765|Oranguru|type=Normal|type2=Psychic|1|Field|Field||||||46|STAB='''}}
{{Movefoot|Psychic|6}}

===By {{pkmn|breeding}}===
{{Movehead/Breed|Psychic|2}}
{{Moveentry/6|054|Psyduck|type=Water|2|Water 1|Field|✔|✔|✔|✔|✔|✔|note=Chain breed in Gen II}}
{{Moveentry/6|079|Slowpoke|type=Water|type2=Psychic|2|Monster|Water 1|✔|✔|✔|✔|✔|✔|STAB='''|note=Chain breed; No STAB in Generations II-IV}}
{{Moveentry/6|122|Mr. Mime|type=Psychic|type2=Fairy|1|Human-Like|Human-Like|✔|✔|✔|✔|✔|✔||STAB='''|note=No STAB in Generations II-IV}}
{{Moveentry/6|131|Lapras|type=Water|type2=Ice|2|Monster|Water 1||||✔|✔|✔|note=Chain breed}}
{{Moveentry/6|175|Togepi|type=Fairy|2|Flying|Fairy|✔|✔|✔|✔|✔|✔}}
{{Moveentry/6|183|Marill|type=Water|type2=Fairy|2|Water 1|Fairy|✔|✔|✔|✔|✔|✔|note=Chain breed}}
{{Moveentry/6|203|Girafarig|type=Normal|type2=Psychic|1|Field|Field|✔|✔|✔|✔|✔|✔|STAB='''|note=Chain breed in Gen II; No STAB in Generations II-IV}}
{{Moveentry/6|225|Delibird|type=Ice|type2=Flying|2|Water 1|Field|✔|✔|✔|✔|✔|✔|note=Chain breed in Gen II}}
{{Moveentry/6|325|Spoink|type=Psychic|1|Field|Field||✔|✔|✔|✔|✔|STAB='''|note=No STAB in Generations III and IV}}
{{Moveentry/6|351|Castform|type=Normal|2|Fairy|Amorphous||✔|✔|✔|✔|✔}}
{{Moveentry/6|358|Chimecho|type=Psychic|1|Amorphous|Amorphous|||✔|✔|✔|✔|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|433|Chingling|type=Psychic|1|Amorphous|Amorphous|||✔|✔|✔|✔|STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|439|Mime Jr.|type=Psychic|type2=Fairy|1|Human-Like|Human-Like|||✔|✔|✔|✔||STAB='''|note=No STAB in Generation IV}}
{{Moveentry/6|561|Sigilyph|type=Psychic|type2=Flying|1|Flying|Flying|||||✔|✔|STAB='''}}
{{Movefoot|Psychic|6}}

===Special move===
====[[Generation VII]]====
{{Movehead/Special|Psychic}}
{{Moveentry/1|468|Togekiss|type=Fairy|type2=Flying|2|Flying|Fairy|{{DL|QR Scanner|Island Scan}} - [[Poni Gauntlet]]}}
{{Movefoot|Psychic|1}}

===By {{pkmn2|event}}===
====[[Generation II]]====
{{Movehead/Special|Psychic}}
{{Moveentry/1|131|Lapras|type=Water|type2=Ice|2|Monster|Water 1|{{DL|List of Gotta Catch 'Em All event Pokémon|Future Sight Lapras|New York Pokémon Center}}}}
{{Movefoot|Psychic|1}}

==In other games==
===[[Pokémon Mystery Dungeon series]]===
In [[Pokémon Mystery Dungeon: Red Rescue Team and Blue Rescue Team]], the user will always inflict 35 HP of damage for 3 turns.

In [[Pokémon Mystery Dungeon: Explorers of Time and Explorers of Darkness|Pokémon Mystery Dungeon: Explorers of Time, Darkness]], and [[Pokémon Mystery Dungeon: Explorers of Sky|Sky]], the user will always deal 30 HP damage on any enemies for a set number of turns.

From [[Pokémon Mystery Dungeon: Gates to Infinity]] onward, it will do nothing other than say that the user has foreseen an attack when the move is used. On the next turn, the attack hits the enemy in front of the user, causing a large amount of damage.

===[[Pokémon Conquest]]===
{{Conquestmove
|type=psychic
|grid={{Conquestmove/Grid/rows|span=2|dist=1}}
|stars=4
|pow=45
|acc=100%
|eff=Any target originally within the specified field will receive Psychic-type damage at the start of the opponent's second turn, even if the user faints.
|users={{CSP|576|Gothitelle}}
}}

===[[Pokémon GO]]===
{{GoSpecialAttack
|id=275
|move=Future Sight
|image=no
|type=Psychic
|pow=120
|segments=1
|duration=2.7
|crit=5
|users={{MSP|065|Alakazam}}{{MSP|097|Hypno}}{{MSP|178|Xatu}}{{MSP|196|Espeon}}{{MSP|249|Lugia}}
}}

===Description===
{{movedesc|Psychic}}
{{movedescentry|{{gameabbrevmd|RB}}|The user gains the Set Damage status. In this state, all damage inflicted by the user will remain constant.}}
{{movedescentry|{{gameabbrevss|Conq}}|A hunk of psychic energy attacks the target 2 turns after this move is used.}}
|}
|}{{left clear}}

==In the anime==
{{moveanime|type=psychic|exp=yes|gen=A while after the attack is used, the opponent is blasted by a powerful blast of psychic energy.|image1=Mesprit Uxie Future Sight start.png|image1p=Mesprit and Uxie|image2=Olympia Meowstic Future Sight 2.png|image2p=Meowstic creating the move|image3=Cherry Girafarig Future Sight.png|image3p=Girafarig|image4=Olympia Meowstic Future Sight.png|image4p=Meowstic's Future Sight hitting}}
{{movep|type=psychic|ms=203|pkmn=Girafarig|method=Girafarig's eyes or whole body glows light blue. After a little bit of time passes, the wind blows strong and a sphere of rainbow colored energy comes out of nowhere, striking the opponent. Future Sight has a second ability that allows the user and occasionally its Trainer to see into the future.}}
{{movemid|type=psychic|user=Cherry|user1=Cherry's Girafarig|startcode=EP156|startname=The Psychic Sidekicks!|notes=Debut}}
{{movep|type=psychic|ms=177|pkmn=Natu|method=Natu's eyes shimmer blue. It can then move objects with its mind.}}
{{movemid|type=psychic|user=McKenzie's father|user1=McKenzie's father's Natu|startcode=EP201|startname=Doin' What Comes Natu-rally}}
{{movemid|type=psychic|user=McKenzie|user1=McKenzie's Naughty|startcode=EP201|startname=Doin' What Comes Natu-rally}}
{{movep|type=psychic|ms=480|pkmn=Uxie|method=Uxie raises its hands into the air and a light blue ball of energy with light blue sparks of electricity surrounding it appears above them. Light blue lightning bolts then fire from the ball into the sky and disappear. After a while, light blue lightning bolts appear and shoot out of the sky, hitting the opponent.}}
{{movemid|type=psychic|user=Uxie (anime)|user1=A wild Uxie|startcode=DP151|startname=The Needs of the Three!}}
{{movep|type=psychic|ms=481|pkmn=Mesprit|method=Mesprit raises its hands into the air and a light blue ball of energy with light blue sparks of electricity surrounding it appears above them. Light blue light bolts then fire from the ball into the sky and disappear. After a while, light blue lightning bolts appear and shoot out of the sky, hitting the opponent.}}
{{movemid|type=psychic|user=Mesprit (anime)|user1=A wild Mesprit|startcode=DP151|startname=The Needs of the Three!}}
{{movep|type=psychic|ms=678F|pkmn=Meowstic|method=Meowstic extends its ears, and the eye-like patterns on its inner ears glow blue. Meowstic creates four or five wormholes then blasts of electrified psychic energy through the wormholes and in between the wormholes. After a certain amount of time, the wormholes appear around the target, barraging the target with the blasts of electrified psychic energy.}}
{{movebtm|type=psychic|user=Olympia|user1=Olympia's Meowstic|startcode=XY092|startname=Cloudy Fate, Bright Future!}}

==In the manga==
===In the Pokémon Adventures manga===
{{movemanga|type=psychic|exp=yes|gen=The user attacks the opponent in the future, and the opponent feels the effects of the attack a while after the attack is used.|image1=Natee Future Sight 1.png|image1p=Setting up|image2=Natee Future Sight 2.png|image2p=Being hit}}
{{movep|type=psychic|ms=177|pkmn=Natu|method=Natu's eyes glitter and it faces where the opponent will be. Once the opponent gets to that place, it gets slashed by an invisible energy beam.}}
{{movebtmManga|type=psychic|user=Crystal (Adventures)|user1=Crystal's Natee|startcode=PS166|startname=Lugia and Ho-Oh on the Loose (Part 2)|notes=Debut}}

==In other generations==
===Core series games===
{{Movegen
|type=Psychic
|genII=Future Sight II
|genIII=Future Sight III
|genIV=Future Sight IV
|genV=Future Sight V
}}
===Spin-off series games===
{{Movegen
|type=Psychic
|Stad2=Future Sight Stad2
|Colo=Future Sight Colo
|XD=Future Sight XD
|PBR=Future Sight PBR
}}

{{Movegen
|type=Psychic
|PMDRB=Future Sight PMD RB
}}

==In other languages==
{{Langtable|color={{psychic color}}|bordercolor={{psychic color dark}}
|zh_yue=預知未來 ''{{tt|Yuhjī Meihlòih|Future Foresight}}'' {{tt|*|Games}} 先知 ''{{tt|Sīnjī|Know First / Prophet}}'' {{tt|*|Pre-Gen VII Media}}
|zh_cmn=預知未來 / 预知未来 ''{{tt|Yùzhī Wèilái|Future Foresight}}'' {{tt|*|Games}} 先知 ''{{tt|Xiānzhī|Know First (Prophet)}}'' {{tt|*|Pre-Gen VII Media}}
|cs=Budoucnost
|nl=Toekomstblik
|fr=Prescience
|de=Seher
|el=Ενόραση
|id=Ramalan Masa Depan
|it=Divinazione
|ko=미래예지 ''Mirae Yeoji''
|pl=Wizja Przyszłości
|pt_br=Visão do Futuro (games, {{series|XY}}-present, TCG) Visão Futura (early anime)
|ro=Privirea în Viitor
|sr=Predskazanje
|es_eu=Premonición
|es_la=Vista al Futuro
|vi=Dự Đoán Tương Lai
}}
{{-}}

{{Project Moves and Abilities notice}}

[[de:Seher]]
[[fr:Prescience]]
[[it:Divinazione (mossa)]]
[[ja:みらいよち]]
[[pl:Future Sight]]
[[zh:预知未来（招式）]]

Talk:Future Sight (move)

2017-07-18T05:19:43Z

Koetsu: /* Double Battle Behavior */

Talk:Future Sight (move)

2017-07-17T04:40:22Z

Koetsu: /* Double Battle Behavior */

Talk:Future Sight (move)

2017-07-16T17:18:42Z

Koetsu: /* Double Battle Behavior */

Talk:Future Sight (move)

2017-07-16T03:42:35Z

Koetsu: /* Double Battle Behavior */

Talk:Future Sight (move)

2017-07-16T03:42:18Z

Koetsu: /* Double Battle Behavior */

Talk:Future Sight (move)

2017-07-15T01:55:41Z

Koetsu: