Expanding the Pokédex into Emerald

Xencleamas · Apr 27, 2014

For those who want a better expansion without any bugs, see this post and use this instead. All of what's left here will be a heap of information on how expansion works and is done.
This post though gave me cancer.

I would like to share a little bit wisdom to all:

"PLEASE CREDIT SBIRD. DO NOT CREDIT ME ALONE, YOU MUST CREDIT SBIRD AS WELL. I have noticed numerous hacks that only credit me for the expansion and that's very unfair to SBird, as he was the one who did it first. YOU MUST CREDIT SBIRD." -Chaos Rush

It is because SBird is the real mastermind and first person who achieved the expansion on Emerald however, thus on a German ROM. SBird was so kind to post his notes for documentation and guiding everyone, making it possible on any language Emerald ROM. Then, Chaos Rush is the guy who made it working into an English Emerald ROM. Chaos Rush formely handled this thread. I took over for the continuity and adding some improvements while he's away. To be fair on crediting, include SBird as well. Alright! Let's make the expansion into Emerald. This tutorial was formerly copied word-by-word from DoesntKnowHowToPlay's FireRed Pokédex expansion tutorial. Now, I've cleared and cleaned some. If not, feel to judge. Alright, let's begin:

Prerequisites
List of tools needed:

An Emerald ROM (preferably the English/US one)
Any GameBoy Advance emulator (I'm using VBA-M)
Any Hex Editor (I'm using HxD)
Any calculator that can use hexadecimal (Calculator for Windows users and you should be in programmer mode)
Free Space Finder (optional, just for looking free spaces)
Advanced knowledge on Hex Editing (I won't be teaching you how to use a hex editor, or how to repoint things. If you're qualified to do this, odds are all you really need is the offsets, which is pretty much all this post is.)

Decide the number of new Pokemon
Before to get started, you need to think and decide of the new total number of Pokemon with the new ones which you will add later. The current number of slots are 440 (this includes the index 0 at the very beginning). So, you will have to pick a number which is more than 440. The answer can be really higher than 440. Here's a quick help for you to decide which new total number of Pokemon you want to use:

Spoiler:

Keep in mind that in the rest of tutorial will be Hex numbers. Advice on typing hex numbers on filters, do not type the "0x08". So, let's move on! Before to go any further, USE AT YOUR OWN RISK!!!

The Expansion
Step 1: Installing the Save Block Hack

Spoiler:

The first obstacle to expanding the Pokedex is the need for flags to store what new Pokemon the player has seen/caught. To do this, we need free memory.

First things first. Put this routine into free space. It is JPAN's Save Block Hack, albeit modified so that it works on hardware:

Code:

21 68 FF 23 1B 01 5B 18 98 88 00 28 09 D0 04 28
0A D0 0D 28 0C D0 0D 2D 1C DD 01 20 08 BC 98 46
F0 BD C4 21 08 4A 06 E0 8E 21 89 00 07 4A 02 E0
BA 21 09 01 06 4A 04 3B 18 68 10 60 04 3A 04 39
00 29 F8 D1 E7 E7 C0 46 C0 D8 03 02 F8 DA 03 02
98 E6 03 02 00 48 00 47 2D 2E 15 08 FF FF FF FF
FF 27 3F 01 CF 19 F8 80 BE 88 00 2E 08 D0 04 2E
09 D0 0D 2E 0B D0 00 00 00 48 00 47 53 28 15 08
C4 23 08 4A 06 E0 8E 23 9B 00 07 4A 02 E0 BA 23
1B 01 06 4A 04 3F 10 68 38 60 04 3A 04 3B 00 2B
F8 D1 E9 E7 C0 D8 03 02 F8 DA 03 02 98 E6 03 02

Make sure you insert it at a 4-byte aligned offset (ending with 0, 4, 8, or C). As some of you know, JPAN never released a hardware-compatible save fix for Emerald, but diegoisawesome fixed it up for his Emerald hack, CrystalDust. Because I had trouble doing it on my own, I will be completely honest: I ripped this routine straight from CrystalDust as it was the only way I got things working properly. I hope you don't mind me doing this, diegoisawesome.

Next we need to make some byte changes to get the routine working.

At 0x152E98,put 00 48 00 47 XX XX XX 08. For XX XX XX 08, it's the offset you put the save block routine +0x1.
At 0x15284E, put 38 47.
At 0x15288C, put YY YY YY 08. For YY YY YY 08, it's the offset you put the save block routine +0x61.
At 0x0D9CC6, put 38 47.
At 0x0D9D04, put YY YY YY 08.
At 0x0DA284, put 00 48 00 47 XX XX XX 08.

At 0x5CDC00 is the offset of the save size table. Paste this over the bytes there:

Code:

00 00 2C 0F 00 00 F0 0F F0 0F F0 0F E0 1F F0 0F
D0 2F B8 0D 00 00 F0 0F F0 0F F0 0F E0 1F F0 0F
D0 2F F0 0F C0 3F F0 0F B0 4F F0 0F A0 5F F0 0F
90 6F F0 0F 80 7F 50 04

Again, this was taken from CrystalDust, as it was the only way I could get everything working. So credit to diegoisawesome for this as well.

Step 2: Get free RAM for the dex flags

Spoiler:

Step 3: Repoint Everything

Spoiler:

Part 1: Pokemon Names

The current Pokemon Names table is at 0x083185C8.
The Pokemon Names table has 11 bytes (0xB bytes) each Pokemon (if changing the limit is possible, just change the multiplier).
Go to a free space to create a new Pokemon Names table.
Create a new Pokemon Names table there. Multiply your desired new slots of Pokémon by 11 (0xB).
Select blocks and the type the length with the number of the result. Then fill the selection with "AC AC AC AC AC AC AC AC AC AC FF". There you go! You got your new table.
Navigate to 0x083185C8 to the Pokemon Names table.
Select and copy 4532 bytes (0x11B4 bytes) of data.
Paste it to where your new Pokemon Names table starts.
Repoint all references of the Pokemon Names table to the new table. Replace all C8 85 31 08 to the pointer of your new table. Also check if it have done 132 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x083185C8 to the Pokemon Names table. Select 4532 bytes (0x11B4 bytes) of data. Then, fill it with "FF".
At 0x0806B944, place 00 00 00 00 00 00 (that's six 00s). This will cause the repointed name table to actually get used.

Part 2: Pokemon Base Stats

The current Pokemon Base Stats table is at 0x083203CC.
The Pokemon Base Stats table has 28 bytes (0x1C bytes) each Pokemon.
Go to a free space to create a new Pokemon Base Stats table.
Create a new Pokemon Base Stats table there. Multiply your desired new slots of Pokémon by 28 (0x1C).
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x083203CC to the Pokemon Base Stats table.
Select and copy 11536 bytes (0x2D10 bytes) of data.
Paste it to where your new Pokemon Base Stats table starts.
Repoint all references of the Pokemon Base Stats table to the new table. Replace all CC 03 32 08 to the pointer of your new table. Also check if it have done 74 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x083203CC to the Pokemon Base Stats table. Select 11536 bytes (0x2D10 bytes) of data. Then, fill it with "FF".
To read the Egg Hatching Time data, it is the Base Stats table plus 17 (0x11) bytes. So, that is 0x083203DD. Replace all DD 03 32 08 to the pointer of your new table for making the Egg Hatching Time read the new table. Also check if it have done 2 occurences.
To read the Held Item data, it is the Base Stats table plus 12 (0xC) bytes. So, that is 0x083203D8. Replace all D8 03 32 08 to the pointer of your new table for making the Held Item read the new table. Also check if it have done 1 occurence (pointer is at 0x0806EB7C)
Another one to read the Held Item data, it is the Base Stats table plus 14 (0xE) bytes. So, that is 0x083203DA. Replace all DA 03 32 08 to the pointer of your new table for making the Held Item read the new table. Also check if it have done 2 occurences (pointers are at 0x0806EB28 and 0x0806EBA0).

Part 3: Pokemon Moveset

The current Pokemon Moveset table is at 0x0832937C.
The Pokemon Moveset table has 4 bytes each Pokemon (a table of pointers).
Go to a free space to create a new Pokemon Moveset table.
Create a new Pokemon Moveset table there. Multiply your desired new slots of Pokémon by 4.
Select blocks and the type the length with the number of the result. Then fill the selection with "DC 30 32 08". There you go! You got your new table.
Navigate to 0x0832937C to the Pokemon Moveset table.
Select and copy 1648 bytes (0x670 bytes) of data.
Paste it to where your new Pokemon Moveset table starts.
Repoint all references of the Pokemon Moveset table to the new table. Replace all 7C 93 32 08 to the pointer of your new table. Also check if it have done 8 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0832937C to the Pokemon Moveset table. Select 1648 bytes (0x670 bytes) of data. Then, fill it with "FF".

Part 4: Front Sprites

The current Front Sprites table is at 0x0830A18C.
The Front Sprites table has 8 bytes each Pokemon (a table of pointers with filler bytes). Noted that PGE lists this offset as "PokemonAnimations", and lists the unused single-frame R/S front sprite table as "PokemonFrontSprites". Don't get these mixed up, as the single-frame R/S front sprite table is never used in-game.
Go to a free space to create a new Front Sprites table.
Create a new Front Sprites table there. Multiply your desired new slots of Pokémon by 8.
Select blocks and the type the length with the number of the result (mine is 8640 in decimal or 0x21C0 hexadecimal). Then fill the selection with "00 00 B0 08 00 08 00 00". There you go! You got your new table.
Navigate to 0x0830A18C to the Front Sprites table.
Select and copy 3520 bytes (0xDC0 bytes) of data.
Paste it to where your new Front Sprites table starts.
Repoint all references of the Front Sprites table to the new table. Replace all 8C A1 30 08 to the pointer of your new table. Also check if it have done 42 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0830A18C to the Front Sprites table. Select 3520 bytes (0xDC0 bytes) of data. Then, fill it with "FF".

Part 5: Back Sprites

The current Back Sprites table is at 0x083028B8.
The Back Sprites table has 8 bytes each Pokemon (a table of pointers with filler bytes).
Go to a free space to create a new Back Sprites table.
Create a new Back Sprites table there. Multiply your desired new slots of Pokémon by 8.
Select blocks and the type the length with the number of the result (mine is 8640 in decimal or 0x21C0 hexadecimal). Then fill the selection with "98 09 C0 08 00 08 00 00". There you go! You got your new table.
Navigate to 0x083028B8 to the Back Sprites table.
Select and copy 3520 bytes (0xDC0 bytes) of data.
Paste it to where your new Back Sprites table starts.
Repoint all references of the Back Sprites table to the new table. Replace all B8 28 30 08 to the pointer of your new table. Also check if it have done 15 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x083028B8 to the Back Sprites table. Select 3520 bytes (0xDC0 bytes) of data. Then, fill it with "FF".
At 0x080346D6, put 07 E0.
At 0x08034AC2, put 07 E0. These will break the limiters from preventing sprites for showing up,

Part 6: Normal Palette

The current Normal Palette table is at 0x08303678.
The Normal Palette table has 8 bytes each Pokemon (a table of pointers with filler bytes). Noted that the filler bytes are important in this, see the animation explanation on step .
Go to a free space to create a new Normal Palette table.
Create a new Normal Palette table there. Multiply your desired new slots of Pokémon by 8.
Select blocks and the type the length with the number of the result (mine is 8640 in decimal or 0x21C0 hexadecimal). Then fill the selection with "E0 0B C0 08 00 00 00 00". There you go! You got your new table.
Navigate to 0x08303678 to the Normal Palette table.
Select and copy 3520 bytes (0xDC0 bytes) of data.
Paste it to where your new Normal Palette table starts.
Repoint all references of the Normal Palette table to the new table. Replace all 78 36 30 08 to the pointer of your new table. Also check if it have done 5 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x08303678 to the Normal Palette table. Select 3520 bytes (0xDC0 bytes) of data. Then, fill it with "FF".

Part 7: Shiny Palette

The current Shiny Palette table is at 0x08304438.
The Shiny Palette table has 8 bytes each Pokemon (a table of pointers with filler bytes). Noted that the filler bytes are important in this, see the animation explanation on step .
Go to a free space to create a new Shiny Palette table.
Create a new Shiny Palette table there. Multiply your desired new slots of Pokémon by 8.
Select blocks and the type the length with the number of the result. Then fill the selection with "F8 0B C0 08 F4 01 00 00". There you go! You got your new table.
Navigate to 0x08304438 to the Shiny Palette table.
Select and copy 3520 bytes (0xDC0 bytes) of data.
Paste it to where your new Shiny Palette table starts.
Repoint all references of the Shiny Palette table to the new table. Replace all 38 44 30 08 to the pointer of your new table. Also check if it have done 3 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x08304438 to the Shiny Palette table. Select 3520 bytes (0xDC0 bytes) of data. Then, fill it with "FF".
At 0x0806E750, put 04 E0. This break the limiter on the palette table.

Part 8: Player Y

The current Player Y table is at 0x083021D8.
The Player Y table has 4 bytes each Pokemon.
Go to a free space to create a new Player Y table.
Create a new Player Y table there. Multiply your desired new slots of Pokémon by 8.
Select blocks and the type the length with the number of the result. Then fill the selection with "88 00 00 00". There you go! You got your new table.
Navigate to 0x083021D8 to the Player Y table.
Select and copy 1760 bytes (0x6E0 bytes) of data.
Paste it to where your new Player Y table starts.
Repoint all references of the Player Y table to the new table. Replace all D8 21 30 08 to the pointer of your new table. Also check if it have done 11 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x083021D8 to the Player Y table. Select 1760 bytes (0x6E0 bytes) of data. Then, fill it with "FF".

Part 9: Enemy Y

The current Enemy Y table is at 0x08300D38.
The Enemy Y table has 4 bytes each Pokemon.
Go to a free space to create a new Enemy Y table.
Create a new Enemy Y table there. Multiply your desired new slots of Pokémon by 8.
Select blocks and the type the length with the number of the result. Then fill the selection with "88 00 00 00". There you go! You got your new table.
Navigate to 0x08300D38 to the Enemy Y table.
Select and copy 1760 bytes (0x6E0 bytes) of data.
Paste it to where your new Enemy Y table starts.
Repoint all references of the Enemy Y table to the new table. Replace all 38 0D 30 08 to the pointer of your new table. Also check if it have done 15 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x08300D38 to the Enemy Y table. Select 1760 bytes (0x6E0 bytes) of data. Then, fill it with "FF".

Part 10: Altitude

The current Altitude table is at 0x08305DCC.
The Altitude table has 1 byte each Pokemon.
Go to a free space to create a new Altitude table.
Create a new Altitude table there. Multiply your desired new slots of Pokémon by 1.
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x08305DCC to the Altitude table.
Select and copy 440 bytes (0x1B8 bytes) of data.
Paste it to where your new Altitude table starts.
Repoint all references of the Altitude table to the new table. Replace all CC 5D 30 08 to the pointer of your new table. Also check if it have done 4 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x08305DCC to the Altitude table. Select 440 bytes (0x1B8 bytes) of data. Then, fill it with "FF".
At 0x080A5F82, put 03 E0.
At 0x080A5EB6, put 03 E0. These break limiters, allowing these tables to be read.

Part 11: Icons

The current Icons table is at 0x0857BCA8.
The Icons table has 4 bytes each Pokemon.
Go to a free space to create a new Icons table.
Create a new Icons table there. Multiply your desired new slots of Pokémon by 4.
Select blocks and the type the length with the number of the result. Then fill the selection with "A0 FF C2 08". There you go! You got your new table.
Navigate to 0x0857BCA8 to the Icons table.
Select and copy 1760 bytes (0x6E0 bytes) of data.
Paste it to where your new Icons table starts.
Repoint all references of the Icons table to the new table. Replace all A8 BC 57 08 to the pointer of your new table. Also check if it have done 2 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0857BCA8 to the Icons table. Select 1760 bytes (0x6E0 bytes) of data. Then, fill it with "FF".

Part 12: Icon Palette Control

The current Icon Palette Control table is at 0x0857C388.
The Icon Palette Control table has 1 byte each Pokemon. This one controls on which one of the three sets of palette that the icon sprite should use.
Go to a free space to create a new Icon Palette Control table.
Create a new Icon Palette Control table there. Multiply your desired new slots of Pokémon by 1.
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x0857C388 to the Icon Palette Control table.
Select and copy 440 bytes (0x1B8 bytes) of data.
Paste it to where your new Icon Palette Control table starts.
Repoint all references of the Icon Palette Control table to the new table. Replace all 88 C3 57 08 to the pointer of your new table. Also check if it have done 12 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0857C388 to the Icon Palette Control table. Select 440 bytes (0x1B8 bytes) of data. Then, fill it with "FF".
At 0x080D2E3A, put 01 E0.
At 0x080D2D20, put 00 00 00 00. This should fix the icon palettes.

Part 13: TM Compatibility

The current TM Compatibility table is at 0x0831E898.
The TM Compatibility table has 8 bytes each Pokemon.
Go to a free space to create a new TM Compatibility table.
Create a new TM Compatibility table there. Multiply your desired new slots of Pokémon by 8.
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x0831E898 to the TM Compatibility table.
Select and copy 3296 bytes (0xCE0 bytes) of data.
Paste it to where your new TM Compatibility table starts.
Repoint all references of the TM Compatibility table to the new table. Replace all 98 E8 31 08 to the pointer of your new table. Also check if it have done 4 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0831E898 to the TM Compatibility table. Select 3296 bytes (0xCE0 bytes) of data. Then, fill it with "FF".

Part 14: Tutor Compatibility

The current Tutor Compatibility table is at 0x08615048.
The Tutor Compatibility table has 4 bytes each Pokemon.
Go to a free space to create a new Tutor Compatibility table.
Create a new Tutor Compatibility table there. Multiply your desired new slots of Pokémon by 4.
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x08615048 to the Tutor Compatibility table.
Select and copy 1648 bytes (0x670 bytes) of data.
Paste it to where your new Tutor Compatibility table starts.
Repoint all references of the Tutor Compatibility table to the new table. Replace all 48 50 61 08 to the pointer of your new table. Also check if it have done 1 occurence. The only pointer is at 0x081B2390.
If you want to erase the old data to have new spaces, navigate back to 0x08615048 to the Tutor Compatibility table. Select 1648 bytes (0x670 bytes) of data. Then, fill it with "FF".

Part 15: Evolutions

The current Evolutions table is at 0x0832531C.
The Evolutions table has 40 bytes (0x28 bytes) each Pokemon if you are having 5 evolutions per Pokemon. If you have 8, that would be 64 bytes (0x40 bytes). Since the default is 5, let's use 5.
Go to a free space to create a new Evolutions table.
Create a new Evolutions table there. Multiply your desired new slots of Pokémon by 40 (0x28). If you already had the evolutions by 8, multiply instead to 64 (0x40).
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x0832531C to the Evolutions table.
Select and copy 16480 bytes (0x4060 bytes) of data.
Paste it to where your new Evolutions table starts.
Repoint all references of the Evolutions table to the new table. Replace all 1C 53 32 08 to the pointer of your new table. Also check if it have done 6 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0832531C to the Evolutions table. Select 16480 bytes (0x4060 bytes) of data. Then, fill it with "FF".

Part 16: Footprints

The current Footprints table is at 0x0856E694.
The Footprints table has 4 bytes each Pokemon. This is a table of pointers.
Go to a free space to create a new Footprints table.
Create a new Footprints table there. Multiply your desired new slots of Pokémon by 4.
Select blocks and the type the length with the number of the result. Then fill the selection with "A0 03 C3 08", or "F0 74 C3 08" if you want every footprint to be empty. There you go! You got your new table.
Navigate to 0x0856E694 to the Footprints table.
Select and copy 1652 bytes (0x674 bytes) of data.
Paste it to where your new Footprints table starts.
Repoint all references of the Footprints table to the new table. Replace all 94 E6 56 08 to the pointer of your new table. Also check if it have done 1 occurence.
If you want to erase the old data to have new spaces, navigate back to 0x0856E694 to the Footprints table. Select 1652 bytes (0x674 bytes) of data. Then, fill it with "FF".

Part 17: Cry Table

The first Cry Table is at 0x0869DCF4. This controls the normal cries like sent out in battle, summary, or the cry in Pokedex.
The first Cry Table has 12 bytes (0xC bytes) each Pokemon.
Go to a free space to create a new first Cry Table table.
Create a new first Cry Table there. Multiply your desired new slots of Pokémon by 12 (0xC).
Select blocks and the type the length with the number of the result. Then fill the selection with "20 3C 00 00 04 67 74 08 FF 00 FF 00". There you go! You got your new table.
Navigate to 0x0869DCF4 to the first Cry Table.
Select and copy 4656 bytes (0x1230 bytes) of data.
Paste it to where your new first Cry Table starts.
Repoint all references of the first Cry Table to the new table. Replace all F4 DC 69 08 to the pointer of your new table. Also check if it have done 1 occurrence (the only pointer is at 0x080A35EC)
If you want to erase the old data to have new spaces, navigate back to 0x0869DCF4 to the first Cry Table. Select 4656 bytes (0x1230 bytes) of data. Then, fill it with "FF".

Part 18: Cry Table 2 (used for moves like Growl/Roar)

The second Cry Table is at 0x0869EF24. This controls for moves like Growl and Roar.
The second Cry Table table has 12 bytes (0xC bytes) each Pokemon.
Go to a free space to create a new second Cry Table.
Create a new second Cry Table there. Multiply your desired new slots of Pokémon by 12 (0xC).
Select blocks and the type the length with the number of the result. Then fill the selection with "30 3C 00 00 04 67 74 08 FF 00 FF 00". There you go! You got your new table.
Navigate to 0x0869EF24 to the second Cry Table.
Select and copy 4656 bytes (0x1230 bytes) of data.
Paste it to where your new second Cry Table starts.
Repoint all references of the second Cry Table table to the new table. Replace all 24 EF 69 08 to the pointer of your new table. Also check if it have done 1 occurrence (the only pointer is at 0x080A35DC)
If you want to erase the old data to have new spaces, navigate back to 0x0869EF24 to the second Cry Table. Select 4656 bytes (0x1230 bytes) of data. Then, fill it with "FF".

Part 19: Auxillary Cry Table

The current Auxillary Cry table is at 0x0831F61C. This controls for moves like Growl and Roar.
The Auxillary Cry table has 2 bytes each Pokemon.
Go to a free space to create a new Auxillary Cry table.
Create a new Auxillary Cry table there. Multiply your desired new slots of Pokémon by 2.
Select blocks and the type the length with the number of the result. Then fill the selection with "00 00". There you go! You got your new table.
Navigate to 0x0831F61C to the Auxillary Cry table.
Select and copy 270 bytes (0x10E bytes) of data.
Paste it to where your new Auxillary Cry table starts.
Repoint all references of the Auxillary Cry table to the new table. Replace all 1C F6 31 08 to the pointer of your new table. Also check if it have done 1 occurrence (the only pointer is at 0x0806D534)
If you want to erase the old data to have new spaces, navigate back to 0x0831F61C to the Auxillary Cry table. Select 270 bytes (0x10E bytes) of data. Then, fill it with "FF".

An explanation on how the Cry tables work, especially the Auxillary Cry table:

Spoiler:

Step 4: Dealing with Dex Entries

Spoiler:

Part 1: National Dex

The current National Dex table is at 0x0831DC82.
The National Dex table has 2 bytes each Pokemon.
Go to a free space to create a new National Dex table.
Create a new National Dex table there. Multiply your desired new slots of Pokémon by 2.
Select blocks and the type the length with the number of the result. Then fill the selection with "E7 03" or "00". There you go! You got your new table.
Navigate to 0x0831DC82 to the National Dex table.
Select and copy 822 bytes (0x336 bytes) of data.
Paste it to where your new National Dex table starts.
Repoint all references of the National Dex table to the new table. Replace all 82 DC 31 08 to the pointer of your new table. Also check if it have done 2 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0831DC82 to the National Dex table. Select 822 bytes (0x336 bytes) of data. Then, fill it with "FF".

This is how the National Dex table works:

Spoiler:

Part 2: Hoenn Dex (Pokedex)

The current Hoenn Dex (Pokedex) table is at 0x0831DFB8.
The Hoenn Dex (Pokedex) table has 2 bytes each Pokemon.
Go to a free space to create a new Hoenn Dex (Pokedex) table.
Create a new Hoenn Dex (Pokedex) table there. Multiply your desired new slots of Pokémon by 2.
Select blocks and the type the length with the number of the result. Then fill the selection with "E7 03" or "00". There you go! You got your new table.
Navigate to 0x0831DFB8 to the Hoenn Dex (Pokedex) table.
Select and copy 822 bytes (0x336 bytes) of data.
Paste it to where your new Hoenn Dex (Pokedex) table starts.
Repoint all references of the Hoenn Dex (Pokedex) table to the new table. Replace all B8 DF 31 08 to the pointer of your new table. Also check if it have done 2 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0831DFB8 to the Hoenn Dex (Pokedex) table. Select 822 bytes (0x336 bytes) of data. Then, fill it with "FF".

This is how the Hoenn Dex (Pokedex) table works:

Spoiler:

Part 3: Hoenn Dex (Summary)

The current Hoenn Dex (Summary) table is at 0x0831D94C.
The Hoenn Dex (Summary) table has 2 bytes each Pokemon.
Go to a free space to create a new Hoenn Dex (Summary) table.
Create a new Hoenn Dex (Summary) table there. Multiply your desired new slots of Pokémon by 2.
Select blocks and the type the length with the number of the result. Then fill the selection with "E7 03" or "00". There you go! You got your new table.
Navigate to 0x0831D94C to the Hoenn Dex (Summary) table.
Select and copy 822 bytes (0x336 bytes) of data.
Paste it to where your new Hoenn Dex (Summary) table starts.
Repoint all references of the Hoenn Dex (Summary) table to the new table. Replace all 4C D9 31 08 to the pointer of your new table. Also check if it have done 2 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0831D94C to the Hoenn Dex (Summary) table. Select 822 bytes (0x336 bytes) of data. Then, fill it with "FF".

This is how the Hoenn Dex (Summary) table works:

Spoiler:

Part 4: Pokedex Entries

The current Pokedex Entries table is at 0x0856B5B0.
The Pokedex Entries table has 32 (0x20) bytes each Pokemon. The table is aligned in the actual Pokedex order.
Go to a free space to create a new Pokedex Entries table.
Create a new Pokedex Entries table there. Multiply your desired new slots of Pokémon by 32 (0x20).
Select blocks and the type the length with the number of the result. Then fill the selection with "CF E2 DF E2 E3 EB E2 FF 00 00 00 00 00 00 00 00 0D D3 55 08 00 00 00 01 00 00 00 01 00 00 00 00". There you go! You got your new table.
Navigate to 0x0856B5B0 to the Pokedex Entries table.
Select and copy 12384 bytes (0x3060 bytes) of data.
Paste it to where your new Pokedex Entries table starts.
Repoint all references of the Pokedex Entries table to the new table. Replace all B0 B5 56 08 to the pointer of your new table. Also check if it have done 8 occurences.
If you want to erase the old data to have new spaces, navigate back to 0x0856B5B0 to the Pokedex Entries table. Select 12384 bytes (0x3060 bytes) of data. Then, fill it with "FF".

Now there's a whole bunch of other things we need to do to get the dex working. We'll get to that later.

Step 5: Explanation of how Pokémon animations work in Emerald

Spoiler:

A Choice Point!
At the point, you have read on how the animations work, right? Now, decide: you will disable it or not? It is up to you. Continue at Step 6A if you want to maintain the animations. Or, continue at Step 6B if you want to disable the animations. Either way, after these, you will continue at Step 7.

Step 6A: Expanding Pokémon animations

Spoiler:

Part 1: Front Animations

The current Front Animations table is at 0x083299EC.
The Front Animations table has 1 byte each Pokemon
Go to a free space to create a new Front Animations table.
Create a new Front Animations table there. Multiply your desired new slots of Pokémon by 1.
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x083299EC to the Front Animations table.
Select and copy 440 bytes (0x1B8 bytes) of data.
Paste it to where your new Front Animations table starts.
Repoint all references of the Front Animations table to the new table. Replace all EC 99 32 08 to the pointer of your new table. Also check if it have done 4 occurences.
If you want to erase the old data to have new spaces, navigate Front to 0x083299EC to the Front Animations table. Select 440 bytes (0x1B8 bytes) of data. Then, fill it with "FF".

Part 2: Back Animations

The current Back Animations table is at 0x0860A8C8.
The Back Animations table has 1 byte each Pokemon
Go to a free space to create a new Back Animations table.
Create a new Back Animations table there. Multiply your desired new slots of Pokémon by 1.
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x0860A8C8 to the Back Animations table.
Select and copy 440 bytes (0x1B8 bytes) of data.
Paste it to where your new Back Animations table starts.
Repoint all references of the Back Animations table to the new table. Replace all C8 A8 60 08 to the pointer of your new table. Also check if it have done 1 occurence.
If you want to erase the old data to have new spaces, navigate back to 0x0860A8C8 to the Back Animations table. Select 440 bytes (0x1B8 bytes) of data. Then, fill it with "FF".

Part 3: Frame Switching

The current Frame Switching table is at 0x08309AAC.
The Frame Switching table has 4 byte each Pokemon. This is a table of pointers.
Go to a free space to create a new Frame Switching table.
Create a new Frame Switching table there. Multiply your desired new slots of Pokémon by 4.
Select blocks and the type the length with the number of the result. Then fill the selection with "BC 8C 30 08". There you go! You got your new table.
Navigate to 0x08309AAC to the Frame Switching table.
Select and copy 1760 bytes (0x6E0 bytes) of data.
Paste it to where your new Frame Switching table starts.
Repoint all references of the Frame Switching table to the new table. Replace all AC 9A 30 08 to the pointer of your new table. Also check if it have done 5 occurences.
If you want to erase the old data to have new spaces, navigate Front to 0x08309AAC to the Frame Switching table. Select 1760 bytes (0x6E0 bytes) of data. Then, fill it with "FF".
Back at Normal Palette table, after every pointer, place "XX XX". XX XX is a digit ranging 0x0000 until 0x01B7. This also depends on how the frames switch during animation. You may not need to do this now. You may do this later when you will set animation indexes to Pokemon.
Back at Shiny Palette table, after every pointer, place "XX XX". XX XX is a digit ranging 0x01F4 until 0x03AB. This also depends on how the frames switch during animation for Shiny Pokemon. You may do this later when you will set animation indexes to Pokemon.

Part 4: Animation Timing

The current Animation Timing table is at 0x08329B87.
The Animation Timing table has 1 byte each Pokemon.
Go to a free space to create a new Animation Timing table.
Create a new Animation Timing table there. Multiply your desired new slots of Pokémon by 1.
Select blocks and the type the length with the number of the result. Then fill the selection with "00". There you go! You got your new table.
Navigate to 0x08329B87 to the Animation Timing table.
Select and copy 412 bytes (0x1B8 bytes) of data.
Paste it to where your new Animation Timing table starts.
Repoint all references of the Animation Timing table to the new table. Replace all 87 9B 32 08 to the pointer of your new table. Also check if it have done 2 occurences.
If you want to erase the old data to have new spaces, navigate Front to 0x08329B87 to the Animation Timing table. Select 412 bytes (0x1B8 bytes) of data. Then, fill it with "FF".
At 0x08034BFE, put 07 E0. This breaks the limiter for animating sprites.
At 0x080A5FEE, put 03 E0. This breaks another limiter .

Step 6B: Disabling Pokémon animations

Spoiler:

Step 7: Dex-related byte changes

Spoiler:

Step 8: Changing lsl operations to make scrolling and other things work properly

Spoiler:

Back-up Point!
Also make sure you guys back up your ROM before doing the following steps. The very nature of how Step 9 is handled is almost sure to overwite a couple bytes or so that aren't actually constants. Eventually I plan on optimizing it so that we only overwrite bytes that are confirmed to be necessary. I mean, the current implementation of it works but the whole game hasn't been tested thoroughly, so we don't know for sure yet if this will overwrite something that's not actually related to the Pokédex routines. That is why I say use this at your own risk. The reason why I posted this tutorial at this stage is because the more people test this out, the faster we can find any problems that occur.

Step 9: Massive byte changes to make scrolling and other things work properly

Spoiler:

Step 10: Fix Castform, other glitches, and misc necessary byte changes

Spoiler:

Step 11: Fix this one glitch

Spoiler:

Now test. If you did everything correctly, you should have a fully working Pokédex expansion on your Emerald ROM.

[PokeCommunity.com] Expanding the Pokédex into Emerald

And, here a video tutorial made by LCCoolJ95 just in case you might want a visual aid on how anyone should be doing this:

This tutorial was just to get everything necessary for the Pokédex alone to work. The offsets for the tables that need to be expanded are listed here:

Spoiler:

Also one difference from FireRed is that there is no limiter to how high the Seen/Caught total is on the Save menu and on the Trainer Card.

Also some of my limiters for the altitude stuff may be wrong. If it is, and if there are any other problems, please report it. As I said earlier, use this at your own risk, as all this was discovered recently and there may be issues we don't know about yet.

I would like to give a huuuuuuuuge thanks to SBird, who did it on a German Emerald ROM first. Without him, none of this would be possible. What I did was find the corresponding English ROM offsets, but as expected that didn't work out perfectly, as there was a few operation codes I had to find on my own. Nonetheless, his advice helped a lot and pointed me in the right direction, so again, SBird deserves huuuuuuuuuuuge credit for this.

Also let me say this again, USE AT YOUR OWN RISK!!! I say this because during Step 8, there might be a few operation codes that I missed, and I alone can't test this out thoroughly. Karatekid552, if you're reading this, and if you're going to implement it into G3HS, I recommend you do it as a beta test type of thing. The main reason being, I only went up to 493 when I did this, so I don't know of any problems that may arise if one were to expand to 649 or 721.
(I believe 744 is the max that you can have in the Pokédex in Emerald, as it was the highest number that the Seen/Caught flags would register)

Credits:

SBird: for documenting it and just being awesome. For every credit you will make, you should add this guy on the credits. He is the real mastermind.
Chaos Rush: The former owner of this thread. He made almost everything to make the expansion working in an English Emerald ROM. I took over for the continuity and adding some improvements while he's away. The "fix this one glitch" ASM routine, and fixing Castform back.
diegoisawesome: I ripped the save block routine and the save table data from CrystalDust. Sorry :)
Doesn'tKnowHowToPlay: There was an inaccuracy in one of SBird's notes and so I applied byte changes similarly to his FireRed implementation of it and got everything working. That and parts of this tutorial are copied word for word from his for the sake of continuity.
shinyquagsire: for documenting how Emerald animations work.
karatekid552: for his awesome G3HS tool, as well as for his Python script and just being an awesome dude.
LCCoolJ95: Finding the limiter for sprites during evolution, and for his wonderful video tutorial.
Artemis64: For giving his guide on how to expand the animations rather than disabling it.
Purple Orange: The Held Items fix to make it read the new base stat table to avoid expanded Pokemon from keep holding "????????" item when caught or received.

EDIT (2016/01/07): I've updated the patch that will make steps 8, 9, and 10 to be done. And, also make sure you backed-up your ROM before patching for failing purposes. But, I more recommend to do this manually instead of patching.

And now, Generation VII (and including Magearna) is now around. It will be yet to be revealed on how much Pokemon will add on. However, the current expansion only supports in a maximum number of 744. I've read notes of SBird and one of his notes says that it can be expanded to more than 744. I'll try and do some testing soon to make sure if still can go further. The bad news right now is the availability of PC Boxes/Storage in Gen III games (no idea how to expand it more but it will cause troublesome).

OronDF343 · Apr 27, 2014

Great post! This is exactly what I needed, thanks!

Question:

Chaos Rush said:
Put YY 30 at x843A8, where YY is the number of bytes between the sets of flags. YY is probably the same as XX, but it doesn't have to be.

Do you mean the space between the sets of flags, in bytes? or the offset of the second set reative to the first?
I tried both, see no diff yet...

EDIT:
~~If you say there should be 40 pointers, and Search/Replace finds 132, is this ok? Am I doing it wrong?~~
I noticed you copied the numbers of pointers from the other guide.

EDIT2:
After preforming steps 1&2, I can't open the dex in game, and it displays the wrong number of either seen or caught.

HidoranBlaze · Apr 27, 2014

Nice work Chaos!
I'll try to beta test this with 649 Pokemon. (cuz screw Kalos, I'm not inserting that many sprites)

Chaos Rush · Apr 27, 2014

tURuI said:
EDIT2:
After preforming steps 1&2, I can't open the dex in game, and it displays the wrong number of either seen or caught.

That's exactly what's supposed to happen when you've only done those steps. That's why I removed some of Doesnt's text saying "Test and it should work" because it doesn't at that point on Emerald. You have to do the whole thing.

HidoranBlaze · Apr 27, 2014

Chaos Rush said:
Be aware that I did not cover these fundamental changes:
*TM compatibility
*Move Tutor compatibility
*Evolution table
*Cry table
*Footprint table
I'm not covering these simply because karatekid552 already has these offsets for his tool, and one o the main reasons why I'm documenting this is so that karatekid552 can add Emerald Pokédex expansion support.

The cry conversion table isn't actually listed in Karatekid's ini (thehoenncryauxtable section) for Emerald. But it wasn't that hard to find. It's at 0x31F61C for BPEE.

EDIT: Looks like Gamer2020 found it a long time ago. I guess I just wasted 2 minutes of my time then :p

Chaos Rush · Apr 27, 2014

Also make sure you guys back up your ROM before doing Step 9. The very nature of how Step 9 is handled is almost sure to overwite a couple bytes or so that aren't actually constants. Eventually I plan on optimizing it so that we only overwrite bytes that are confirmed to be necessary. I mean, the current implementation of it works but the whole game hasn't been tested thoroughly.

wael96 · Apr 27, 2014

Thanks you for the work, a feature like expansion of pokedex is vey cool! BTW, how to find the RAM for the dex flags?

Chaos Rush · Apr 27, 2014

wael96 said:
Thanks you for the work, a feature like expansion of pokedex is vey cool! BTW, how to find the RAM for the dex flags?

I used 0203D800 for the SEEN flags and 0203D860 for the CAUGHT flags.

I found a glitch: When viewing one of the search mode listings (A-Z, by type, smallest/largest, lightest/heaviest, color, etc.) and then going back to the main national listing, the list will appear blank. I'm 90% sure this can be fixed just by finding an lsl opcode that's related to it and adding +1 to it.
EDIT: To fix that, put 1B 01 at xBC42E. I have added it to the first post.

Chaos_Darkrai · Apr 27, 2014

WOW! Just wanted to say, INCREDIBLE job on this, Chaos Rush! One question I have, though... How will the battle frontier work with the extended pokemon? Just a question, that, honestly, I am quite curious about!

SBird · Apr 27, 2014

The reason why this only supports up to 744 Pokémon is actually this:

Search: 81 01 00 00
Replace: E7 02 00 00
Do this for the first 29 occurances in the ROM.

Now go back to offset x000000.
Search: 9B 01 00 00
Replace: 0D 03 00 00

I guess if you fiddle around with the numbers you should be able to add even more if you are crazy like that. The reason I chose 744 is because I ran into issues with higher numbers at first, but I guess those came from another set of global vars and would be easy to fix anyways. Keep in mind though if you really want to go further in terms of how many entries to place in the dex you also want to allocate more RAM via the malloc operation AND spare some space for the global variables, because neighter me nor chaos rush did calculate exactly how many places there are if you just add 0x700 or shift the bytes one more(which basically means a multiply of two so 0x600 becomes 0xC00)

So thats that, the first one controls how many entries are displayed by the way: 0x02E7 = 743(d), that makes 744 if you count entry zero.

~SBird

Chaos Rush · Apr 27, 2014

Here are some offsets that may or may not be necessary (this would be part of Step 8 should it be confirmed that it's necessary):
080BB3BA: 12 01
080BB5AE: 1B 01
080BC42E: 1B 01 <--- fixes Search-related stuff
080BC4CE: 1B 01
080BF3BE: 1B 01
080BF59E: 1B 01
080BFB80: 09 01
080C17C6: 12 01
080C23F2: 1B 01

Chaos Rush · Apr 27, 2014

I found and squashed another bug. The bug was that if you press START in the main Pokédex screen to make that small blue menu slide from the bottom (the one that says "BACK TO LIST/LIST TOP/LIST BOTTOM/CLOSE POKéDEX"), then Pokédex slot #405 (Luxray) would be overwritten with the last menu choice you had in that blue menu (basically it would show either Missingno, Bulbasaur, Ivysaur, or Venusaur where Luxray is supposed to be if you bring up the small blue menu by pressing START). This was because the RAM location of that menu variable conflicted with that of Luxray's slot on the Pokédex RAM. This is fixed by doing the following byte changes:
BB8CA: 09 01
BBABE: 12 01
BBBA8: 24 01
BBBD4: 12 01
BBF96: 09 01
BC140: 09 01
BC288: 1B 01
BC2B4: 12 01
BE892: 09 01
Again, added to the first post as well.

EDIT: Found and squashed yet ANOTHER bug. Make these byte changes in order to get the category listings to load correctly when highlighting "SHIFT" in the mode change menu:
BC4CE: 1B 01
C1808: 12 01
C23F2: 1B 01

EDIT: There is one last bug that I'm trying to squish. What happens is that the Pokédex doesn't remember the position you were at when you press SELECT to bring up the mode change menu, instead it will always bring you back to Bulbasaur (or Treecko if you're in Hoenn dex mode). The position you were at is held at 02000D1E (0200061E in a vanilla Emerald ROM). It should only be overwriting that offset with 0000 if you are switching between National and Hoenn, but for some reason it is always overwriting it with 0000 whether you switch or not. I don't know what's causing this, and I've tried looking into it but with little success. If someone can help me with this, I'd be very grateful, as this is the last final bug to squish before we have a seemingly perfect Pokédex expansion.

wael96 · Apr 28, 2014

I am now facing the question which showed as pink color text... may you help me?

Put a pointer to whichever set of flags comes first at x843BC.(Does this mean" if I use the 0x0203D800, then I should type 00D80302 at 0x843BC?)
Put 20 1C 00 00 at x8439A.
Put XX 22 at x843A0, where XX is the number of bytes taken by your dex flags.(sorry that I don't understand about the value "XX" Does this mean "number of dex entries- the answer is (number of dex entries)/8, rounded up." )
Put 20 1C at x843A6.
Put YY 30 at x843A8, where YY is the number of bytes between the sets of flags. YY is probably the same as XX, but it doesn't have to be.
Put XX 22 at x843AC, where XX is the number of bytes taken by your dex flags.

Alternatively, instead of these byte changes, you can instead make an OW script that clears the dex with writebytetooffset, and make sure it runs before the player gets the Pokédex. Your choice.

Sniper · Apr 28, 2014

Omg. This really awesome omg omg! :D I can finally put more x3

OronDF343 · Apr 28, 2014

Chaos Rush said:
Starting at x309AAC and ending at x30A11B is a table. This table is 4 bytes per mon.

Are you sure this table ends at x30A11B? I found exactly 28 more pointers right after it, which means that they could be for slots 412-439 which are the alternate formes. ~~The same could be true for the sprite animation tables.~~ (It's not the same for the animation tables most likely)

EDIT1+2: Found Hoenn Dex Order. It's at x31DFB8. There are 2 pointers to it. ~~It is 0x194 bytes long, just like the length of the Hoenn dex.~~
EDIT3: Heres what I found from analyzing the data: There are 411 entries in the Hoenn dex table, each one has the National dex ID of the pokemon that appears in that slot in the Hoenn Dex. My guess is that there is a limiter and/or a global variable somewhere. Another thing: I'm not sure if it has one more entry for Missingno or not (probably not)
tl;dr: The table is 0x336 bytes long, 2 bytes per entry, 411 entries total.

Dragonflye · Apr 28, 2014

Thanks for the deleting the 2nd Frame Tut. ;) It work, but tURuI has right, the end Offsets are not correkt.^^

Chaos Rush · Apr 28, 2014

tURuI said:
Are you sure this table ends at x30A11B? I found exactly 28 more pointers right after it, which means that they could be for slots 412-439 which are the alternate formes. ~~The same could be true for the sprite animation tables.~~ (It's not the same for the animation tables most likely)

EDIT1+2: Found Hoenn Dex Order. It's at x31DFB8. There are 2 pointers to it. ~~It is 0x194 bytes long, just like the length of the Hoenn dex.~~
EDIT3: Heres what I found from analyzing the data: There are 411 entries in the Hoenn dex table, each one has the National dex ID of the pokemon that appears in that slot in the Hoenn Dex. My guess is that there is a limiter and/or a global variable somewhere. Another thing: I'm not sure if it has one more entry for Missingno or not (probably not)
tl;dr: The table is 0x336 bytes long, 2 bytes per entry, 411 entries total.

There are actually two Hoenn Dex tables, one at 0x31DFB8 that controls how the order that they appear in the Pokédex, and then there's another table at 0x31D94C that controls the Pokédex number that appears in the Summary screen when you haven't yet obtained the National Dex. But yeah, the former is the "main" one.

And yes, I fixed the frame table ending offsets, thanks for pointing that out :)

I am working on fixing the bug where the dex doesn't remember what position you were at when you press SELECT to bring up the mode change menu. Once that's done, then I can say that the Pokédex alone is perfect and will post offsets for all the other easier stuff so that karatekid can add it to his tool :)

EDIT: I have literally spent hours trying to fix that one final glitch to no avail (the dex doesn't remember your position when changing modes by pressing SELECT, thus always resetting to Bulbasaur/Treecko). Here is what I've found on it so far:
Branch to routine below: 080BBD4E
Routine that handles this: 080BBD7C
RAM offset of dex slot in SBird's expansion method: 02000D1E
RAM offset of dex slot in vanilla Emerald: 0200061E

If anyone can help me look into this, it would be greatly appreciated, as I've already worked out all the other bugs earlier. This is really the only thing that needs to be solved until we can call it a perfect Pokédex expansion.

SBird · Apr 30, 2014

Something I figured out, I would apreciate confirmation of the english hackers, is: Castform(And its ability) seem to bug when using the expanded pokemon tables etc. I don't know if this is a general bug, which also exists if you do this for FR or if its emerald only. However the sprites, palettes etc. get messed up. Until now I only experienced this for castform(I thinks its the only pokémon of its kind, having a transformation ability)

~SBird

Deokishisu · May 1, 2014

SBird said:
Something I figured out, I would apreciate confirmation of the english hackers, is: Castform(And its ability) seem to bug when using the expanded pokemon tables etc. I don't know if this is a general bug, which also exists if you do this for FR or if its emerald only. However the sprites, palettes etc. get messed up. Until now I only experienced this for castform(I thinks its the only pokémon of its kind, having a transformation ability)

~SBird

Could it have something to do with disabling the animations? Castform's sprite has more than one frame. Perhaps locking out all the second frames is the issue? If so, then Deoxys would also not work correctly.

SBird · May 1, 2014

Deokishisu said:
Could it have something to do with disabling the animations? Castform's sprite has more than one frame. Perhaps locking out all the second frames is the issue? If so, then Deoxys would also not work correctly.

Hrn, that does not seem to be it. The animations are there but the ability does not work. It does not load the correct sprite / palette and it also does not change the type. I am almost certain it has something to do with the pokedex, but I can't figure out what the heck it is.

So a warning to everyone(unless something confirms that this is not an issue bound to the pokédex): Castform will be bugged due to the expansion.

~SBird

Edit: The bug exists due to the fact that castform(id 0x181) and the maximum amount of pokémon in the dex(0x181) interfer. To solve the issue you have to check in the search / replace process which 0x81010000 really refer to the pokédex. I'm sorry to have made that error in the first place, but that is also the reason castform does not work anymore ;)

Expanding the Pokédex into Emerald

More options

Xencleamas

Attachments

OronDF343

HidoranBlaze

Chaos Rush

HidoranBlaze

Chaos Rush

wael96

Chaos Rush

Chaos_Darkrai

SBird

Chaos Rush

Chaos Rush

wael96

Sniper

ふゆかい

OronDF343

Dragonflye

Author of Pokémon Sovereign of the Skies

Chaos Rush

SBird

Deokishisu

Mr. Magius

SBird