Organizing Your Project
Creating a fangame isn't just about building maps, events, or sprites.
It's also about making decisions, making choices, keeping the bigger picture in mind, and knowing where your project is heading.
At the beginning of a project, everything seems simple. You remember every idea and every detail. But after a few weeks, or even a few months, it becomes much harder to keep everything in your head.
The purpose of good organization isn't to make your project look more "professional."
Its purpose is to save you time.
Your Memory Is Not a Project Management Tool
We've all had this thought at some point:
"I'll remember it later."
A few weeks go by.
Then a few months.
And suddenly, questions start appearing:
- Why did I create this variable?
- Is this quest finished?
- Which Pokémon was supposed to appear on this route?
- Why is this character here?
Your memory is excellent at generating ideas.
It's much less reliable when it comes to remembering them over the course of several years.
Get into the habit of writing down the things that matter.
A few lines are often enough.
Example 1
"I'll remember how this quest is supposed to work."
Write a short summary that explains:
- the context
- the characters involved
- the objectives
- the rewards
A few months from now, you'll be glad you did.
Keep Your Information in One Place
One of the most common mistakes is scattering information across multiple places.
The story is in Discord. Your Pokémon list is in a notebook. Your ideas are buried in private messages. Your tasks are in a text file.
After a few months, finding a single piece of information turns into a treasure hunt. Try to keep your project information centralized in as few tools as possible.
It doesn't matter which tools you choose. What matters is always knowing where to look.
Example 2
You can perfectly manage a project using:
- one document for your story
- one board to track your tasks
- one place to communicate with your team
Three tools that you use consistently are far better than ten that you rarely open.
Break Your Work into Small Tasks
Saying:
"Create the first town"
is a goal. It isn't a task.
A good task should be small enough to complete in one or a few work sessions.
Example 3
Instead of:
Create the first town
Break it down into smaller tasks:
- design the town layout
- create the map
- add the buildings
- place the NPCs
- write their dialogue
- create the main events
- test the player's progression
These smaller tasks make it much easier to measure your progress and make every work session feel more rewarding.
Once you've completed several tasks, you'll be able to release a new version of your game. Each new release is an Iteration: another step forward in your project's development.
Know the Difference Between "In Progress" and "Done"
As your project grows, it's tempting to work on several things at once.
A route. Then a town. Then a Pokémon. Then an interface. Then a mini-game.
After a while, everything is "almost finished"... ...but nothing is actually finished.
Try to limit the number of things you're actively working on at the same time.
Finishing a task gives you visibility, reduces your project's complexity, and makes it easier to keep moving forward.
Example 4
Having ten maps that are all 80% complete.
Finish one map before moving on to the next, unless a technical dependency genuinely requires you to do otherwise.
Document for Your Future Self
The version of yourself working on this project a year from now won't see it the same way you do today.
You'll have forgotten certain decisions. You'll have learned new things. You'll wonder why you made some of the choices you did.
A short note explaining why something exists is often much more valuable than a long explanation of how it works.
Example
Writing: "Variable 248"
Write: "Variable 248: the player has received permission to enter the nature reserve."
Just a few extra words are enough to make your project much easier to understand.
You'll also occasionally reorganize your code or your events without changing how the game behaves. This process is called Refactoring.
Tools Don't Move Projects Forward
There are countless tools available for organizing projects.
Task boards. Documents. Project management software. Collaboration platforms.
All of them can be useful. But none of them can replace a simple, consistent workflow. Changing tools every month is rarely the solution.
Before looking for a new tool, ask yourself whether your current workflow actually prevents you from doing what you need.
Most of the time, a few good habits will have a much greater impact than a more sophisticated piece of software.
Conclusion
Here are some situations we regularly encounter in amateur projects.
- Starting development without ever writing down important ideas.
- Multiplying tools until nobody remembers where information is stored.
- Creating tasks that are far too large to accurately measure progress.
- Working on too many things at once without finishing any of them.
- Giving resources, variables, or events unclear names.
- Thinking that documentation is a waste of time.
Good organization doesn't require much effort.
But it can save you dozens or even hundreds of hours over the lifetime of a project that may take several years to complete.