GitHub Search

See also GitHub's official help

The FAQ should suffice for most of the data, but you might as well want to look something up in the source code by yourself, e.g. item locations, trainers, flags, and procedures such as ifs and thens. (Particularly, there aren't exhaustive item location lists yet; each map file defines items available there, and each Pokémon Base Stats file the ones it may hold.) Use GitHub's search functions on your browser, namely the file finder and the search box.

Command line users can of course do grep, awk, etc.

File Finder

Press the Go to file button and input a file name you know or guess, and the finder performs a real-time forward search.

Examples:

• baseglac ➡️ data/pokemon/base_stats/glaceon.asm;
• evosatt ➡️ data/pokemon/evos_attacks.asm and some more;
• mapvictory ➡️ maps/VictoryRoad1F.asm, 2F, and 3F;
• wildjohto ➡️ data/wild/johto_grass.asm and data/wild/johto_water.asm; but…
• johtowild ➡️ audio/music/johtowildbattle.asm and audio/music/johtowildbattlenight.asm.

Search Box

Find the search box in the top bar or the hamburger menu and input a code string to look up. The extension:asm qualifier is useful for narrowing the results. It's a case-insensitive search and only shows result snippets; open one of the results to read through the code on the browser.

Polished follows pokecrystal's style guide for coding, e.g. constants in SCREAMING_SNAKE_CASE and labels in PascalCase.

Examples:

• ice_stone ➡️ map(s), shop(s), evolution conditions, definitions and descriptions, etc.;
• ice stone ➡️ not only the files above but also the others with ice and stone;
• itemfinder delivers some results, but item finder or item_finder don't.