Ranger Wiki · Unofficial

How Poke Assists work

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

A Poke Assist runs on two clocks: most assists last their power in seconds on your Styler, and a Pokemon they hit is held for a time set by the assist's matchup against its group. Most assists reach that Pokemon through effects they add to your line, such as gusts, shots and bubbles, and none of those effects ever breaks the line.

The short version

Every assist each species gives, with its power, is listed on Poke Assists.

Clock one: how long the assist runs

Assist typesTimerMark
Fighting, Poison, Ground, Flying, Bug, Rock, Ghost, Fire, Water, Grass, Iceits power in seconds (power x 60 frames)Source 2: From the game
Electricno timer: the power is how much energy it recharges, 5, 15 or allSource 9: Read in code Source 10: Cross-checked
Psychicthe stored power is never used as a timer on the capture fieldSource 9: Read in code
Dark, the Plusle partnerthe power counts frames, not secondsSource 2: From the game

Source 11: From the game, the data

While it runs, Fire, Poison, Ground, Grass and Ice leave effects along your line every 16 pixels (Fire on nearly every frame the line grows; Ice also about once a second, even with the stylus still). Source 2: From the game unconfirmedSource 12: Best reading (unconfirmed), what they look like Fighting changes how loops count and Dark the line's length (below). Source 13: From the game

The timer starts only once the friend that brings the assist has hopped to the middle of the screen, landed and jumped back off it: the assist begins when it is 24 units up, 16 frames after landing. Source 14: From the game

What each assist does on your line

Each assist type puts its own effects on the line while it runs. Source 15: From the game A Pokemon reacts to an assist when one of these effects reaches it, so where you draw decides who gets hit. Source 7: From the game, the hit path Source 8: Read in code, the test on the Pokemon

AssistWhat appears, and when
Flyinga gust leaves the stylus every 4th frame the line grows, along your last stroke; older gusts get pushed on; up to 6 at once
Bug, Rocknothing while you draw; lift the stylus after a quick stroke and one shot flies off along it, up to 6 at once
Ghosteach loop you close lets out a wisp that drifts around the screen for 10 seconds, even after the assist ends; up to 4 at once
Watertouching down blows a bubble at the stylus that grows as you draw; lifting lets it go along your last stroke
Fire, Poison, Ground, Grass, Icemarks left along the line every 16 pixels as you draw
Fire, Ice (and Electric, if it ever runs as a timed assist)closing a loop also sets off an effect in its middle; Ice sends crystals from the middle out to the loop

Source 15: From the game, the effects unconfirmedSource 16: Best reading (unconfirmed), 600 frames as 10 seconds unconfirmedSource 17: Best reading (unconfirmed), whether Electric runs as a timed assist

The quick stroke. For Bug and Rock, every pixel you draw builds a charge, and each frame the stylus is held still drains 8 pixels of it; a lift with 32 pixels or more of charge fires the shot. Source 14: From the game So draw fast and lift at once: a slow line or a pause fires nothing. unconfirmedSource 18: Best reading (unconfirmed)

How long the effects last. A gust lasts 320 frames and a Bug or Rock shot 120, unless something ends it first. Source 7: From the game, the rule Source 8: Read in code, the counts

They never break your line. The game makes every assist effect with targets that leave the line out, so your own gusts, shots, wisps and bubbles can cross it freely. Source 7: From the game

Clock two: the matchup

When an assist hits a Pokemon, the game works out how long it reacts:

reaction (frames) = matchup x susceptibility / 100, rounded down, then x 10

Fire against four targets, from the data:

Target (group)MatchupSpecies percentReaction
Bulbasaur (Grass)20100200 frames, about 3.3 seconds
Charmander (Fire)710070 frames, about 1.2 seconds
Squirtle (Water)110010 frames, a sixth of a second
Steelix (Steel)20255510 frames, 8.5 seconds

Source 4: From the game, the rule Source 20: From the game, the numbers unconfirmedSource 21: Best reading (unconfirmed), frames as seconds

For Fire, that stored time only decides whether the Pokemon reacts at all: every Fire hit gives the same short hop (see Measured on every species). Source 22: From the game, the stored time Source 23: Read in code, the hop

Some bosses shrug assists off. Kyogre takes a quarter of the normal effect from almost every type, so Fire holds it 1 frame. Source 24: From the game Shedinja ignores every assist except Flying, Fire and Rock, which hit it two and a half times as hard, much like its ability in the main games. Source 11: From the game, the data unconfirmedSource 25: Best reading (unconfirmed), the comparison

Every reaction is proven frame by frame. Source 26: From the game

The capture field on every Pokemon page plays all of these.

A second hit of the same type does not extend a running reaction, except Psychic, Electric and the partner assists, which start again. Source 5: From the game While Ice has a Pokemon frozen, Water, Flying, Psychic and Fire hits do nothing to it, and after the thaw Ice cannot freeze it again for a second. Source 30: From the game unconfirmedSource 27: Best reading (unconfirmed), frames as seconds Grass, Ground and Ice only work on a Pokemon on the ground, so they do nothing to fliers. Source 5: From the game unconfirmedSource 31: Best reading (unconfirmed), that the flag means flying

Measured on every species

The game's own reaction code was run under emulation for all 213 capture-field species, with every assist type's hit at 5 moments of each Pokemon's own behaviour. Source 22: From the game Each Pokemon page has its own table of what each assist does to it and for how long.

Up and down arrows

A friend's assist counts as good against a target when the table entry is above that assist's usual value (its baseline column). Source 4: From the game Above the baseline, an up arrow shows over the Pokemon; below it, a down arrow; exactly at it, nothing. Source 4: From the game, the percent Source 36: Read in code, the arrows Every 5 seconds the game moves on to the next friend whose assist is good against something on the field. Source 36: Read in code unconfirmedSource 21: Best reading (unconfirmed), frames as seconds

The arrows read only the table, never the species' own percentage, so a boss that resists a type can still show an up arrow for it. Source 4: From the game

Fighting counts loops more than once

With Fighting active, each loop you draw counts again a quarter of a second later, as many extra times as the Fighting row gives the target's group. Source 4: From the game unconfirmedSource 37: Best reading (unconfirmed), 15 frames as a quarter second

Target groupOne loop counts as
Normal, Rock, Steel, Ice, Dark3 loops
Ghost1 loop (no extras)
every other group2 loops

Source 4: From the game, the rule Source 19: From the game, the table

A Pokemon whose own Fighting percentage is below 100 gets no extra loops. Nine Browser Pokemon are like that: Kyogre, Groudon, Rayquaza, Mew, Shedinja, Dusclops and the Gastly line. Source 4: From the game, the rule Source 11: From the game, the list Bulbapedia says Fighting counts each loop as two, the most common case. Source 1: Published source unconfirmedSource 38: Best reading (unconfirmed), the comparison

Psychic

At the lift, the first Pokemon on the line that is short of its loops is not let go: it goes into a state of its own, which ends by resetting its loops. Source 39: From the game, the lift Source 40: Read in code, the state

Every Psychic Pokemon stores an assist time (10 to 90), but the capture field never passes it to the timer. Source 9: Read in code Source 11: From the game, the stored times The Cutting Room Floor reports that a Psychic assist always lasts 5 seconds and the stored times are never loaded. Source 41: Published source Where the 5 seconds come from is not traced in the code yet. unconfirmedSource 42: Best reading (unconfirmed)

The Psychic friend walks onto the field at twice its run speed, lifts every capture target after its own animation, and lets them all go the frame after it has flown off the screen; each then falls after its own reaction time. Abra appears and vanishes on the spot. Source 28: From the game, the state unconfirmedSource 43: Best reading (unconfirmed), that it is the Psychic assist's friend

Dark

Dark doubles the line length limit while it is active. Source 44: From the game Every Dark Pokemon stores a power of 2, and Dark's timer counts frames, so started directly it would last two frames. Source 2: From the game Source 11: From the game, the data Bulbapedia says Dark uses a quarter of your energy to double the line for 6 seconds. Source 1: Published source

One proven state in the code fits: a friend walks onto the field and, when its power is 2, takes a quarter of your energy (at least one point, one point every 10 frames), then starts its own assist for 6 seconds (360 frames) per point taken. Source 28: From the game The best reading is that this is the Dark assist's friend: a long line, paid for in energy. unconfirmedSource 45: Best reading (unconfirmed)

Electric

The Electric friend walks onto the field at twice its run speed and gives back one Styler energy every 10 frames, as many points as its power (5, 15 or 99), never past the gauge's maximum (a full gauge drops the rest). Then it runs off and flies away. Source 28: From the game, the state unconfirmedSource 46: Best reading (unconfirmed), that it is the Electric assist's friend

Assists you can never use

Some Pokemon carry an assist in the data but never become friends, so you can never use it. Bulbapedia's Poke Assist page and The Cutting Room Floor each list them, mostly in agreement; Poke Assists marks every one and notes where the lists differ. Source 47: Published source

Try it

Try an assist against a target

Not known yet

How this is known

The two clocks, the formula, the Fighting rule, the hit handler, every reaction and every effect an assist puts on the line are proven functions of the game; the arrows and the test that tells a Pokemon an effect has reached it are read in the code. The tables come from the game's data at build time, and every example above is recomputed from them. Where Bulbapedia or The Cutting Room Floor describe an assist, the sentence names them. What each assist does to each species was also measured by running the game's own code under emulation. Source 22: From the game

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 Cross-checked Best reading (unconfirmed) Published source. How this wiki is made

  1. Published source. Bulbapedia, Poke Assist (the Pokemon Ranger section and table). Bulbapedia, read from a web.archive.org copy of 2026-08-02. archived copy Back to text: a b c
  2. From the game. The assist timer, its warnings, the queue, what each type does to the line. The decompilation's findings: assist-timer.md (Assist_Start, Assist_TickTimer, Assist_PlayTimerSounds, Assist_TickType01 to 16; MapSnatch__v02 and func_02033ff8 read only). Back to text: a b c d e f
  3. Best reading (unconfirmed) (frames as seconds). Same as source 2. Back to text
  4. From the game. The matchup formula, the 18 susceptibility bytes, Fighting's extra loops, the "good against" rule, the Bug reaction, the hit handler. The decompilation's findings: assist-matchup.md (Pokemon_GetAssistMatchupValue, Pokemon_GetAssistSusceptibility, Capture_QueueFightingExtraLoops, Pokemon_GetAssistMatchupPercent, Pokemon_IsAssistGoodOnField, Pokemon_HandleState3f; func_0203ea1c, func_020429b8, func_0204d3f4 read only). Back to text: a b c d e f g h i j k
  5. From the game. The hit handler that starts each reaction, row by row. The decompilation's findings: attacks.md (Pokemon_ReactToAssistHit). Back to text: a b c
  6. Best reading (unconfirmed) (that the queue is used in play). Same as source 2. Back to text
  7. From the game. How an assist effect reaches a Pokemon (its hit word), that no assist effect touches the line, how long each lasts. The decompilation's findings: effects.md (func_0206a390, EffectControl_Setup, EffectControl_SpawnFieldObject, EffectControl_IsEnded; func_0202dfa0 read only). Back to text: a b c d
  8. Read in code (the test on the Pokemon; the counts). Same as source 7. Back to text: a b c
  9. Read in code. Same as source 2. Back to text: a b c d
  10. Cross-checked. Assist type and power (kind 2 sub-record bytes 0x0c, 0x0d), group (record +0x02), the 18 susceptibility percentages (record +0x38). The game's own data, read at build time from a US copy of the game. Bulbapedia, Poke Assist (the Pokemon Ranger section and table). Bulbapedia, read from a web.archive.org copy of 2026-08-02. archived copy Back to text
  11. From the game (the data; the values; the list; the stored times). Assist type and power (kind 2 sub-record bytes 0x0c, 0x0d), group (record +0x02), the 18 susceptibility percentages (record +0x38). The game's own data, read at build time from a US copy of the game. Back to text: a b c d e f
  12. Best reading (unconfirmed) (what they look like). Same as source 2. Back to text
  13. From the game. The matchup formula, the 18 susceptibility bytes, Fighting's extra loops, the "good against" rule, the Bug reaction, the hit handler. The decompilation's findings: assist-matchup.md (Pokemon_GetAssistMatchupValue, Pokemon_GetAssistSusceptibility, Capture_QueueFightingExtraLoops, Pokemon_GetAssistMatchupPercent, Pokemon_IsAssistGoodOnField, Pokemon_HandleState3f; func_0203ea1c, func_020429b8, func_0204d3f4 read only). The Dark assist doubles the line length limit (Capture_GetLineLengthLimit). The decompilation's findings: styler-rank-stats.md. Back to text
  14. From the game. What the Flying, Bug, Rock, Ghost and Water assists do on the line, the loop effect of a closed loop, the assist Pokemon arriving. The decompilation's findings: assist-effects.md (Assist_TickType04, Assist_TickType05, Assist_TickType06, Assist_TickType07, Assist_TickType10, Assist_StartLoopEffect, Assist_TickArrivals). Back to text: a b
  15. From the game. What the Flying, Bug, Rock, Ghost and Water assists do on the line, the loop effect of a closed loop, the assist Pokemon arriving. The decompilation's findings: assist-effects.md (Assist_TickType04, Assist_TickType05, Assist_TickType06, Assist_TickType07, Assist_TickType10, Assist_StartLoopEffect, Assist_TickArrivals). The assist timer, its warnings, the queue, what each type does to the line. The decompilation's findings: assist-timer.md (Assist_Start, Assist_TickTimer, Assist_PlayTimerSounds, Assist_TickType01 to 16; MapSnatch__v02 and func_02033ff8 read only). Back to text: a b
  16. Best reading (unconfirmed) (600 frames as 10 seconds). Same as source 14. Back to text
  17. Best reading (unconfirmed) (whether Electric runs as a timed assist). Same as source 14. Back to text
  18. Best reading (unconfirmed). Same as source 14. Back to text
  19. From the game (the values; the row; the table). The matchup table, 19 assist rows by 20 group columns, column 18 the baseline. The game's own data, read at build time from a US copy of the game. Back to text: a b c
  20. From the game (the numbers). The matchup table, 19 assist rows by 20 group columns, column 18 the baseline. The game's own data, read at build time from a US copy of the game. Assist type and power (kind 2 sub-record bytes 0x0c, 0x0d), group (record +0x02), the 18 susceptibility percentages (record +0x38). The game's own data, read at build time from a US copy of the game. Back to text
  21. Best reading (unconfirmed) (frames as seconds). Same as source 4. Back to text: a b
  22. From the game. The game's own reaction code run under emulation for all 213 capture-field species, every assist type's hit at 5 moments of the Pokemon's own behaviour; two steps (an effect passing its hit on, and the released bubble's size reaching the Water hit) are read in code only. Code reading and emulator checks for this wiki. Back to text: a b c d e f g h i j k l m n o p q
  23. Read in code (the hop; that every Fire hit is this short; that the bubble's size reaches the hit). Same as source 22. Back to text: a b c
  24. From the game. Assist type and power (kind 2 sub-record bytes 0x0c, 0x0d), group (record +0x02), the 18 susceptibility percentages (record +0x38). The game's own data, read at build time from a US copy of the game. The matchup table, 19 assist rows by 20 group columns, column 18 the baseline. The game's own data, read at build time from a US copy of the game. Back to text: a b
  25. Best reading (unconfirmed) (the comparison). Same as source 11. Back to text
  26. From the game. What each assist hit does to a Pokemon, frame by frame, and how long it is out of action. The decompilation's findings: reactions.md (Pokemon_HandleState39 to Pokemon_HandleState4a, Pokemon_ClearReactionEffects). Back to text: a b c d e f g
  27. Best reading (unconfirmed) (frames as seconds). Same as source 26. Back to text: a b
  28. From the game. The friends a Poke Assist brings onto the field (states 0x6c to 0x72, answer 71) and the line test against a Pokemon. The decompilation's findings: hit-test.md (Pokemon_HandleState6f, Pokemon_HandleState70, Pokemon_GetDrainSteps, Pokemon_HandleState71, Capture_CheckPokemonHits). Back to text: a b c d e
  29. Best reading (unconfirmed) (the species). Same as source 26. Back to text
  30. From the game. The hit handler that starts each reaction, row by row. The decompilation's findings: attacks.md (Pokemon_ReactToAssistHit). What each assist hit does to a Pokemon, frame by frame, and how long it is out of action. The decompilation's findings: reactions.md (Pokemon_HandleState39 to Pokemon_HandleState4a, Pokemon_ClearReactionEffects). Back to text
  31. Best reading (unconfirmed) (that the flag means flying). Same as source 4. Back to text
  32. From the game. The game's own reaction code run under emulation for all 213 capture-field species, every assist type's hit at 5 moments of the Pokemon's own behaviour; two steps (an effect passing its hit on, and the released bubble's size reaching the Water hit) are read in code only. Code reading and emulator checks for this wiki. The matchup formula, the 18 susceptibility bytes, Fighting's extra loops, the "good against" rule, the Bug reaction, the hit handler. The decompilation's findings: assist-matchup.md (Pokemon_GetAssistMatchupValue, Pokemon_GetAssistSusceptibility, Capture_QueueFightingExtraLoops, Pokemon_GetAssistMatchupPercent, Pokemon_IsAssistGoodOnField, Pokemon_HandleState3f; func_0203ea1c, func_020429b8, func_0204d3f4 read only). Back to text
  33. Best reading (unconfirmed) (frames as seconds). Same as source 22. Back to text
  34. Best reading (unconfirmed). Same as source 22. Back to text
  35. Best reading (unconfirmed) (which partner type it is). Same as source 22. Back to text
  36. Read in code. Same as source 4. Back to text: a b
  37. Best reading (unconfirmed) (15 frames as a quarter second). Same as source 4. Back to text
  38. Best reading (unconfirmed) (the comparison). Same as source 19. Back to text
  39. From the game (the lift). The Psychic assist at the stylus lift. The decompilation's findings: capture-release.md (Capture_ResolveLine). Back to text
  40. Read in code (the state). Same as source 39. Back to text
  41. Published source. The Cutting Room Floor, Pokemon Ranger, Unused Pokemon Data ("Unused Psychic Times"; "Unused Assist and Field Moves"). The Cutting Room Floor, read from a web.archive.org copy of 2025-04-04. archived copy Back to text
  42. Best reading (unconfirmed). Same as source 2. Back to text
  43. Best reading (unconfirmed) (that it is the Psychic assist's friend). Same as source 28. Back to text
  44. From the game. The Dark assist doubles the line length limit (Capture_GetLineLengthLimit). The decompilation's findings: styler-rank-stats.md. Back to text
  45. Best reading (unconfirmed). The friends a Poke Assist brings onto the field (states 0x6c to 0x72, answer 71) and the line test against a Pokemon. The decompilation's findings: hit-test.md (Pokemon_HandleState6f, Pokemon_HandleState70, Pokemon_GetDrainSteps, Pokemon_HandleState71, Capture_CheckPokemonHits). Bulbapedia, Poke Assist (the Pokemon Ranger section and table). Bulbapedia, read from a web.archive.org copy of 2026-08-02. archived copy Back to text
  46. Best reading (unconfirmed) (that it is the Electric assist's friend). Same as source 28. Back to text
  47. Published source. Bulbapedia, Poke Assist (the Pokemon Ranger section and table). Bulbapedia, read from a web.archive.org copy of 2026-08-02. archived copy The Cutting Room Floor, Pokemon Ranger, Unused Pokemon Data ("Unused Psychic Times"; "Unused Assist and Field Moves"). The Cutting Room Floor, read from a web.archive.org copy of 2025-04-04. archived copy Back to text
  48. Best reading (unconfirmed). Same as source 28. Back to text
  49. Best reading (unconfirmed). Decomp findings, answers 8 to 13. The decompilation's findings: README.md. Back to text
  50. From the game (the store). Same as source 49. Back to text

What changed and why

  • The capture field now follows the decompiled game: Pokemon attack, every mover and every Poke Assist reaction runs as the game runs it, divers start under water, Steelix is built from its parts, and the line and the Styler disc are drawn exactly as the game draws them, 8 pixels thick. The pages that describe how Pokemon move and what each assist does were rewritten to match. Why: A review found the field not exact enough: no attacks, no real Styler sprite, the wrong line thickness, and water Pokemon showing their water layer all the time. The decompilation now covers all of it.

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