Ranger Wiki · Unofficial

Line breaks and damage

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

Anything that touches your Capture Line breaks it, and every loop on every Pokemon is lost at once. A plain touch costs no Styler Energy; only a charging Pokemon or a line attacker drains 0 to 8 energy a hit, set by its species.

The short version

What breaks the line

Every frame the game checks the Pokemon, then the other objects on the field; any touch breaks the line. Source 1: From the game, the order Source 2: From the game, the objects

The effects of your own Poke Assists are made so they can never touch the line, only Pokemon. Source 6: From the game

Does it cost energy?

Each Pokemon has a damage switch: a touch costs energy only while it is on, otherwise the break does no damage. Source 3: From the game

Two things turn the switch on:

  1. The charge. During a Pokemon's charge attack, its touch does damage. When the animation ends, the switch goes off and the Pokemon waits at least 4 seconds before acting again. Source 2: From the game unconfirmedSource 10: Best reading (unconfirmed), frames as seconds
  2. Line attackers. Some capture targets are marked as line attackers. Each time their behaviour resets (after a release or some reactions), the switch goes on, outside any charge, until a state or an assist hit turns it off. Source 11: From the game, the reset unconfirmedSource 12: Best reading (unconfirmed), who is marked

An assist that hits a Pokemon turns the switch off. Source 13: Read in code

The first draft of the findings missed the second path; the decomp review found it in a proven function. Source 14: From the game

No species row has the action number that starts the charge through the usual roll, so other code, not traced yet, must start it. Source 7: From the game, the roll unconfirmedSource 15: Best reading (unconfirmed), the data

How much a hit costs

A hit costs the species' stored damage (0 to 80, always a multiple of 10) divided by 10: 0 to 8 energy. Source 2: From the game, the copy Source 1: From the game, the divide Source 5: From the game, the values Objects work the same way with their own values. Source 2: From the game

Energy per hitBrowser Pokemon
01 (Magikarp)
153
247
354
438
59
65
72
84 (Raikou, Suicune, Groudon, Rayquaza)

Source 5: From the game

Each point costs one energy, energy never goes below 0, a break with no damage costs nothing, and of several hits in one frame only the strongest counts, not the sum. Source 2: From the game These are the capture targets' values. Source 2: From the game A Pokemon's overworld version stores a fixed push value instead when it charges, which most likely never meets your line. Source 14: From the game, the value unconfirmedSource 16: Best reading (unconfirmed), what it means

With no energy left, the Styler draws nothing: every touch of the screen is ignored. Source 17: From the game Each Pokemon page shows its own damage, and the Styler page how much energy each level gives.

What a break does

  1. With damage, an effect appears at the hit point and the cost is paid one point at a time; with none, the no-damage break is paid instead. Source 2: From the game
  2. Each tracked Pokemon gets its break reaction (below), then loses its loop count, its loops this run and both EXP bonuses. Source 2: From the game
  3. The tracking slots are emptied and the line is erased. Source 2: From the game

A Pokemon already taken by an earlier lift is not reset. Source 2: From the game The break plays one sound for 1 to 6 damage and another for 7 or more. Source 18: Read in code

You can read the damage off the break itself: 32 sparks burst from the hit point, white for no damage, yellow for 1 to 4 and red for 5 or more, and a trail of the same colour runs out along the line from the hit, 8 pixels a frame. Source 19: From the game, the rule unconfirmedSource 20: Best reading (unconfirmed), the colours as you see them

What a touched Pokemon does

On its next frame, a Pokemon that touched your line reacts in a way set by its species. Source 21: From the game, the rule Source 5: From the game, the species The game's own code, run for every species under emulation, did exactly this, and the capture field on each Pokemon page gives the same answer. Source 22: From the game

What it doesBrowser Pokemon
Spins two whole turns in about half a second (31 frames), then decides again108, the usual answer
Attacks back at once, unless it is already attacking or cannot right now62, such as Venusaur, Blastoise, Arcanine, Snorlax, Metagross and Entei
Runs for the edge of the screen13: Mudkip, Swellow, Dragonite, Gengar, Gyarados, Gloom, Ariados, Flygon, Umbreon, Beldum, Swablu, Kyogre and Deoxys
Answers with its field-wide attackTyranitar and Groudon
A move of its own during which the line cannot touch itShedinja, Gastly and Haunter
Stops to restBeedrill, Scizor, Linoone and Aerodactyl
Teleports to a new spotRalts and Gardevoir
A move of its own that is not decompiled yet: in the game's own run it paused about a third of a second, then walked off14, such as Bulbasaur, Rattata and Zubat
Another move of its ownthe few left: Ivysaur whips out its vine, Silcoon blocks, Lapras, Murkrow and Octillery attack back with their other attack

Source 21: From the game, the answers Source 5: From the game, the species Source 23: From the game, that the line cannot touch the three Source 24: Read in code, the pause and walk unconfirmedSource 25: Best reading (unconfirmed), what the other moves look like

A Pokemon that spins can be marked again only after its spin ends. Source 21: From the game One that would attack back but is already attacking, or a diver under water, spins instead. Source 21: From the game

A few bosses answer by their own data row first:

Pokemon that react to a break

Only two species rows react to a break, and only if they had a loop on them:

Every other row has no reaction. Source 2: From the game

Timed modes

On a clock, each damage point costs 10 seconds instead of a point of energy, a break with no damage still costs 10 seconds, and the clock stops at 0. Source 2: From the game Which modes are timed is not traced; likely the Capture Arena and the Capture Challenges. unconfirmedSource 9: Best reading (unconfirmed)

Try it

How many hits can your Styler take?

Not known yet

How this is known

The touch test, the break, the energy cost, the reactions and each species' answer to a touch are proven functions of the game, and the touch answers were also run as the game's own code under emulation for every species. Damage values and each species' answer come from the species table at each build.

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 line against the Pokemon (a circle per species, the whole-pixel test, who is tested, what a touch does, the damage divide); answers 68 and 69. The decompilation's findings: hit-test.md (Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_SetHitCircle, Pokemon_MarkLineTouched). Back to text: a b c d e
  2. From the game. What breaks the line, damage per hit, what a break does, break reactions, timed modes. The decompilation's findings: line-break-damage.md (Capture_BreakLine, Capture_CheckFieldObjectHits, MapSnatch__v60, MapSnatch__v61, Pokemon_ReactToLineBreak, Pokemon_HandleState22, Pokemon_HandleState57; func_020209b0 read only). Back to text: a b c d e f g h i j k l m n o p q r
  3. From the game. The line against the Pokemon (a circle per species, the whole-pixel test, who is tested, what a touch does, the damage divide); answers 68 and 69. The decompilation's findings: hit-test.md (Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_SetHitCircle, Pokemon_MarkLineTouched). Pre-release review M4 (answer 5 was wrong; a touch also costs energy outside the charge) and F1 (the kind 0 charge). The pre-release review of the decompilation. Back to text: a b
  4. From the game (the flag setters). The behaviour reset that reloads line damage (Pokemon_ResetBehaviourState). The decompilation's findings: capture-release.md. Back to text
  5. From the game. Styler damage (species sub-record +0x28 byte 7), action types (kind 2 sub-record +0x04), the touch answer (kind 2 sub-record +0x08). 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
  6. From the game. Which effects can hurt the line (the field object's targets), a Pokemon's projectiles and their damage, the assist effects. The decompilation's findings: effects.md (func_0206a390, EffectControl_Setup, EffectControl_SpawnFieldObject, Pokemon_SpawnEffectFlagged). Back to text: a b c
  7. From the game (the attack; the roll). The attacks and their cooldowns, which action types lead to them. The decompilation's findings: movement-profile.md (section 8; the kind 2 action table func_0203bb90 read only). Back to text: a b
  8. Read in code (the action table). Same as source 7. Back to text
  9. Best reading (unconfirmed). Same as source 2. Back to text: a b c
  10. Best reading (unconfirmed) (frames as seconds). Same as source 7. Back to text
  11. From the game (the reset). The behaviour reset that reloads line damage (Pokemon_ResetBehaviourState). The decompilation's findings: capture-release.md. Pre-release review M4 (answer 5 was wrong; a touch also costs energy outside the charge) and F1 (the kind 0 charge). The pre-release review of the decompilation. Back to text
  12. Best reading (unconfirmed) (who is marked). Same as source 4. Back to text
  13. Read in code. An assist hit ends a charge's line damage (func_0203ea1c read only). The decompilation's findings: assist-matchup.md. Back to text
  14. From the game. Pre-release review M4 (answer 5 was wrong; a touch also costs energy outside the charge) and F1 (the kind 0 charge). The pre-release review of the decompilation. Back to text: a b
  15. Best reading (unconfirmed) (the data). Same as source 7. Back to text
  16. Best reading (unconfirmed) (what it means). Same as source 14. Back to text
  17. From the game. The stylus and the Styler with no energy left. The decompilation's findings: line-bosses.md (Capture_ReadStylus). Back to text
  18. Read in code. Same as source 2. Back to text
  19. From the game (the rule). The break's burst and trail of particles, their colours by damage. The decompilation's findings: assist-effects.md section 7 (CaptureLine_SpawnBreakBurst, CaptureLine_SpawnBreakTrail). Back to text
  20. Best reading (unconfirmed) (the colours as you see them). Same as source 19. Back to text
  21. From the game. What a line touch sets off, frame by frame, and the species that answer it with a state of their own. The decompilation's findings: touch.md (Pokemon_StartTouchReaction, Pokemon_TakeSpeciesState, Pokemon_GetTouchActionState). Back to text: a b c d e f g
  22. From the game. The game's own code run under emulation for all 213 field species, a touch set exactly as the line test sets it, 90 frames recorded per species. Code reading and emulator checks for this wiki. Back to text
  23. From the game (that the line cannot touch the three). The game's own code run under emulation for all 213 field species, a touch set exactly as the line test sets it, 90 frames recorded per species. Code reading and emulator checks for this wiki. The line against the Pokemon (a circle per species, the whole-pixel test, who is tested, what a touch does, the damage divide); answers 68 and 69. The decompilation's findings: hit-test.md (Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_SetHitCircle, Pokemon_MarkLineTouched). Back to text
  24. Read in code (the pause and walk; the move). Same as source 22. Back to text: a b
  25. Best reading (unconfirmed) (what the other moves look like). Same as source 21. Back to text
  26. Best reading (unconfirmed) (the species). Same as source 21. Back to text: a b c d e
  27. From the game (the rule). What a line touch sets off, frame by frame, and the species that answer it with a state of their own. The decompilation's findings: touch.md (Pokemon_StartTouchReaction, Pokemon_TakeSpeciesState, Pokemon_GetTouchActionState). The line against the Pokemon (a circle per species, the whole-pixel test, who is tested, what a touch does, the damage divide); answers 68 and 69. The decompilation's findings: hit-test.md (Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_SetHitCircle, Pokemon_MarkLineTouched). Back to text
  28. From the game (the rule). What a line touch sets off, frame by frame, and the species that answer it with a state of their own. The decompilation's findings: touch.md (Pokemon_StartTouchReaction, Pokemon_TakeSpeciesState, Pokemon_GetTouchActionState). The timed row switch, which turns Altaria's other row back at its next decision. The decompilation's findings: holdouts.md (Pokemon_TickSpeciesTimerRow). Back to text
  29. Best reading (unconfirmed) (that both are Charizard). Same as source 2. Back to text
  30. Best reading (unconfirmed) (the species and what it looks like). Same as source 2. Back to text
  31. Best reading (unconfirmed). Same as source 4. Back to text
  32. Best reading (unconfirmed). Same as source 21. Back to text

Also consulted

  • Decomp findings, answers 4, 5, 14 and 67, the line hits table. The decompilation's findings: README.md.

What changed and why

  • A touch can cost energy outside the charge attack too: a line attacker such as Steelix drains energy with a plain touch. Why: The pre-release review found a second place in the code that switches the touch damage on.
  • The capture field now answers a touch of the line as the game does: most Pokemon spin for about half a second, others attack back, run for the edge, rest or do a move of their own. Entei calls two Magmar, Raikou roars and switches rows, Suicune leaves two copies, Deoxys changes form, Charizard takes to the air, and Bulbasaur, Ivysaur and Tangela whip out their vine. Why: The decompilation proved the touch reaction and these moves, and the game's own code, run under emulation, does the same for every species.

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