Ranger Wiki · Unofficial

Shadows of Almia

From the Pokemon Ranger Wiki · DS, 2008

Pokemon Ranger: Shadows of Almia (DS, 2008) is the second Ranger game. Its 270 Browser entries, places, missions, quests, Styler and Poke Assists are all here, read from a US copy of the game. Each Pokemon's page covers the whole series, with an Almia section.

270Browser entries
31places with Pokemon
1,139Pokemon placements
17missions
6special missions
61quests

Counted from the game's data Source 1: Read in code unconfirmedSource 2: Best reading (unconfirmed), places by name Source 3: From the game Source 4: From the game. 267 Browser entries are numbered R-001 to R-267; the other three are the special-mission legendaries Source 5: Cross-checked.

The Browser opens with these 12 entries Source 5: Cross-checked:

In this section

Shadows of Almia Browser

All 270 entries with group, Poke Assist, field move and capture gauge. Sort and filter.

Places and their Pokemon

31 places and which Pokemon their maps hold.

Missions and quests

17 missions, 6 special missions and 61 quests, with ids.

Styler and Poke Assists

Styler levels 1 to 50, Power-up Data, assist power and the matchup chart.

How capturing changed

Loop counts in Ranger, capture gauges in Almia and Guardian Signs.

Browser numbers compared

Every Pokemon of the series and its number in each game.

What is different from Pokemon Ranger

Groups and Poke Assists in the Browser

How many of the 269 entries the wiki covers have each group Source 10: Read in code and each Poke Assist Source 5: Cross-checked. Recharge is only ever an assist, never a group. 20 entries have an assist that differs from their group.

TypeGroupPoke Assist
Normal2424
Fire2322
Water3229
Electric2114
Grass2121
Ice1113
Fighting1111
Poison1010
Ground1410
Flying1217
Psychic1516
Bug1412
Rock1211
Ghost1313
Dragon1213
Dark1214
Steel1212
Recharge07

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. 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: a b
  2. Best reading (unconfirmed) (places by name). 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
  3. From the game. The mission text of a US copy of Shadows of Almia, one bank per mission id: title, place, client and description. Ids 0 to 20 (15, 17, 18 and 19 are empty; 20 is a second Get the Blue Gem!) and the six special missions, each stored twice (69 to 74 and 80 to 85, with different descriptions). The goals are the wiki's own summaries. Whether the ids are the mission numbers shown on screen is not traced. Back to text
  4. From the game. The quest text of a US copy of Shadows of Almia, one bank per quest id: title, place and client, ids 1 to 61 (id 0 repeats quest 1). The quest scripts are not decoded, so steps and rewards are not shown. Back to text
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. Read in code. The group column of the species table, which the capture code passes to the matchup chart as the target's group (read in code); the in-game glossary calls it the group. 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