Ranger Wiki · Unofficial

About this wiki

From the Pokemon Ranger Wiki · Meta · Pokemon Ranger (DS, 2006)

The Pokemon Ranger Wiki is written and directed by GardenFlouer, and its numbers are read from the game's own data and from a decompilation of its code. Each fact carries a marker that says how certain it is, and mistakes are corrected in the open.

Who makes it

Written and directed by GardenFlouer. The numbers come from the game's own data and from a decompilation of its code that I direct; AI agents did much of the decompiling and drafted much of the text. Facts marked From the game are proven against the game's code by automated tests, and anything less certain says so.

I am GardenFlouer, the same GardenFlouer as the About page. The articles use a plain reference voice, so "I" appears only here and in the bylines.

Three kinds of source

The game's data. Every number (loops to capture, EXP, damage, speeds, Styler levels, where each Pokemon lives) is read from the game's own tables on a US copy, fresh on every build. If a sentence disagrees with the data, its page is not built. Raw game files are never published.

The game's code. The rules (how a loop counts, how EXP adds up, what breaks the line) come from the decompilation: each game function is rebuilt in C and tested against the original on thousands of generated inputs. It counts as proven only when every input gives the original's result and the inputs reached at least 90 percent of its instructions. Source 1: From the game The front page's count of proven functions comes from the decompilation's status file.

The game, running. Some rules are also checked by running the game's own code under emulation. The wiki's capture field on each Pokemon page is compared with the game frame by frame: all 213 species match exactly over 600 frames. The line test and each species' answer to a touch gave the game's results for every species. Source 2: From the game

Other people's work. When Bulbapedia, Serebii or The Cutting Room Floor say something, the sentence names them, citing dated web.archive.org copies so it stays checkable. Agreement with the data earns Cross-checked; a disagreement is shown side by side, never quietly "fixed".

The markers

Each fact carries a small numbered marker, like a footnote. Its shape says how certain the fact is; the Sources list at the foot says it in words, names what the fact rests on and links back.

MarkerWhat it means
From the game (a solid square)Read from the game's data, and the decompiled code proves the game uses it that way.
Read in code (a dashed square)Seen in a function that has been read but not yet rebuilt and proven. Likely right, still a reading.
Cross-checked (a double ring)Read from the data, with its meaning matched against Bulbapedia, Serebii or The Cutting Room Floor.
Best reading (unconfirmed) (a dotted line)The number is real, but its meaning in play, or its look, is a reading not confirmed yet. The text says "unconfirmed" beside it.

Source 3: From the game A sentence can carry two markers when its parts differ, for example a value From the game whose meaning is a best reading. The markers differ in shape, not only in colour.

What is quoted and what is not

  • Browser entries are quoted exactly as the US game shows them, labelled as the game's text. All 213 species have one, matched through the index the game uses for names and categories, and each entry names its own species. Source 4: From the game
  • Everything else the game says (dialogue, mission briefings, descriptions) is retold, never quoted: the build refuses any page that repeats eight words in a row from the game's text outside the labelled Browser entries.
  • Names of Pokemon, places, people and missions are used as names.

Known limits

  • The decompilation is not finished. Most of what a capture runs on is rebuilt and proven, from the loop and the lift to every mover, the line test and the end of a capture, but some special moves, the field's own modes and screens and a few Poke Assist paths are still read, not rebuilt, so their rules carry Read in code. Source 5: Read in code
  • Proven means proven within what the checker can test. Its review found cases it skips rather than compares, and cases where a time limit can end a check early; none hid a real difference in the rebuilt code, and the rules that depend on them are marked accordingly. Source 6: From the game
  • Some things only play can settle, such as what an effect looks like or how many frames an animation lasts. They stay a best reading, marked unconfirmed, until code or play confirms them.

Corrections so far

Four so far, all fixed on these pages:

  • A touch costs energy outside the charge. The first findings said a touch costs energy only during a Pokemon's charge attack. The review found a proven function that switches line damage on for some Pokemon at other times too. Source 6: From the game
  • Deoxys has seven data rows, not six. The capture check skips six of them; the seventh, read as the Normal Forme, is captured normally. Source 6: From the game
  • The Ranger Net needs no password. The early notes followed a source that said all four special missions need one. The code and an emulator run show only the Manaphy Egg mission does. Source 7: From the game
  • The line length limit counts steps of 11 pixels. Earlier drafts took one step to be 8 pixels, the size of a field unit, and showed the longest line about a quarter too short. The line's own set-up code gives 11. Source 8: Read in code

Field reports

If your cartridge does not match a page, send a field report from that page. I check each one against the game's data and code; when it holds, the page changes, says what changed and why, and thanks you by name if you like. There is no open editing, because this wiki's one promise is that every number traces back to the game.

Unofficial

The Pokemon Ranger Wiki is an unofficial fan wiki by GardenFlouer. It is not affiliated with Nintendo, The Pokemon Company, Creatures or HAL Laboratory. Pokemon and Pokemon Ranger are trademarks of their owners. Each page's foot says where its pictures come from.

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. How this wiki is made

  1. From the game. Decomp status (what counts as done, and the count of proven game functions). The decompilation's findings: ranger-decomp/docs/STATUS.md. Back to text
  2. From the game. The game's own capture field code run under emulation and compared with the wiki's capture fields frame by frame (round 8, 2026-10-30, all 213 species clean over 600 frames; the three vine users in the run that also runs the vine), the line test on 106,500 test lines, and the touch answers of all 213 species. Code reading and emulator checks for this wiki. Back to text
  3. From the game. Decomp findings, the confidence marks and the answers for the wiki. The decompilation's findings: README.md. Back to text
  4. From the game. The game's US Browser entries, joined to their species by name index (213 of 213). The game's own data, read at build time from a US copy of the game. Back to text
  5. Read in code. Same as source 3. Back to text
  6. From the game. The pre-release review of the decomp (corrections M4 and M8; the checker's limits M2, G1 to G3). The pre-release review of the decompilation. Back to text: a b c
  7. From the game. The emulator check of the Ranger Net unlock, which corrected the earlier notes. Code reading and emulator checks for this wiki. Back to text
  8. Read in code. The line length trim and its 11-pixel step. The decompilation's findings: line-bosses.md (CaptureLine_TrimToLimit; the constructor func_02027860 read only). 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