Open tthverst opened 8 years ago
Yeah I like that :)
Should we only have the new cries, old ones when applicable, or both?
The veekun link has both old and new cries. So I guess we can do both.
What would be the approach legally speaking?
What is the legal approach with sprites?
@cgbsu Your comment is a bit out of context. I redirect you here for your question: https://github.com/PokeAPI/sprites/issues/38
FYI here is an api for pokemon cries https://www.pkmnapi.com/endpoints/pokemon-cries/ @tthverst maybe you could add it in your initial post
Is work on having pokemon cries in the api still an option or has this idea been dropped if its fine I could make a pr for this (PS: I think it's a great idea to have pokemon cries as an additional resource under the api)
It would be pretty cool if the pokémon cries would be included in the API, I guess their implementation would be quite similar to how the sprites are implemented.
The response for endpoint
http://pokeapi.co/api/v2/pokemon/1/
would then contain a new key => value pair. Something like the code below:"cry" : "http://pokeapi.co/media/sounds/pokemon/cry/1.ogg"
The first step would be to gather the resources for this, the sound files would need to have the appropriate format for web playback, so MP3, OGG, or WAV would be safe choices.
The link below is one I found, but there could be better ones out there so I would appreciate your input on this.
UPDATE: I added another link for the cries.
Resources
http://www.smogon.com/forums/threads/pok%C3%A9mon-xy-remastered-cries.3512615/ http://veekun.com/dex/downloads#other-files