Ranger Wiki · Unofficial

Mantine

From the Pokemon Ranger Wiki · Browser No. 116 · Pokemon Ranger (DS, 2006)

Mantine takes 8 loops to capture in Pokemon Ranger. The game's maps never place it; it shows up in a Capture Challenge. Its Poke Assist, Water, is never usable in play, and it has no field move. It is also in Shadows of Almia and Guardian Signs.

In Pokemon Ranger, Mantine takes 8 loops at any Styler level, and 58 Pokemon in that game take more. Source 1: Cross-checked In Shadows of Almia, Mantine's capture gauge is 300; at Styler level 1 that is 30 loops, and at level 50, 2. Source 2: Read in code unconfirmedSource 3: Best reading (unconfirmed), fewest loops with no drain In Guardian Signs, Mantine's capture gauge is 2,070 and refills 60 a second once you stop looping; how many loops that takes is not decoded yet. Source 4: Read in code The hardest captures in all three games.

In the Ranger series

Mantine is in the Browser of all three Ranger games.

GameBrowser number
Pokemon Ranger (2006)No. 116 Source 7: From the game
Shadows of Almia (2008)R-091 Source 8: Cross-checked
Guardian Signs (2010)R-063 Source 9: Cross-checked

Pokemon Ranger (DS, 2006): the sections down to Shadows of Almia cover this game.

How Mantine moves

The capture field moves Mantine by these numbers, drawn with the game's own field sprite and animations. Source 10: From the game

WhatMantineSource
MovementStarts under water, where only its shadow ring shows, and may surface or dive again when it rests; it walks the usual way (movement type 27).Source 11: From the game
Turn speedUp to about 7.0 degrees a frame, always the short way round (game value 500).Source 12: From the game
Walk speedAbout 1.50 pixels a frame (game value 768).Source 11: From the game, value unconfirmedSource 13: Best reading (unconfirmed), pixels
Run speedGame value 1,920 a frame, for fast walks and some special actions.Source 11: From the game
Where it walks nextA random spot 48 to 256 pixels away, inside field area 1 (x 64 to 191, y 74 to 161); it tries up to 8 times, then takes the last.Source 11: From the game
RestsNever (its rest time is 0, with no random extra)Source 14: From the game
TurningTurns while it walks; stops to turn only near its stop, when 45 degrees or more off course.Source 11: From the game
Special actionDiving and surfacing, rolled at the start of a rest. An 80 percent chance at the start of each rest on the ground, once the wait since the last one is over.Source 15: From the game, chance and type Source 16: From the game, what the type does
At the startWalks at once.Source 15: From the game
Hit circleRadius 15 pixels: the line touches Mantine when it passes 15 pixels or less from the centre, in whole pixels. The centre moves with the animation and sits 11 pixels left and 13 up from the spot it stands on when facing left (5 pixels left and 13 up facing right). A centre more than 15 pixels off the screen never touches.Source 17: From the game
A touchBreaks the line, but costs energy only from a charging Pokemon or a line attacker like Steelix. Then it attacks back at once; if it is attacking already, it spins for about half a second instead. Only a frame's strongest hit counts; in the Fire, Rock and Flying reactions a touch leaves the line whole.Source 17: From the game, the rule Source 18: Read in code, which species attack by touch Source 19: From the game, what it does next
Leaves after70 seconds (a countdown of 60, which the code turns into 4,200 frames). Not simulated here.Source 15: From the game, value unconfirmedSource 20: Best reading (unconfirmed), seconds
Screen scaleOne game unit is 8 pixels (the field box is 32 by 24 units, the DS screen 256 by 192 pixels).unconfirmedSource 21: Best reading (unconfirmed)

How exact the field is

    Left out: the leaving countdown, herds, sounds and screen shake. Moves not decompiled yet are walked instead. Which background the game uses for each place is not decoded, so the field picks one.

    Browser entry

    Browser No. 116 · Mantine

    Mantine leaps out of the water, then

    charges with its massive body.

    The game's own words, quoted exactly as the Browser shows them (US version). Source 7: From the game

    Where to find Mantine

    1. Fall City
    2. East Road
    3. Lyra Forest
    4. Krokka Tunnel
    5. Waterworks
    6. Safra Sea
    7. Olive Jungle
    8. Jungle Relic
    9. Kisara Plain
    10. Dusk Factory
    11. Panula Cave
    12. Sekra Range
    13. Go-Rock Base
    14. Fiore Temple

    Fiore's areas in order, a sketch rather than a map. The numbers count its placements in the map data across the story.

    Capture Challenge

    Capture data

    How these rules work for every Pokemon: How capture works and Capture EXP.

    WhatMantineSource
    Loops to capture8 (the capture check uses exactly this number)Source 22: Cross-checked
    Base capture EXP3Source 23: From the game
    Bonus for extra loopsNone: its data holds no loop bonus, so extra loops add nothing.Source 23: From the game
    Group bonus+1 with 2 Pokemon in the loop, +2 with 3, +3 with 4 or more.Source 23: From the game
    Styler damage per hit4 energy points (game value divided by 10)Source 24: From the game, value Source 17: From the game, the divide
    Size classLarge (game value 18; small is under 12, large 18 and up)Source 12: From the game

    Poke Assist

    Mantine gives a Water assist that lasts 30 seconds. Source 5: Cross-checked Every Water assist, longest first

    Never usable in play. Mantine's assist is in the data but never helps you: Bulbapedia's Poke Assist list marks it unusable, and The Cutting Room Floor lists it with the unused assists and field moves of Pokemon met only in Capture Challenges or story fights. Source 5: Cross-checked

    How Mantine reacts to Poke Assists

    What each assist does when it hits Mantine, measured by running the game's own reaction code on its data (what was measured). Frames are the game's, 60 to a second. Source 25: From the game

    How Mantine reacts to each Poke Assist
    AssistWhat happensOut of action
    FireTurns away and hops 25 to 47 px up Source 26: Read in code, that every Fire hit gives this short reaction18 to 20 frames (0.3 s)
    WaterLifted in a bubble Source 26: Read in code, that the bubble's size reaches the hit68 to 93 frames (1.1 to 1.6 s)
    IceFrozen in place41 frames (0.7 s)
    FlyingBlown 47 px up147 frames (2.5 s)
    RockKnocked 2 to 53 px along168 to 179 frames (2.8 to 3 s)
    PsychicLifted 20 to 23 px and held until the Psychic friend has leftwhile held, then 214 to 215 frames (3.6 s)
    GhostSpins, circled by a ghostly shape181 frames (3 s)
    BugHeld in place, turning side to side161 frames (2.7 s)
    PoisonHeld in place, turning side to side151 frames (2.5 s)
    GroundHeld in place, turning side to side161 frames (2.7 s); the hit landed 4 of the 5 times it was tried
    GrassHeld in place, turning side to side261 frames (4.3 s); the hit landed 4 of the 5 times it was tried
    The two partner typesReacts to the partner's assist unconfirmedSource 27: Best reading (unconfirmed), which partner each type is301 frames (5 s) and 501 frames (8.3 s)

    Electric makes no Pokemon react, and Fighting counts loops instead. Source 25: From the game

    How assists react against each target, and why some show an arrow: How Poke Assists work.

    Field move

    Mantine has no field move, so it cannot clear obstacles.

    The Water group

    A Pokemon's group decides how Poke Assists affect it. All 39 Water-group Pokemon in the Browser:

    In Shadows of Almia

    Pokemon Ranger: Shadows of Almia (DS, 2008), from the game's own data (US copy). The Pokemon Ranger numbers above do not apply here.

    Mantine in Shadows of Almia: its stand animation at the game's own frame timing Source 28: From the game
    Browser numberR-091 Source 8: Cross-checked unconfirmedSource 29: Best reading (unconfirmed), three-digit R- form
    GroupWater Source 30: Read in code
    Poke AssistWater Source 8: Cross-checked
    Assist powerThree stored values: 5, 10, 20 at level 1, 103, 205, 410 at level 50 unconfirmedSource 31: Best reading (unconfirmed), what each of the three does
    Field moveSwim Source 8: Cross-checked
    A one-level move: the game stores no level for it.
    Capture gauge300 Source 2: Read in code
    Styler EXP for a capture18 unconfirmedSource 32: Best reading (unconfirmed)

    Browser entry

    Shadows of Almia · R-091 · Mantine

    It swims leisurely. It rams to attack.

    The game's own words, quoted exactly as its Browser shows them (US version). Source 33: From the game

    Loops at your Styler level

    The loops Mantine needs depend on your Styler level: each loop adds the Styler's capture power at its level Source 34: Read in code to Mantine's capture gauge of 300 Source 2: Read in code.

    Each loop adds 10: 30 loops fill the gauge of 300.

    The result uses the game's gain per loop Source 2: Read in code, formula; assist values by level unconfirmedSource 35: Best reading (unconfirmed), that the assist row is the Styler level; matchup factors Source 36: Read in code. It is a minimum, for uncharged loops with no drain and no other bonus: the gauge drains over time at a rate not found yet, and two bonuses of half the capture power depend on conditions not traced unconfirmedSource 3: Best reading (unconfirmed), fewest loops with no drain.

    Loops with no assist and no Power-up Data
    Styler levelCapture powerLoops
    11030
    102413
    20526
    301003
    401552
    502052

    Where it is found

    The game's maps place Mantine in these areas unconfirmedSource 37: Best reading (unconfirmed), area names. Some spots may depend on story progress, which the map data does not record.

    • Puel Sea: 4 placements on 3 maps
    • Sea of Wailord: 2 placements on 2 maps

    In Guardian Signs

    Pokemon Ranger: Guardian Signs (DS, 2010), from the game's own data (US copy). It has no groups: the Poke Assist type plays that part.

    Mantine, its field sprite from Guardian Signs
    Mantine in Guardian Signs: the first frame of its field movement set, a still Source 38: From the game
    Browser numberR-063 Source 9: Cross-checked unconfirmedSource 39: Best reading (unconfirmed), three-digit R- form
    Poke AssistWater, level 4 Source 9: Cross-checked, type Source 40: Read in code, level
    Field moveCut 4 Source 9: Cross-checked
    Capture gauge2,070 Source 4: Read in code
    Gauge refill60 a second (+6 every 6 frames), after a 3 second wait (180 frames) Source 4: Read in code
    Styler EXP for a capture2,200 Source 41: Read in code

    Browser entry

    Guardian Signs · R-063 · Mantine

    It attacks by spitting bubbles

    that make Pokémon Slowed.

    The game's own words, quoted exactly as its Browser shows them (US version). Source 42: From the game

    Capture gauge

    No loop count yet: each loop carries the Styler's Power, 10 at level 1 and 327 at level 99, plus 5 for each Power Plus Source 43: Read in code, but how Power fills the gauge is not decoded.

    Where it is found

    The story maps place Mantine 3 times on 3 maps Source 44: Read in code, the count. Which area each map belongs to is not decoded yet, so places are not named.

    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). 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
    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. Best reading (unconfirmed) (fewest loops with no drain). Same as source 2. Back to text: a b
    4. 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
    5. Cross-checked. The game's own data tables, matched against Bulbapedia, Serebii and The Cutting Room Floor (checked 2026-10-16). Back to text: a b c d e
    6. 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
    7. From the game. The game's own data tables on a US copy of Pokemon Ranger (DS, 2006), decoded for this wiki: the species table, the Browser, the map layers and spawn lists. Back to text: a b
    8. Cross-checked. Serebii's Shadows of Almia Ranger Browser list, compared row by row with the US data on 2026-10-23: all 267 numbers, names and Poke Assists agree. Field move or level differs in 8 cells; there the wiki keeps the US value and says what Serebii lists. Back to text: a b c d
    9. Cross-checked. Serebii's Guardian Signs Ranger Browser list, compared row by row with the US data on 2026-10-23: all 307 numbers and names agree. Serebii names five field moves differently from the US game (Slash, Break, Slam, Flame and Water for Cut, Crush, Tackle, Burn and Soak); once mapped, every field move agrees. Six Poke Assists and one field move level differ; there the wiki keeps the US value and says what Serebii lists. Back to text: a b c d
    10. From the game. The capture field draws the game's own field sprites, animations and capture backgrounds, decoded from the game, played frame by frame with the game's own timing. Which background each place uses is the wiki's choice. Back to text
    11. From the game. movement-profile.md, move-geometry.md, locomotion-types.md, wander-target.md, fliers-effects.md, water.md: units, the two speeds, turning, where a Pokemon walks next, the field box and every mover; Pokemon_GetWalkSpeed, Angle_StepToward, Pokemon_ChooseWanderTarget, Pokemon_MoveDefault, Pokemon_MoveHover, Pokemon_MoveShootFlyer. Proven. Back to text: a b c d e
    12. From the game. Same as source 1. Back to text: a b
    13. Best reading (unconfirmed) (pixels). A value from the game's own data tables; what it means here is a reading, not yet confirmed. Back to text
    14. From the game. idle-turn-airborne.md: rest times, hovering, hops and gravity; Pokemon_RollRestTime, Pokemon_HandleRestGround, Pokemon_MoveHop. Proven. Back to text
    15. From the game. decide-and-timing.md, behaviour-subrecord.md: the action chance and type, the cooldown, the first decision; Pokemon_HandleState2, Pokemon_RollSpecialAction. Proven. How it starts (walk, rest or decide at once) is the first state, Pokemon_HandleState0, proven too. Back to text: a b c
    16. From the game (what the type does). attacks.md, water.md: the capture target's action table, its main attack and projectile, the charge, the field-wide attack, diving and surfacing; Pokemon_PickKind2Action, Pokemon_HandleState8, Pokemon_FireProjectile, Pokemon_HandleDive. Proven. Back to text
    17. From the game. hit-test.md and the findings' answers 68 and 69: the line against the Pokemon, a circle per species from record +0x04 to +0x07, the whole-pixel distance test, what a touch does; Pokemon_SetHitCircle, Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_MarkLineTouched, Pokemon_HandleState5a. Proven; whether the touch reaction starts on the touch's own frame or the next is read in code. Back to text: a b c
    18. Read in code (which species attack by touch). line-break-damage.md: Styler damage per hit, line breaks, the energy gauge; Capture_BreakLine, StylerGauge_DecrementEnergy, proven. The pre-release review corrected when a touch costs energy: also for line attackers, not only during the charge; which species are line attackers is read in code. Back to text
    19. From the game (what it does next). touch.md and holdouts.md and the findings' answers 81, 82 and 90 to 97: what a touch sets off and the species that answer it with a move of their own, the first state, the timed row switch, the vine, Entei, Raikou, Suicune, Deoxys and Charizard; Pokemon_StartTouchReaction, Pokemon_TakeSpeciesState, Pokemon_HandleState0, Pokemon_TickSpeciesTimerRow, Pokemon_HandleVine. Proven, and the game's own code run under emulation answers a touch the same way for all 213 species. Charizard's landing, the move 14 species answer a touch with, and what starts Suicune's copies are not decompiled yet. Back to text
    20. Best reading (unconfirmed) (seconds). Same as source 13. Back to text
    21. Best reading (unconfirmed). Same as source 11. Back to text
    22. Cross-checked. 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
    23. From the game. exp-bonus.md: capture EXP, the group bonus and the loop bonus, Entei's row change; Pokemon_SetLoopCountAndExpBonus, Pokemon_GetCaptureExp. Proven. Back to text: a b c
    24. From the game (value). Same as source 18. Back to text
    25. From the game. content/ranger/assist-reactions.json: the game's own reaction code run under emulation for each of the 213 capture-field species (2026-10-29), every Poke Assist type's hit at 5 moments of the Pokemon's own behaviour. Each stored time matches the matchup formula on the species' own data, and the build checks that. Two steps rest on functions read in the code but not yet run: the one that passes a touching effect to the reaction (behind the Fire result) and the one that hands a released bubble's size to the Water hit. Back to text: a b
    26. Read in code (that every Fire hit gives this short reaction; that the bubble's size reaches the hit). Same as source 25. Back to text: a b
    27. Best reading (unconfirmed) (which partner each type is). Same as source 25. Back to text
    28. From the game. The field sprite, decoded from the game's graphics: the first sequence of its stand set, at the game's own frame timing when that sequence is plain frames, a still when it carries motion commands not decoded yet. Which way it faces is not confirmed. Back to text
    29. Best reading (unconfirmed) (three-digit R- form). Stored as a plain number; the US menu text has only an R- prefix for it. The three-digit form follows Serebii's list; how the game pads it on screen is not confirmed in its code yet. Dialga, Palkia and Shaymin are stored after the list as 1001 to 1003, for the special missions; how the game numbers them on screen is not found yet. Back to text
    30. Read in code. The Browser of a US copy of Pokemon Ranger: Shadows of Almia (DS, 2008): the number from the table the Browser reads by species (sub_0201DF54, read in code); group, Poke Assist, field move and level from the species-table columns it copies. A species with several data rows shows its lowest; which row the Browser picks is not traced. Back to text
    31. Best reading (unconfirmed) (what each of the three does). The assist power table (one row per level, one value or three per assist type), read through its accessor in code. That its row is the Styler level is a reading, not confirmed, and what the three values of Water, Ice, Bug, Dragon and Steel do is not decoded. Back to text
    32. Best reading (unconfirmed). The capture EXP column of the battle species table. Its values only make sense as Styler EXP (10 for early Pokemon, thousands for legendaries, on the same scale as the Styler's EXP table), but the code that pays it out is not traced. Back to text
    33. From the game. The Browser description of a US copy of Pokemon Ranger: Shadows of Almia, quoted word for word. Back to text
    34. 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
    35. Best reading (unconfirmed) (that the assist row is the Styler level). Same as source 31. Back to text
    36. 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
    37. Best reading (unconfirmed) (area names). Each map's Pokemon layer (1,139 placements on 271 maps in 35 areas). Area names come from the game's place-name list by area number, checked against each area's own text for about 15 areas and against the habitats. The layers store no story phase, and Pokemon brought in by story or mission scripts are not in them. Back to text
    38. From the game. The field sprite, decoded from the game's own graphics: the first frame of its field movement set, a still. The game's animation files are not decoded yet, and which way that frame faces is not confirmed. Back to text
    39. Best reading (unconfirmed) (three-digit R- form). Serebii numbers the last six entries S-001 to S-006, and the US menu text holds both an R- and an S- prefix. The three-digit form follows Serebii's list; how the game pads the number on screen is not confirmed in its code yet. Back to text
    40. Read in code (level). The Browser list of a US copy of Pokemon Ranger: Guardian Signs (DS, 2010): the number and its species row (func_02060AA8), and from that row the field move and level and the Poke Assist type and level (read by the target panel, the release scene and func_02041F84), all read in code. Back to text
    41. Read in code. The capture table's EXP field, which CCapturePlayer__v14 adds to the capture's running total (read in code). That this total is what the result screen shows is not traced. Back to text
    42. From the game. The Browser description of a US copy of Pokemon Ranger: Guardian Signs, quoted word for word. Back to text
    43. 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
    44. Read in code (the count). Every map's Pokemon placement layer (2,549 placements), its fields named by a schema table the game's code reads. Story maps and the second set are told apart by where they load from; that the second set is the multiplayer missions is a reading. Which area each map belongs to is not decoded yet. 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 Mantine joins your Loopbook, the list of what you have read on this device.

    Mantine, Browser No. 116, is in your Loopbook.

    Open your Loopbook