How to Choose Metroidvania Map, Combat & Upgrades
This guide breaks down the three pillars of Metroidvania design—map layout, combat feel, and upgrade progression—so you can make deliberate choices that create a tight, rewarding game. You’ll learn what to prioritize at each stage of development, how to test your decisions, and how to avoid the pitfalls that make these games feel frustrating or empty. No prior game design experience is needed, just a clear idea of the experience you want players to have.
What You’ll Need
- A design document or notes app to record your decisions
- Access to a game engine (Unity, Godot, GameMaker, etc.) or paper prototyping tools
- A list of your favorite Metroidvanias and why you like them
- Time to playtest and iterate—this is not a one-pass process
Step-by-Step
- Define your core fantasy and movement verbs. Before drawing a single room, write down the one sentence that describes what the player does. Are you a nimble acrobat who dashes through the air? A heavy tank who smashes through walls? This determines everything: map density, enemy speed, upgrade types. For example, a fast, fragile character needs more save points and shorter corridors than a tank.
- Sketch the critical path first, not the whole map. Draw a simple line from start to final boss. This is the route a player must take if they never explore. Mark 3–5 major “gates” along that line—places where a required upgrade blocks progress. This ensures the game is always completable and prevents softlocks.
- Add optional branches off the critical path. For each gate, add 2–3 side areas that loop back to the main path. These should reward exploration with upgrades, lore, or health pickups. Make sure every side area has at least two entrances/exits so players don’t feel trapped.
- Design the map as a series of loops, not a tree. A good Metroidvania map has multiple connections between zones, so you never have to backtrack the exact same way twice. When you add a new area, ask: “Can the player get back to a previous area from here without retracing their steps?” If not, add a shortcut or a one-way door that opens from the other side.
- Choose combat mechanics that match your movement. If your character can dash, make enemies that require dashing to avoid. If you have a parry, design attacks that are telegraphed and punishable. Combat should feel like an extension of movement, not a separate system. Test each enemy against your movement verbs—if it can be beaten by standing still and mashing, it’s not using your game’s strengths.
- Define 3–5 core upgrades, each with a clear use in combat and traversal. The classic examples: double jump (reach new heights), dash (cross gaps and dodge), wall jump (climb vertical shafts), and a projectile upgrade (open doors and hit distant switches). Each upgrade should open at least one new area and change how you approach existing enemies. Avoid upgrades that are only used once—they feel like keys, not tools.
- Place upgrades at the end of meaningful challenges, not just in plain sight. The player should feel they earned the double jump by solving a puzzle or beating a mini-boss. If you put an upgrade in an easy-to-find room, it loses its impact. But don’t hide it behind an obscure secret either—players should be able to find it by exploring the area thoroughly.
- Balance combat difficulty with upgrade pacing. As the player gains upgrades, enemies should become slightly tougher or appear in new combinations. But never make an enemy that requires an upgrade the player doesn’t have yet—that’s a softlock. Instead, place stronger enemies in areas that require the new upgrade to reach.
- Playtest the critical path first, then the full map. Have someone play who has never seen your game. Watch where they get stuck, what they miss, and what they find by accident. Fix any point where they are stuck for more than 5 minutes without a clue. Then test with players who explore everything—make sure they’re rewarded but not overpowered.
- Iterate based on feedback, not just your own feelings. You will be blind to your own design flaws. Ask testers specific questions: “Did you ever feel lost?” “Did you ever feel too weak?” “Did you ever find an upgrade and not know what it did?” Use their answers to adjust map density, upgrade placement, and combat tuning.
Common Mistakes
- Making the map too large and empty. Bigger is not better. A map with too much empty corridor feels tedious. Fill every room with something: a puzzle, a fight, a lore note, or a hidden nook.
- Gating progress behind an upgrade that’s missable. If the player can skip the double jump and then reach an area that requires it, they’re stuck. Always ensure the critical path is linear enough that required upgrades can’t be missed.
- Combat that doesn’t evolve. If the same attack works on every enemy, the game becomes boring. Introduce enemies that force the player to use new movement or upgrades.
- Upgrades that are just stat boosts. A +10% damage upgrade is fine, but it’s not a Metroidvania moment. Players want new abilities that change how they interact with the world.
- Ignoring the map screen. A confusing map is worse than no map. Make sure the map is clear, marks unexplored rooms, and shows doors and elevators. Testers should be able to navigate without getting lost.
Tips
- Start small. Design a 10-room demo with one upgrade and one boss. Finish it, then expand. This prevents burnout and lets you test your core loop early.
- Use color and lighting to guide players. A bright area usually means safe, a dark one means danger. Subtle cues help players make decisions without explicit hand-holding.
- Place a save point before every boss fight, and a health refill after. This reduces frustration and respects the player’s time.
- Make every upgrade visible from afar. If the player sees an item on a ledge they can’t reach, they’ll remember to come back later. This creates “ah-ha” moments.
- Keep a design log. Write down why you placed each upgrade and enemy. When something feels off, you can trace it back to a decision.
Troubleshooting
- Players keep getting lost. Add more landmarks (distinct visual features), improve the map screen, or add signposts. Also check if your critical path is too long between save points—add a shortcut or teleport.
- Players find the combat frustrating. Reduce enemy health, add more invincibility frames to dodges, or make attacks faster. Also check if enemies are too fast—give them a wind-up animation.
- Players miss an upgrade. Move it to a more visible location, or add a hint (like a cracked wall that’s obvious). If it’s required, make it impossible to bypass.
- Players feel overpowered. Reduce the number of health upgrades, or make enemies scale slightly in later areas. But don’t nerf too hard—players should feel powerful after earning upgrades.
- Softlock discovered. If a player can get stuck without a required upgrade, add a back door or a way to return. Always test for this by playing through with minimal upgrades.
Frequently Asked Questions
How many upgrades should a Metroidvania have?
Most successful Metroidvanias have 5–10 major upgrades. Fewer than 5 feels sparse, more than 10 can overwhelm. Focus on quality—each upgrade should be used in multiple situations.
Should I design the map or the upgrades first?
Design the upgrades first, then the map. The map exists to test the upgrades. If you design the map first, you’ll have to retrofit upgrades and they may feel arbitrary.
How do I prevent players from getting lost?
Use a clear map screen, color-coded areas, and landmarks. Also, keep the critical path relatively linear—branches can be complex, but the main route should be obvious.
What makes combat feel good in a Metroidvania?
Responsive controls, clear enemy telegraphs, and a sense of impact (screen shake, sound effects, hitstop). Also, combat should be fair—if you get hit, it should feel like your fault.
How do I balance exploration and combat?
Alternate between the two. After a combat-heavy area, give a peaceful exploration section. After a long exploration, place a boss. This keeps pacing varied and prevents fatigue.
Can I use a random map generator?
Yes, but be careful. Random maps often lack intentional design. If you use one, add handcrafted “set pieces” (like a boss arena) and ensure the critical path is always generated correctly.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.