Essentials Docs Wiki
Essentials Docs Wiki

When confronted with designing a pokemon game using Essentials, the developer is challenged to develop the front end of the software from scratch, as opposed from piggybacking off an already-established ROM. Pokemon Essentials gives the developer the engine to base their game off, however they are inclined to make everything else: the trainers, the maps, events (and plot), any custom moves, abilities, animations, and pokemon that have been introduced in generation 6 or later or any other fake pokemon.

There are many ways to skin a cat, and designing a pokemon fan game is no exception; however, let this serve as a simple road map for those just starting.

Skills to Do It Yourself

The main and most important skill while using RPG Maker is the manipulation of events. You can build an entire game with only this knowledge and mapping skills alone (or you could make a game entirely based off of a region of the official games). However, it is advisable that you learn about the capabilities of eventing before anything else. Learning how to be a good eventer will make you better see the possibilities of your game and, most importantly, how to solve a problem. Good exercises include, in a basic level, setting up a bank system and, in a more advanced level, how to make a calculator.

The following is a list of skills to improve your game development through RPG Maker with emphasis in Pokemon Essentials kit. While not all of them are needed, they can really help you along the journey.

  • Coding in Ruby or the ability to learn coding from previously established code;
  • Decent photo manipulation and graphic design skills in programs more powerful than MS Paint, notably ones that support transparency;
  • Ability to draw and sketch maps, trainers, and fakemon designs by hand, and draw them into said graphic manipulation programs;
  • A keen sense of design;
  • If you want to maintain the pixel density of all the sprites, a working knowledge of sprite art is required;
  • Project management skills is a must if you want to organize a team of people to help make assets for you;
  • Strong knowledge over niche battle mechanics, moves, abilities, and forms.

Groundworks for your Games Aesthetic and Theme

Starting out, it is easy to say "I want make a pokemon game!"

We already know what that is. Most people who develop pokemon game are already familiar with the series and have a good idea about what it looks like. Believe it or not, coming from there can be used as a start point. We already have a core: we have a game based around magical creatures that can be stored in pokeballs and can battle each other.

We're also familiar with the general structure of their games: a young trainer travels the region(s) to defeat many trainers and ultimately the Pokemon League while also at the same time become the region(s)' hero/heroine!

Jumping from there ask yourself:

"What is my idea that sets it apart from the main series?"

The main idea: Do you want to invert the story? Do you want to make it darker? Do you want to see what Let's Go! style gameplay in a Unova-inspired region might look like?

Your next question then would be: How do you want it to look? How do you want people to interact with your theme? How will the game's aesthetics match/or not match it?

The Next Step: Determining Where Your Game Is

The next big step in planning your game is to determine where it is, now that we know what it is.

If you want a tropical adventure, set it in the Seafoam Islands, reprise Alola, or make up a new region! That's up to you! Just make sure that the region's aesthetics will match the aesthetics of your game! If you want a warm sunny region with the plot as the next Poke-war, you're free to do so, but be aware that your players will go in expecting a happier adventure in a region with a bright, cheery color palette. Your fans that like dark, dank stories would also be disappointed in the fact that your region would not reflect the story and the game's overall aesthetic.

Now that you have decided where you would like to put it, get a rough drawing of what the region would look like. Don't go too far into the details right now, as they will reflect your plot. This is the time to look up images of cities and towns that could be turned into something like a Pokemon game.

Determining The Plot and Region

Now that you have some idea of where you want the game to take place and what it is about, it's time to think of the details more specifically and how they relate to your game map.

This is important because your player interacts with your region through the map. Before I get into the specifics of structuring your game map, this is the time to think about the structure of your Gameplay

Open Plot Linear Plot
Open Map Open/Open Open/Linear
Linear Map Linear/Open Linear/Linear
  • Linear/Linear: Most mainline pokemon games use this model: You're on a single track through the game, with small optional areas going through a plot that only has one possibility to be completed in a specific order
  • Open/Linear: Think the main series (dragon) plot from Bethesda's Skyrim. There is a strict linear flow to the game's plot despite being in an open world that you're free to explore with minimal gating.
  • Linear/Open: You approach areas in a linear progression, but are free to do whatever when you arrive there. The dragon age series, particularly the third, utilizes this. Eventually the story will culminate, but you're free to complete various subplots that distract from the main series.
  • Open/Open: Completely open; the game's plot is determined by discordant events that can be completed in any order. Skyrim becomes like this only after including all three major plot-lines in any order. Runescape does this especially well with each quest being a fixed difficulty, so some are easily stomped, and others are much more involved.

Determining which style of gameplay is imperative as it influences 1) pokemon levelling and balancing, 2) your map design, 3) how you structure your game's plot.

The traditional pokemon plot is gated by the gym leaders, or by the Island Captains/Kahunas in Alola, or progress in defeating Cipher in the Colosseum games. As a fangame developer, you are in complete control over what it will be like as RMXP supports all four of those play styles. It's up to you to choose a format that works for your game.

Please note that Open World pokemon maps are possible, though it becomes complicated when you have to consider the technical aspects of the game design because an individual Pokemon's power is in the form of leveling and you would have to make 8 variations of each gym if you want it truly open (and be able to complete each gym in any order you please). You also need scripts that will scale wild encounters appropriately with the correct gating.


Once you've determined the format of your game, how do you want to gate the player's progress through the game? Do you want the traditional gym system? Do you want to do Trials and Kahunas like in Alola? Essentially, how do you want your players to progress through the story? Will there be a rival with battles? Where would they be in the towns, cities, a magical place in the sky? The sky is the limit, but figuring them out will give you a mental checklist to incorporate into your game and its map and plot. They can be unrelated to the plot, but gating needs to be specified on your game map or at least implied. Otherwise, players would have to keep a mental tally on where that Snorlax was sleeping in the middle of the road or determining where they need to Surf, etc.

Who are the People of your Region

Now you know how to gate and how the player should interact with your game's world, it is time to determine who occupies it! This is important as it directly determines your plot! There are games that have no characters but even with those the landscape/puzzles become the characters!

We are all familiar with the teenage/child protagonist often single-handedly toppling a large, criminal organization that somehow has plans to destroy the world. And despite the region's best attempts by the actual police, only a child who started their pokemon journey hours before managed to topple them completely before challenging the pokemon league. 

As a game developer you're free to both adapt that, rewrite it, or embrace it! As long as you can fit it into your game's planned structure, you should be fine!

Some other questions to be mindful is how the setting influence their looks? What they wear, what their hair color is? Do they have lives? Do they go to work, have families, have different rules in society than ours? It may sound trivial, but characters play an integral role in establishing your game's plot and aesthetics. Notice how everyone in Kalos looked super French? Many berets were worn, walking their Furfrou in front of a building that looked suspiciously like the Eiffel Tower? How Team Flare was obessed about Fashion? The people of a region make it feel alive!

Sketching Your Map

Now that you have everything above considered, it is time to start sketching your map!

It is a good idea to play out the plot as you are placing the cities in your head as you design it (especially true if you chose the Linear/Linear game structure).  

A structural diagram of a pokemon map

The details of pokemon game's plot can be worked out as you draw a map. If you're basing your region off an established place on Earth, a common newbie mistake is including too much of that area in your map. You should feel free to warp space and leave out cities and towns that don't contribute anything for the player or their experience. It is a bad idea to make a map and then stick a plot on it. A smarter way to approach mapmaking and developing your plot is play it out mentally as you make it. A pokemon map can be as simple as the drawing to the right or as convoluted as something from Generation 5 or 6, or even 7. At this stage it's imperative to get the route structure down before applying the later aesthetics. 

For Linear maps with a linear plot, there should be a clear starting point and a clear ending point. Pokemon maps are made to be simple enough a child can read it but complex enough to imply the entire game's progression.

Pokemon and Writing your Pokedex

Now that you have a region with characters planned, and a general idea about the characters, time to start making the game! 

The next part is assembling a list of what pokemon to include. Pokemon Essentials by default has every pokemon introduced up to generation 5. You will have to add every pokemon manually after that, in addition to the Fairy type and any other custom types/fakemon.

Assembling a Pokedex can be an interesting challenge considering that there are so many to choose from. To start, it is a good idea to consider how many pokemon should be available:

Each main series game has a different number, before the postgame:

  • Kanto: 150
  • Kanto (LGPE): about 175
  • Johto: about 250
  • Johto (HGSS): about 300
  • Hoenn (RSE): about 250
  • Hoenn (ORAS): about 300
  • Sinnoh: about 150
  • Sinnoh (Pt): about 200
  • Unova: about 150
  • Unova (B2W2): about 300
  • Kalos: about 450
  • Alola: about 350
  • Alola (USUM): about 400

While there are fangames that claim to have all 809 currently available pokemon, it gives the developer a headache to find ways to make it feel less overwhelming for the player and themselves. Essentials supports 12 different encounter rates for pokemon on normal tall grass, and only 5 different percentages for Surfing, so if you want to develop a pokemon game will the pokemon, it will get chaotic. Luckily v17.2 has all of the gen 6 moves and abilities coded. It is your job to update the PBS files. You will have to program all of the Gen 7 moves and abilities.

Larger pokedexes will naturally lower the game's difficulty, so having too much variety in pokemon can make a would be difficult game easily curb-stomped despite the rich variety of choices. However, too few pokemon forces the developer to limit the variety of pokemon for the player both to use and encounter, but makes the difficulty curve more manageable.

Generally, all of the regional pokedexes order the pokemon in the order they are encountered in their respective games. Therefore, it makes it somewhat easier on the developer as players going in to the game exepect your regional pokedex to reflect that. 

Your pokedex will go through many drafts as you develop the game, so unless you choose to make fakemon, your pokedex can remain flexible until you finalize your encounters, battles, and difficulty curve later on the road.

The pokemon games incorporate the Pokemon's rarity, approximate strength (BST) and it's typing and abilities when placing them in a route/trainer battle, and thus should be considered when making your game. No one likes route 1 legendaries. They make no sense. Early game pokemon such as rattata, pidgey, the elemental monkeys, poliwag, oddish, purrloin, bunnelby, etc., are all great pokemon with simple typings and movesets that give the player an illusion of variety right after picking your starter (discussed in the next section). Consider the terrain, as that is a direct implication about what pokemon could be there! It would be silly fishing magikarp out of lava (it would make sense to find slugma there). It would make more sense for wingull to be found on an early coastal map than in a dry desert in the middle of your region!

If you have Fakemon, now is a good time to start sketching them!

The Starters

Perhaps the most important part of Pokemon (and perhaps even more important than the box legendaries) are your starter pokemon. Nailing who they are, and what types they are is essential to starting a fangame. We're very much used to the fire/water/grass trio, or the pikachu/eevee, umbreon/espeon in the spin-offs. They can be real pokemon, or fakemon, or can be of non-standard types. What matters is how they appear and how do they fit in the game's difficulty curve. If you have a fire type starter and the first three gyms are weak to fire, then you have a poor gym structure. The opposite is also a poor structure. In Kanto, if you chose Charmander, there would be no STAB move to defeat Brock!

Mapping and Eventing

Now you have the Pokedex planned out, time to start making game maps! You can use the default tilesets preloaded into essentials or you can create your own. The wiki has extensive documentation on how to event and use the RMXP mapping tools. A quick google search will reveal that there are hundreds of public tilesets and characters for the overworld on the internet! However, make sure that you have permission to use them, otherwise you can have your project taken down for plagiarism!

Building A Team

Once you're out of the planning stages, implementation of the game can be overwhelming for one person! You may have to recruit a team to help you make whatever you need for this project to see light of day! Be aware that working on a team as the lead dev that it is expected that you will be doing most of the work. Fangame development is different from professional development because most people would have to pay out of pocket to commission someone. If the developer cannot do their part, they are liable to being booted off their team! Likewise, if you haven't done much for the project at the start, people are not likely to join your team or take it seriously if they do join. Even if your sketches or maps are of poor quality they can always be redone--fangames can take years to complete.

This is where your project management skills will take shape! You need to make sure everyone is submitting everything on time at a high enough quality to present.