Pokémon Gaia evolutions: Gengar, Alakazam, Eevee and Regal Stone

Start with the creator’s changed-method reference

Spherical Ice links the evolution spreadsheet from the Gaia project thread. Its title is Pokémon Gaia v3.0 Evolution Methods. The thread describes v3.2 as a bugfix update within the v3 branch, but this guide does not relabel the spreadsheet as a separately tested v3.2 dataset.

Use the table as the maker’s linked v3 reference, then check the README bundled with your exact release. A randomized or otherwise modified output also needs its own configuration record; a vanilla reference cannot establish every rule after additional modifications.

The sheet says an unlisted Pokémon follows its ordinary official-game method. That is not proof that every species is obtainable in Gaia. For encounter scope and campaign limits, use the before-you-play guide. This page provides a focused selection of changed methods, not the entire species database.

How to evolve Haunter, Kadabra and other changed level evolutions

These rows give a level method rather than an external trade requirement. Check the actual party member, current level and installed instructions before the next level event. Do not use another hack’s Linking Cord or Link cable rule merely because it also changes trade evolutions.

The sheet does not explain every edge case for a Pokémon already above the listed level. Preserve the exact build context and consult its instructions rather than promising that reopening the game triggers evolution.

Which Pokémon use the Regal Stone?

The checked reference assigns Regal Stone to these six evolution targets:

• Clamperl → Gorebyss
• Seadra → Kingdra
• Poliwhirl → Politoed
• Slowpoke → Slowking
• Scyther → Scizor
• Feebas → Milotic

Choose the intended result before acting. Clamperl is a useful example: the same reference gives Huntail a level-38 method and Gorebyss a Regal Stone method. Those are two different branches; the Pokémon’s name alone does not tell you which action meets your goal.

For Feebas, the listed Regal Stone method is the starting point for Milotic. Do not import an official-game Beauty-training recipe or another Emerald hack’s Easier Feebas option as Gaia evidence.

This page establishes the listed targets, not the Stone’s exact acquisition point, price or availability in your save. Use the creator’s item-location reference for that separate lookup. No Regal Stone location is asserted here without reading its relevant entry.

An item-use method is different from a held-item level method

The evolution reference explicitly lists Porygon’s Up-Grade and Porygon2’s Dubious Disc as items used like stones. That is different from assigning an item to hold and then waiting for a level. Read the action as well as the item name.

1. Find the row for the current species and intended evolved form.
2. Identify whether it describes an item action, a level or a location condition.
3. Inspect the selected recipient and actual item before confirming.
4. Read the game’s prompt and check the resulting species afterward.

Example: you gave Porygon an Up-Grade because an official-game guide mentioned holding it during a trade. Gaia’s listed action is different. Repeating battles while holding it would not test the documented item-use route. Check the intended interaction before buying or searching for another copy.

If an action is rejected, retain the exact species, item and build information. Do not assume every evolutionary item shares the same use-versus-hold rule.

Choose the Eevee result before spending a stone

For the listed Umbreon and Espeon stone routes, start with that item requirement rather than changing the handheld clock to follow a day/night friendship recipe. For Sylveon’s move route, a move the species can learn is different from one this Eevee currently knows.

Example: your plan is Sylveon, but the current moves contain no Fairy-type move. Establish an available teaching route before the level attempt, or investigate the listed Shiny Stone alternative. This reference does not establish which route is faster or how conflicting evolution conditions are prioritized.

Glaceon and Leafeon use the location-based routes below. Choose the target first so a convenient stone or nearby level does not become an unintended branch.

For a location method, the level event must happen in the named place

These rows describe levelling in the specified place. Being in the same town, visiting the area earlier or gaining a level after leaving is a different condition. Inspect the current location and actual party member before spending the session training elsewhere.

The Glaceon entry names proximity to the Icy Rock. This guide does not invent a tile radius or an exact coordinate. Likewise, a location row is not a walkthrough proving that your current story progress can reach the site. If access is blocked, record that exploration prerequisite separately.

Example: Magneton gained a level on a route outside Telmurk. That event does not test the Warehouse condition. Confirm access to the named interior, then perform the relevant level event there and observe the result.

Why did the expected evolution not happen?

Describe what happened instead of reporting only “does not work.” A useful record includes the build, species, level, current moves, used or held item, location and the action taken. If those satisfy the matching rule but the result still differs, consult the creator’s known-bug guidance with that context.

A missing evolution is not evidence that the entire save is unreadable. If party and ordinary progress still reopen correctly, preserve that working result while investigating the specific rule.

Plan one evolution task for the next session

1. Name the current teammate and desired result.
2. Read its row in the creator-linked sheet and the matching package instructions.
3. Choose the missing resource: a level opportunity, an item, a known move or access to a location.
4. Prepare that condition without changing the game build or emulator at the same time.
5. Perform the named action, inspect the species and moves, then save through the game.

If the needed area is inaccessible, keep the teammate’s current battle role usable while progressing toward it. If the item is missing, make that one location lookup. This is an editorial task plan, not a fastest-route recommendation or an observed playthrough.

After a successful evolution, inspect the new move options before teaching a reusable TM. The Gaia move-planning section helps connect that change to the next battle rather than treating an evolved name as a complete team plan.

Sources and next steps

Spherical Ice’s project thread · Creator-linked evolution methods. Checked 8 Oct 2026. The direct sheet is the destination of the author’s GaiaEvolutionMethods link. No complete item-location or tutor dataset is reproduced here.

Gaia profile and patch requirements · Campaign, species and save boundaries · GBA handheld controls and saves