Add missing evolution entries

[FreakMediaLP]

Change description

Added missing evolution locations:

• "New Mauville" for "Magneton" and "Probopass" (available in ORAS)
• "Petalburg Woods" for "Leafeon" (available in ORAS)
• "Shoal Cave" for "Glaceon" (available in ORAS)

AI coding assistance disclosure

Used AI to get a better understanding of the pokemon_evolutions.csv and its connections with other .csv files.
All changes were made manually though.

Contributor check list

• I have written a description of the contribution and explained its motivation.
• I have written tests for my code changes (if applicable).
• I have read and understood the AI Assisted Contribution guidelines.
• I will own this change in production, and I am prepared to fix any bugs caused by my code change.

[Naramsim]

Hi! For Leafeon I see that being close to a Moss Rock is needed for eevee to evolve. Is there a way to map this requirement?

And for Gleceon one must be at the lowest level of the cave: https://pokeapi.co/api/v2/location/445 Which in the API is a location-area. Can we also map that?

[FreakMediaLP]

And for Gleceon one must be at the lowest level of the cave: https://pokeapi.co/api/v2/location/445 Which in the API is a location-area. Can we also map that?

The pokemon_evolution.csv currently has no attribute for "location_area", only "location_id". This addition or change would mean a lot of work and research, as there will most likely be more evolution chains, which would need to be updated as well.

But this might not be necessary, because as you stated, Leafeon requires sth like "close-to-moss-rock", and also Glaceon requires "close-to-ice-rock" (The "lowest level of the cave" just happens to be the area, where ice-rocks can be found).
The reason why I just added the "location_id" was, beause at the moment, every (level-up) evolution only has a "location-id" and as stated above, there is no attribute for "location-area"

---

Leafeon (470)

Row	Trigger	Condition	Resolved
238	1 (level-up)	location_id=8	eterna-forest
324	1 (level-up)	location_id=375	pinwheel-forest
363	1 (level-up)	location_id=650	kalos-route-20
407	3 (use-item)	trigger_item_id=85	leaf-stone
548	1 (level-up)	location_id=438	petalburg-woods ← new

Glaceon (471)

Row	Trigger	Condition	Resolved
239	1 (level-up)	location_id=48	sinnoh-route-217
325	1 (level-up)	location_id=380	twist-mountain
364	1 (level-up)	location_id=640	frost-cavern
408	3 (use-item)	trigger_item_id=885	ice-stone
549	1 (level-up)	location_id=445	shoal-cave ← new

But how should these methods be added? It wouldnt make sence to add them as a "location_id", neither as a "location-area" and at the moment, every (level-up) evolution for these two has a "location_id" mapped, so ALL of them would need to be adjusted.

How would you suggest, we should add these (level-up) methods/areas?

[jemarq04]

There are only 19 location-based evolutions currently in the database. I'm familiar with updating the evolution details, so if we think it would be more descriptive I can go in after this PR and update these locations to point to the relevant location areas. That still wouldn't be able to specify things like "close-to-moss-rock", as there are no evolution conditions like there are for encounters. But I think it would be sufficient.

What do we think?

[FreakMediaLP]

Sounds good, I unfortunately dont have the time, to go through all, If you could do that, that would be great

[Naramsim]

We can merge this PR as is since the current schema doesn't provide all the fields necessary to be that specific. @FreakMediaLP is right, that would require probably going through many pokemon/evolutions to update all the DB.

[jemarq04]

Ok sounds good. Once this PR is up-to-date with the base branch we can merge and I'll get started on the additional PR when I get the chance

[Naramsim]

Thank you all a lot!

[pokeapi-machine-user]

A PokeAPI/api-data refresh has started. In ~45 minutes the staging branch of PokeAPI/api-data will be pushed with the new generated data.

The staging branch will be deployed in our staging environment and the entire API will be ready to review.

A Pull Request (master<-staging) will be also created at PokeAPI/api-data and assigned to the PokeAPI Core team to be reviewed. If approved and merged new data will soon be available worldwide at pokeapi.co.

[pokeapi-machine-user]

The updater script has finished its job and has now opened a Pull Request towards PokeAPI/api-data with the updated data.

The Pull Request can be seen deployed in our staging environment when CircleCI deploy will be finished (check the start time of the last build).