Ranger Wiki · Unofficial

How capturing changed across the Ranger games

From the Pokemon Ranger Wiki · Across the series

Pokemon Ranger gives each Pokemon a fixed loop count. Shadows of Almia and Guardian Signs give it a capture gauge instead, so the loops you need depend on your Styler. All three compared, from each game's own data.

The three games side by side

Pokemon Ranger (2006)Shadows of Almia (2008)Guardian Signs (2010)
What a capture fillsA fixed loop count per species Source 1: Cross-checkedA capture gauge per species, filled by each loop Source 2: Read in codeA capture gauge per species, filled by each loop Source 3: Read in code
Per species1 to 32 loops, 6 in the middle Source 1: Cross-checkedGauge 40 to 40,000, 1,680 in the middle Source 2: Read in codeGauge 12 to 40,000, 2,070 in the middle Source 3: Read in code
Styler levels1 to 20 Source 4: From the game1 to 50 Source 5: Read in code1 to 99 Source 6: Read in code
What each loop addsOne loop Source 1: Cross-checkedCapture power, 10 at level 1 to 205 at level 50, plus bonuses Source 2: Read in codePower, 10 at level 1 to 327 at level 99, plus 5 per Power Plus; the full formula is not decoded Source 7: Read in code
Most energy4 at level 1 to 60 at level 20 Source 4: From the game10 at level 1 to 104 at level 50 unconfirmedSource 8: Best reading (unconfirmed), energy and EXP columns10 at level 1 to 164 at level 99, plus 5 per Energy Plus Source 6: Read in code
Line lengthGrows with the level: the game enforces 39 steps at level 1 to 53 at level 20 Source 4: From the game, each step 11 pixels Source 9: Read in code; the status screen shows 100 to 200, a figure nothing else reads (Styler Energy and line length)Not a level stat; Power-up Data lengthens it unconfirmedSource 10: Best reading (unconfirmed), line length448, plus 16 per Line Plus Source 11: Read in code
When the loops stopLift the Styler before the capture and the loops drawn are lost Source 12: From the gameThe gauge drains, at a rate not found yet unconfirmedSource 13: Best reading (unconfirmed), drainThe gauge refills by a set amount per species, after a wait Source 3: Read in code
Assists on the captureThe assist's matchup against the target's group sets how long it holds the target; see How Poke Assists work Source 14: From the gameNormal, Fire, Fighting and Dark add to each loop, scaled by a matchup chart Source 15: Read in codeEffects keyed by assist type, variant and level; not decoded Source 16: Read in code

Pokemon Ranger: a fixed loop count

Each Pokemon needs a set number of loops, whatever the Styler's level Source 1: Cross-checked; a lift with the full count always captures (How capture works). Lapras joins without a capture, so it is left out. How the other 212 entries spread:

LoopsPokemon
1 to 348
4 to 674
7 to 944
10 to 1430
15 to 3216

Almia and Guardian Signs: a gauge to fill

Both later games give each Pokemon a gauge instead, on the same scale, up to 40,000 Source 2: Read in code Source 3: Read in code. The loops you need depend on the Styler: in Almia each loop adds the Styler's capture power, 10 at level 1 and 205 at level 50 Source 5: Read in code. Guardian Signs' Power runs from 10 to 327, but how it turns into gauge is not decoded yet Source 7: Read in code. How the gauges spread (Almia's gauge-0 rows left out):

GaugeShadows of AlmiaGuardian Signs
0 to 99119
100 to 4995266
500 to 1,9999374
2,000 to 9,99986136
10,000 to 40,0002721

The 69 Pokemon in all three games

Ranger's loops next to the two gauges. Almia's loops at Styler levels 1 and 50 assume no assist, no Power-up Data and no drain unconfirmedSource 17: Best reading (unconfirmed), fewest loops with no drain. For Guardian Signs the gauge and refill are shown, since its loop math is not decoded. Click a column head to sort.

PokemonRanger loopsAlmia gaugeAlmia loops, Lv. 1Almia loops, Lv. 50GS gaugeGS refill
Charmander37207241,254+4
Charmeleon52,000200101,800+5
Charizard1640,00040001966,750+17
Blastoise178508554,810+13
Pikachu26456541,056+3
Raichu31,54015481,904+5
Zubat28491120+1
Golbat71,2401247756+2
Oddish5312322300+1
Gloom8912925640+2
Vileplume92,500250131,620+5
Mankey53843921,276+4
Primeape103,750375192,070+6
Geodude8126131180+1
Graveler11700704480+2
Golem154,550455232,070+6
Magnemite2180181400+2
Magneton31,900190103,066+8
Dodrio41,75017592,580+7
Gastly54041672+2
Haunter61,40014073,066+8
Gengar75,200520263,700+10
Voltorb5252262380+1
Koffing8980985160+1
Horsea32,09020911264+1
Seadra52,375238122,967+8
Scyther31,68016891,800+5
Electabuzz62,070207113,611+10
Magmar61,14011463,066+8
Vaporeon152,900290152,580+7
Jolteon83,780378194,818+13
Flareon131,920192103,696+10
Spinarak3903915120+1
Ariados63,51035118756+2
Crobat43,7503751916,000+9
Pichu16671120+1
Espeon53,25032516640+2
Umbreon72,900290153,066+8
Murkrow91,4881498140+1
Gligar5448453450+2
Scizor124,050405202,000+6
Sneasel31,960196101,254+4
Swinub51,36413773,140+8
Piloswine74,030403203,611+10
Mantine83003022,070+6
Skarmory31,71517292,240+6
Houndoom62,112212113,504+9
Kingdra610,0001000492,967+8
Larvitar34164231,600+5
Pupitar131,30013072,070+6
Tyranitar118,750875432,600+7
Celebi312,000120059300+1
Sceptile82,730273144,368+11
Blaziken83,750375194,255+11
Wingull325226250+1
Pelipper121,92019210400+2
Ralts4774784240+1
Kirlia51,2001206936+3
Gardevoir93,900390203,864+10
Makuhita59899951,110+3
Hariyama122,320232123,400+9
Sharpedo11910915300+1
Numel54484531,800+5
Camerupt103,720372192,070+6
Dusclops92,83528414756+2
Absol54,500450225,000+13
Bagon51,84018492,700+7
Shelgon62,160216111,800+5
Salamence2235,00035001714,810+13

Sources

Numbers come from each game's own data on a US copy, and rules from each game's code as far as it has been read, unless a sentence names another source. Nothing is copied from another wiki; Serebii's lists were only compared.

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

  1. Cross-checked. species-record.md: the 60-byte species record (loops to capture, capture EXP, size class, hop speed, turn speed); Pokemon_GetLoopsToCapture, Pokemon_GetCaptureExp, Pokemon_IsSizeSmall, Pokemon_GetTurnSpeed. Proven. Back to text: a b c d
  2. Read in code. The battle species table's capture gauge column, which sets up the target's gauge (CBattleEnemyGauge). Gain per loop (ov1_0212CD6C): the Styler's capture power times a charge factor of 1, 2 or 3, plus the Normal, Fire or Fighting assist's value (minus the Dark assist's), times the matchup factor for those four assists, plus Power-up Data (3, 5 or 7). Both read in code. Back to text: a b c d
  3. Read in code. The capture table: the gauge (func_ov003_020F1E60; the gauge shown is 100 times the current value over it), the refill amount, the wait before it starts and the frames between refills (func_ov003_020EFD88), all read in code. Back to text: a b c d
  4. From the game. styler-rank-stats.md: Styler Energy and the line length limit by level; StylerLevel_GetLineLength, Player_RecomputeStylerStats. Proven; the trimming of old line points is read in code. Back to text: a b c
  5. Read in code. The Styler level table (levels 1 to 50: energy, capture power and EXP), read through its accessors in code; the capture loop asks it for the capture power at the current Styler level. Back to text: a b
  6. Read in code. The Styler level table: EXP threshold (func_0205D8C4), Energy (func_0205D7A0) and Power (func_0205D804) at each level 1 to 99, read in code. The thresholds stop rising at level 52 (60,000); whether EXP itself is capped there is not traced. Back to text: a b
  7. Read in code. The Styler level table: Power at each level, plus 5 per Power Plus (func_0205D804, read in code). How Power, charge and Latent Power turn into gauge per loop is not decoded yet. Back to text: a b
  8. Best reading (unconfirmed) (energy and EXP columns). Same as source 5. Back to text
  9. Read in code. The decompilation's reading of the game's code, not yet rebuilt and proven. Back to text
  10. Best reading (unconfirmed) (line length). The Styler level table stores energy, capture power and EXP, but no line length. The in-game glossary says only Power-up Data makes the line longer. The lengths are not found yet. Back to text
  11. Read in code. The Styler Modification upgrades: the seven top steps, from the table func_0205D734 reads. Energy and Power add 5 per step, and the line is 448 plus 16 per Line Plus (func_0205D860), all read in code. The other four are the menu's own descriptions, summarized; how much each of their steps does is not decoded. Back to text
  12. From the game. capture-loop.md, capture-release.md, capture-state.md: crediting a loop, the two-ray inside test, the lift, letting go; Capture_CreditLoop, Capture_CreditDrawnLoop, Capture_ResolveLine. Proven; the release handler is read in code. Back to text
  13. Best reading (unconfirmed) (drain). The in-game glossary says one assist tires the target so its gauge stops draining, so the gauge drains over time. The drain rate is not found yet. Back to text
  14. From the game. The game's own data tables, read from a US copy of Pokemon Ranger (DS, 2006) each time the wiki is built. Back to text
  15. Read in code. The assist matchup chart in the capture code (1.5 strong, 0.75 weak, no immunities), read in code; the in-game glossary's lists of weak matchups agree with its 0.75 cells. Back to text
  16. Read in code. The Poke Assist effect table (631 rows): its key, the assist type and the species' variant times 10 plus the assist level, is read in code (func_02041F84). The fields of each row are not named yet; the Browser labels two of them Power and Recovery Time. Back to text
  17. Best reading (unconfirmed) (fewest loops with no drain). Same as source 2. Back to text

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