Making Good Decisions
Throughout the development of your fangame, you'll make hundreds of decisions.
Some will be major. Others will seem insignificant. Yet every single one of them will have an impact on your project.
Should you add a new mechanic? Redo this map? Create a new Fakemon? Accept a player's suggestion? Recruit another contributor?
There are no universal answers.
However, there's one question that's worth asking yourself almost every time:
Will this decision actually move my project closer to its next goal?
If the answer is no, it may be better to wait.
A Good Idea Isn't Necessarily a Good Priority
Fangame creators are full of ideas. And that's a great thing.
But not every good idea needs to be implemented right away. Some ideas will become far more valuable later.
Example 1
You're currently working on your first Gym. Suddenly, you come up with the idea of a dynamic weather system that affects the entire world.
It's probably an excellent idea. But is it more important than finishing your first demo? Most of the time, the answer is no.
Write the idea down. Then get back to your current goal.
"Later" Doesn't Mean "Never"
Many creators are afraid of losing a good idea. As a result, they feel the need to implement it immediately.
The outcome is often the same: the project constantly changes direction.
Instead, get into the habit of keeping a list of ideas. That list becomes a reserve you can come back to when the time is right.
You may even be surprised to discover that some ideas which once felt essential no longer seem that important a few months later.
Every Feature Has a Cost
When you add a new mechanic, you're not just writing a few lines of code.
You're also adding:
- design time
- development time
- testing
- bug fixes
- documentation
- long-term maintenance
The larger your project becomes, the higher that cost grows.
Before adding any new feature, ask yourself:
Does the value it brings to the player truly justify all the work it requires?
When a feature is implemented too quickly without enough planning, it can make future development more difficult. This is known as Technical Debt.
Player Feedback Is Valuable... But It Isn't a Checklist
Playtesting your game is incredibly valuable.
Players will notice issues you've become blind to. They'll also come up with plenty of ideas. Some of those ideas will genuinely improve your game.
Others will simply reflect their personal preferences.
Your job is to listen to that feedback, then decide whether it aligns with your vision.
Example 2
One player asks you to add Mega Evolutions. Another prefers Dynamax. A third wants Fakemon.
You can't satisfy everyone.
What you can do is build a coherent experience that stays true to the goals you've set for your project.
Be Careful About Starting Over
Sometimes a system genuinely deserves to be redesigned.
But starting over should never become your default solution.
As you gain experience, your skills will naturally improve.
You'll always be capable of producing better work than you did a few months ago.
If you constantly restart your work, your project may never actually move forward.
Example 3
"Now that I'm better at mapping, I'm going to remake every route."
A few months later:
"Now that I understand events better, I'm going to redo everything."
Then:
"Now that I've changed the art style..."
The project stops moving forward.
Continue developing your game and only revisit older content when there's a genuine reason to do so.
Don't Add a Feature Just Because It Exists Somewhere Else
The official Pokémon games include countless mechanics. So do many fangames.
That doesn't mean your project needs every one of them.
Every feature should answer one simple question:
How does this improve the player's experience?
If you can't clearly answer that question, it may be better not to add it.
Knowing When to Let Go Is Part of Development
Some ideas will have to be abandoned. Sometimes because they require too much work. Sometimes because they no longer fit your project. Sometimes because you've found a better solution.
Letting go of an idea doesn't mean you've failed. It means you've made a decision that allows the rest of your project to move forward.
The best creators aren't the ones who implement every idea they have.
They're the ones who know which ideas are worth saving for later, or leaving behind altogether.
Conclusion
Here are some decisions that regularly slow projects down.
- Adding a new feature before finishing the previous one.
- Constantly changing priorities whenever a new idea appears.
- Implementing every player suggestion without taking a step back.
- Rebuilding large parts of the game simply because your skills have improved.
- Trying to include every mechanic from the official Pokémon games.
- Holding onto features that nobody wants to remove, even when they make the project unnecessarily more complex.
Making good decisions doesn't always mean saying "yes."
More often than not, the best decision is the one that keeps your project moving forward, even if it means postponing... or abandoning... an excellent idea.