• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • Our weekly protagonist poll is now up! Vote for your favorite Conquest protagonist in the poll by clicking here.
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.

Pokédex Generator

  • 1
    Posts
    14
    Years
    Hi all!

    I recently started developing my own fan game, for which I also wanted to come up with my own fakémon. Although I have no problem coming up with fakémon on the spot, I noticed I had difficulties coming up with a balanced pokédex - i.e. how many pokémon should there be of each type, how many evolutions should there be and so on. So I analyzed all existing Pokémon games to come up with a "formula" for all of these variables and wrote a python script, which gives you a pokédex template as a .txt file. It's definitely not perfect, but I thought this could be something that others also find helpful.

    To run it:

    1. Install Python (if you haven't already)
    2. Open up your command prompt
    3. Type: cd followed by the path to the location where you saved the script, and press enter
    4. Type: python pokedex_generator.py and press enter

    It will chuck out the txt file into the same folder as the script.

    If you have suggested improvements feel free to tell me, or even better - edit the script yourselves so that we can improve it.
     

    Attachments

    • pokedex_generator.zip
      1.6 KB · Views: 5
    An interesting experiment. I think this is specifically geared for a Gen1-like 'dex distribution? Made a few runs and examined the code and there's some things in there that definitively can be not there while still retaining some balance.

    So if you are looking for improvements, I'd say there are some logical "locks" you can remove (in particular in the valid dual types table) while retaining a good sense of 'dex-ness. I would have to take the time to examine the code a bit more closely and make more trial runs to get a feel of what the statistics of the generated 'dexes "feel" like to provide further feedback.

    Also, are you just learning Python or do have some good previous experience with it already? Just in case I can better shape any potential suggestions I could give.
     
    Back
    Top