Ranger Wiki · Unofficial

How capture works

From the Pokemon Ranger Wiki · How it works · Pokemon Ranger (DS, 2006)

To capture a Pokemon, circle it with as many loops as it needs, then lift the stylus before anything touches your line. A full count always captures: the game rolls a number at the lift, but the roll can never change the result.

The short version

How many loops each Pokemon needs is on its own page, from the Browser. This page is about Pokemon Ranger; the later games fill a capture gauge instead (How capturing changed).

What counts as a loop

When the newest piece of your line crosses an older piece, the part in between is a closed loop, and every Pokemon inside it gets one loop at the same moment. Source 1: From the game

The game tests the newest piece pushed 4 pixels further on, so a loop closes a moment before your stylus reaches the old line. Source 9: From the game At most one loop closes a frame, and a loop needs at least 4 points of line. Source 9: From the game

The line is not emptied when a loop closes: it is cut back to where it crossed and goes on, so one stroke can close loop after loop. Source 9: From the game Each closed loop stays on screen as a grey outline for 39 frames, swelling and fading. Source 9: From the game

A Pokemon is inside when two rays from it, one to the left edge of the screen and one to the top, both cross the loop an odd number of times. Source 1: From the game The rays start from its hit centre, on its body where you see it, even while it hovers or hops; the line test below uses the same point. Source 10: From the game

Each Pokemon in a loop also records how many shared it, for the group bonus on Capture EXP. Source 1: From the game

The Styler tracks up to 10 Pokemon at once, each with its own count. A newcomer takes the first free slot and starts at 1; if all 10 slots hold Pokemon still in play, its loop does not count. Source 11: From the game

A count of 100 or more captures on the spot, with no lift, and a count stops at 255. Source 11: From the game No species needs anywhere near 100 loops, so you will not see this. unconfirmedSource 12: Best reading (unconfirmed)

Loops do not count while a capture target is in certain behaviour states. Source 13: From the game One of them lasts 3 to 5 seconds (180 frames plus a random 0 to 119). Source 14: Read in code

With a Fighting Poke Assist active, one drawn loop can count 2 or 3 times against some groups, one extra loop every quarter of a second (How Poke Assists work). Source 1: From the game

With no Styler Energy left, the Styler draws nothing at all: every touch of the screen is ignored. Source 9: From the game

The game highlights a Pokemon that has loops on it, faster as it nears its count. Source 6: From the game, the rule unconfirmedSource 7: Best reading (unconfirmed), how it looks

Loops still neededIt lights up
3every 8th frame
2every 4th frame
1every other frame
none (full)all the time

Source 6: From the game It also lights for one frame each time a loop counts. Source 6: From the game So a steady glow means a lift will capture it now. unconfirmedSource 15: Best reading (unconfirmed)

The line against a Pokemon

Every frame, after the loop test and the lift, the game checks the line against each Pokemon that loops can count on and that is not already being captured (a diver under the water is skipped). Source 4: From the game

It checks a circle with a radius of 5 pixels (Ralts, the smallest) to 31 (Rayquaza, the largest); 113 of the 213 Browser entries have 7 to 10 (species record byte +0x04). Source 4: From the game, the rule Source 16: From the game, the values The circle sits on the body, not round the feet: its centre is the Pokemon's ground spot raised by its height, moved by record bytes +0x05 (sideways, mirrored while it faces right) and +0x06 (up) and by its animation, then 8 pixels left and 3 up. Source 4: From the game Each Pokemon page gives its own circle.

The line touches when its nearest point is within the radius of the centre, counted in whole pixels. A centre more than the radius off the 256 by 192 screen never touches. Source 4: From the game Run under emulation, the game's own code gave the same answer as these rules for every species on all 106,500 test lines. Source 17: From the game

What a touch does:

  • The line breaks, unless the Pokemon is in the Fire, Rock or Flying reaction of a Poke Assist. Source 4: From the game
  • It costs energy only during the Pokemon's charge or from a line attacker: its stored damage divided by 10, rounded down. Only the strongest hit of a frame counts, Pokemon and other objects together; any other touch breaks the line for free (Line breaks and damage). Source 4: From the game
  • During its field-wide attack, a Pokemon breaks the line wherever it is, with no circle test. Source 4: From the game
  • The Pokemon that touched is marked, unless it is attacking, reacting to an assist, diving, leaving, being captured or is a Salamence on the ground. Source 4: From the game

What the touched Pokemon does next depends on the species. Most spin two whole turns in about half a second (31 frames) and then decide again. Source 18: From the game, the spin unconfirmedSource 19: Best reading (unconfirmed), frames as seconds 62 Browser Pokemon attack back at once instead, if they can, and a few run for the edge, vanish or rest: the full list is in What a touched Pokemon does. Source 6: From the game, the rule Source 16: From the game, the species

The code also holds a push for one assist type: instead of breaking the line, the Pokemon is shoved away from the line's first point and spins dizzily for about 2 seconds. No Pokemon gives that assist, so it never happens in play. Source 4: From the game, the push unconfirmedSource 20: Best reading (unconfirmed), never in play

Other short states

Three more short states exist; what starts them is only partly traced. Source 4: From the game, the states Source 21: Read in code, who starts them

The friends a Poke Assist brings

Three assists send a friend Pokemon onto the field instead of starting a timer. It walks to the middle at twice its run speed, does its part, walks off toward the far side and flies away. Source 4: From the game, the walk unconfirmedSource 23: Best reading (unconfirmed), which assist each belongs to

The lift settles it

When you lift the stylus, the line vanishes at once and the game lists every tracked Pokemon that is active, not already taken and looped at least once. Source 2: From the game

Each listed Pokemon with its full loop count is captured. Any other is let go and drops back to 0. Source 2: From the game So lifting one loop early throws away all the loops you drew, not just the last. Source 27: From the game

Two exceptions:

Nothing drains between loops: a count only changes at a lift, a broken line, or another reset such as the Pokemon leaving the field. Source 3: From the game, the settle paths Source 30: Read in code, no other writer in the main code

After the lift, frame by frame

A captured Pokemon rocks in place for 2 seconds (120 frames), plus 8 frames for each Pokemon before it on the same line, so a group capture finishes one Pokemon after another. Source 27: From the game, the frames unconfirmedSource 31: Best reading (unconfirmed), frames as seconds Then the capture is decided, it rocks half a second more and rises straight up off the top of the screen. Source 27: From the game From the lift to gone takes about 3 seconds (182 frames) for the first Pokemon of a line. Source 27: From the game, the frames unconfirmedSource 31: Best reading (unconfirmed), frames as seconds Diglett and Dugtrio dig away up the screen instead. Source 27: From the game, the rule unconfirmedSource 32: Best reading (unconfirmed), the species

Its capture EXP is paid only once it has left the screen, one Pokemon at a time. Source 27: From the game The Pokemon never flashes or changes colour while it is captured; the moments you see are the loop effect, the rocking, the rise and the vanish. Source 27: From the game

A Pokemon you let go rocks for 1 second (60 frames, plus 8 per Pokemon before it), then jumps up and lands with a bounce, and its loops are gone. Source 27: From the game, the frames unconfirmedSource 31: Best reading (unconfirmed), frames as seconds The closer it came, the higher it jumps:

Share of its loops you had drawnThe jump rises for
under a tenthno jump
a tenth to under 40 percent5 frames
40 to 59 percent10 frames
60 to 69 percent15 frames
70 to 79 percent20 frames
80 to 89 percent25 frames
90 percent or more30 frames

Source 27: From the game So a big jump means you lifted just short. unconfirmedSource 33: Best reading (unconfirmed) After the jump it goes back to roaming, and a few species go into a move of their own. Source 27: From the game, the release Source 6: From the game, the special states

The capture check, and why luck never matters

A Pokemon with all its loops is captured every time. Source 5: From the game The game does roll 0 to 99 for each listed Pokemon at the lift and asks whether its loop progress is above the roll. Source 3: From the game But progress is only ever 0 (not enough loops) or 100 (enough), so the roll never changes the outcome. Source 5: From the game

Deoxys is the exception. The species table has seven Deoxys rows, and only the first (0xe5) can pass the normal check; the other six (rows 0xe6 to 0xeb) never do. Source 27: From the game, the row test Source 34: From the game, the row count The first reads as the Normal Forme, the others as the Attack, Defense and Speed Forme rows, two each. unconfirmedSource 35: Best reading (unconfirmed)

A forme row with all its loops is let go with animations of its own. Then three of the six leave the field and set a flag on it, and the other three go into a state of their own. Source 27: From the game The best reading: in the Deoxys mission, filling a forme with loops ends that forme's part of the fight instead of catching it. unconfirmedSource 33: Best reading (unconfirmed)

What you see over a Pokemon

The number over a Pokemon shows the loops it still needs, then its capture EXP (up to 9999) once it has enough. Source 27: From the game It stays 1 second after each loop and 4 seconds after a capture. Source 36: From the game, 60 and 240 frames unconfirmedSource 37: Best reading (unconfirmed), frames as seconds Each time it restarts, it hops and flashes white for 4 frames. Source 27: From the game Up to 8 of these counters show at once, though the Styler tracks 10 Pokemon. Source 36: From the game

Its four colours: blue normally, pink during a Fighting assist until the target is met, then green if the last loop held 2 or more Pokemon, orange if it held one. Source 38: From the game, the values unconfirmedSource 39: Best reading (unconfirmed), that they are the colours you see

Strange corners

Try it

The loop lab

Loop lab · Styler level 20Lyra Forest (background: the wiki's choice)
Draw one loop around

To scroll the page, swipe outside the screen.

EXP receipt

Paid at the lift. Three loops around all four, then a lift, pays each one double its base.

PokemonLoopsGroupExtraEXP
Pichu0 / 1000
Pikachu0 / 2000
Bulbasaur0 / 3000
Chikorita0 / 3000
Total captured0

Not known yet

How this is known

The rules come from the game's decompilation: each named function was rebuilt in C and checked against the original on thousands of generated inputs; "read in code" rules come from functions read but not yet rebuilt. The line test and the touch answers were also run as the game's own code under emulation for every species. Numbers come from the species table. The Deoxys row count follows the pre-release review, which corrected the first findings' six.

See also

Sources

Numbers come from the game's own data on a US copy of Pokemon Ranger (DS, 2006), and rules from a decompilation of its code, unless a sentence names another source. Nothing is copied from another wiki.

A marker's shape shows how sure a fact is: From the game Read in code Best reading (unconfirmed). How this wiki is made

  1. From the game. The drawn loop and its two-ray inside test; Fighting extra loops. The decompilation's findings: assist-matchup.md (Capture_CreditDrawnLoop, Capture_QueueFightingExtraLoops). Back to text: a b c d e f
  2. From the game. The stylus lift, all-or-nothing mode, the Psychic diversion, the capture check. The decompilation's findings: capture-release.md (Capture_ResolveLine, Pokemon_PassesCaptureCheck). The capture's end frame by frame (the rocking, the decision, the rise, the vanish), letting a Pokemon go, the Deoxys rows test, the Entei dismissal, when the EXP is paid, the counter's frames. The decompilation's findings: capture-success.md (Pokemon_HandleState5c, Pokemon_RockSprite, Pokemon_ReleaseFromCapture, Pokemon_IsRowE6ToEb, Pokemon_SendOtherKind2Away, MapSnatch_PayCaptureExp, LoopCounter_UpdateRecord). Back to text: a b c
  3. From the game. The stylus lift, all-or-nothing mode, the Psychic diversion, the capture check. The decompilation's findings: capture-release.md (Capture_ResolveLine, Pokemon_PassesCaptureCheck). Back to text: a b c d e
  4. From the game. The line against the Pokemon (a circle per species, its centre, the whole-pixel test, what a touch does), the states 0x42, 0x46, 0x48 and 0x49, and the friends a Poke Assist brings onto the field (states 0x6c to 0x72); answers 68 to 71. The decompilation's findings: hit-test.md (Pokemon_SetHitCircle, Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_MarkLineTouched, Pokemon_HandleState42 to Pokemon_HandleState72). Back to text: a b c d e f g h i j k l m n o p q r
  5. From the game. Decomp findings, "Answers for the wiki" (answers 5, 6, 7, 52 to 62) and the capture tables. The decompilation's findings: README.md. Back to text: a b c d
  6. From the game. What a line touch sets off (the spin, the species' own answers), the capture blink. The decompilation's findings: touch.md (Pokemon_StartTouchReaction, Pokemon_TakeSpeciesState, Pokemon_UpdateCaptureBlink). Back to text: a b c d e f g
  7. Best reading (unconfirmed) (how it looks). Same as source 6. Back to text: a b
  8. From the game. The stylus lift, all-or-nothing mode, the Psychic diversion, the capture check. The decompilation's findings: capture-release.md (Capture_ResolveLine, Pokemon_PassesCaptureCheck). Pre-release review corrections M8 (seven Deoxys rows, six excluded), F7 (state 0x20 is B), F8 (no decay is A for the settle paths, B for the search). The pre-release review of the decompilation. Back to text
  9. From the game. The stylus, when a line closes into a loop, what happens to the loop and the rest of the line, the line's frame order. The decompilation's findings: line-bosses.md (Capture_ReadStylus, CaptureLine_FindLoop, CaptureLine_TickLoops, CaptureLine_Update). Back to text: a b c d e
  10. From the game. The drawn loop and its two-ray inside test; Fighting extra loops. The decompilation's findings: assist-matchup.md (Capture_CreditDrawnLoop, Capture_QueueFightingExtraLoops). The line against the Pokemon (a circle per species, its centre, the whole-pixel test, what a touch does), the states 0x42, 0x46, 0x48 and 0x49, and the friends a Poke Assist brings onto the field (states 0x6c to 0x72); answers 68 to 71. The decompilation's findings: hit-test.md (Pokemon_SetHitCircle, Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_MarkLineTouched, Pokemon_HandleState42 to Pokemon_HandleState72). Back to text
  11. From the game. The 10 capture slots, the count cap, capture on the spot. The decompilation's findings: capture-state.md (ObjRef_IsValid, Pokemon_SetLoopCountAndExpBonus). Back to text: a b
  12. Best reading (unconfirmed). The species table (loops to capture at record +0x1f, the Deoxys and Entei rows). The game's own data, read at build time from a US copy of the game. Back to text
  13. From the game. States where loops do not count. The decompilation's findings: ai-core.md (Pokemon_SetState; state 0x20 handler func_02030f0c read only). Back to text
  14. Read in code. States where loops do not count. The decompilation's findings: ai-core.md (Pokemon_SetState; state 0x20 handler func_02030f0c read only). Pre-release review corrections M8 (seven Deoxys rows, six excluded), F7 (state 0x20 is B), F8 (no decay is A for the settle paths, B for the search). The pre-release review of the decompilation. Back to text
  15. Best reading (unconfirmed). Same as source 6. Back to text
  16. From the game (the values; the species; the speeds; the EXP). Same as source 12. Back to text: a b c d
  17. From the game. The game's own capture field code run under emulation for all 213 field species (the line test on 106,500 test lines, and what a touch sets off), matching the rules here. Code reading and emulator checks for this wiki. Back to text
  18. From the game (the spin). What a line touch sets off (the spin, the species' own answers), the capture blink. The decompilation's findings: touch.md (Pokemon_StartTouchReaction, Pokemon_TakeSpeciesState, Pokemon_UpdateCaptureBlink). The game's own capture field code run under emulation for all 213 field species (the line test on 106,500 test lines, and what a touch sets off), matching the rules here. Code reading and emulator checks for this wiki. Back to text
  19. Best reading (unconfirmed) (frames as seconds). Same as source 6. Back to text
  20. Best reading (unconfirmed) (never in play). Same as source 4. Back to text
  21. Read in code (who starts them; what leads to it). Same as source 4. Back to text: a b
  22. Best reading (unconfirmed) (what starts it). Same as source 4. Back to text
  23. Best reading (unconfirmed) (which assist each belongs to). Same as source 4. Back to text
  24. Best reading (unconfirmed) (that it is Electric's friend). Same as source 4. Back to text
  25. Best reading (unconfirmed) (that it is Dark's friend). Same as source 4. Back to text
  26. Best reading (unconfirmed) (that it is Psychic's friend). Same as source 4. Back to text
  27. From the game. The capture's end frame by frame (the rocking, the decision, the rise, the vanish), letting a Pokemon go, the Deoxys rows test, the Entei dismissal, when the EXP is paid, the counter's frames. The decompilation's findings: capture-success.md (Pokemon_HandleState5c, Pokemon_RockSprite, Pokemon_ReleaseFromCapture, Pokemon_IsRowE6ToEb, Pokemon_SendOtherKind2Away, MapSnatch_PayCaptureExp, LoopCounter_UpdateRecord). Back to text: a b c d e f g h i j k l m n o
  28. Best reading (unconfirmed) (which fights use it). Same as source 3. Back to text
  29. Read in code. Same as source 3. Back to text: a b
  30. Read in code (no other writer in the main code). Pre-release review corrections M8 (seven Deoxys rows, six excluded), F7 (state 0x20 is B), F8 (no decay is A for the settle paths, B for the search). The pre-release review of the decompilation. Back to text
  31. Best reading (unconfirmed) (frames as seconds). Same as source 27. Back to text: a b c
  32. Best reading (unconfirmed) (the species). Same as source 27. Back to text
  33. Best reading (unconfirmed). Same as source 27. Back to text: a b c
  34. From the game (the row count). The species table (loops to capture at record +0x1f, the Deoxys and Entei rows). The game's own data, read at build time from a US copy of the game. Pre-release review corrections M8 (seven Deoxys rows, six excluded), F7 (state 0x20 is B), F8 (no decay is A for the settle paths, B for the search). The pre-release review of the decompilation. Back to text
  35. Best reading (unconfirmed). Same as source 30. Back to text
  36. From the game. Crediting one loop, the loop counter over a Pokemon, its colours and timers. The decompilation's findings: capture-loop.md (Capture_CreditLoop, LoopCounter_Show, LoopCounter_ShowCaptured). Back to text: a b
  37. Best reading (unconfirmed) (frames as seconds). Same as source 36. Back to text
  38. From the game (the values). Crediting one loop, the loop counter over a Pokemon, its colours and timers. The decompilation's findings: capture-loop.md (Capture_CreditLoop, LoopCounter_Show, LoopCounter_ShowCaptured). Pre-release review corrections M8 (seven Deoxys rows, six excluded), F7 (state 0x20 is B), F8 (no decay is A for the settle paths, B for the search). The pre-release review of the decompilation. Back to text
  39. Best reading (unconfirmed) (that they are the colours you see). Same as source 36. Back to text
  40. From the game (the rule). The capture reset, Entei's orbiting objects and its row change. The decompilation's findings: exp-bonus.md (Pokemon_ResetCaptureProgress, Pokemon_SetLoopCountAndExpBonus). Back to text
  41. Read in code (the count of 10). Same as source 40. Back to text
  42. Best reading (unconfirmed) (that it is Entei). Same as source 40. Back to text
  43. Best reading (unconfirmed). Same as source 40. Back to text
  44. Best reading (unconfirmed) (that the row is Entei). Same as source 27. Back to text
  45. Best reading (unconfirmed) (that both rows are Charizard). Same as source 5. Back to text
  46. Best reading (unconfirmed) (the species). Same as source 6. Back to text
  47. Best reading (unconfirmed). Same as source 3. Back to text

What changed and why

  • Deoxys has seven data rows, not six: six of them never pass the normal capture check, and the first, the Normal Forme, can be captured the usual way. Why: The pre-release review of the decompilation counted the rows again and corrected the first findings.

Your cartridge says otherwise? File a field report.

Every number here is read from the game, so the wiki is not crowd-edited. Each report is checked against the game's data and code. If you are right, the page is fixed, says what changed and why, and can thank you by name.

File a field report

Your Loopbook

Read to the end and this page joins your Loopbook, the list of what you have read on this device.

Open your Loopbook