"My RPG Was a Roguelike?!": Pivoting Without Losing Your Soul
My RPG Was a Roguelike?! Pivoting Without Losing Your Soul
Open the Wayline editors — pixel sprites, sheets, palettes, scenes — and export drop-in assets for Unity, Unreal, and Godot. Free to start, no signup.
It started as a sprawling RPG, the kind with branching dialogue, a meticulously crafted world, and a character arc that would make Tolkien weep. Two years in, I was neck-deep in crafting intricate systems. Then, playtesters kept saying the same thing: “It’s fun… but it takes too long to get anywhere.”
Turns out, I was accidentally building a roguelike. The core gameplay loop - exploring procedurally generated dungeons, battling enemies, and acquiring loot – was engaging. The overarching narrative, not so much. I faced a choice: force the square peg of traditional RPG structure into the round hole of engaging gameplay, or embrace the roguelike lurking within.
I pivoted. It wasn’t easy. This is how I navigated that shift, keeping the heart of my initial vision alive.
Identifying Your Core: What’s Worth Saving?
The first step is brutal honesty.
What are the absolutely essential elements of your RPG? For me, it was character progression and a fragmented, discoverable narrative. I loved the idea of players piecing together the world’s story through environmental details and item descriptions. I also wanted character builds to feel meaningful, even if runs were short.
Everything else was on the chopping block. The elaborate branching dialogue? Gone. The hand-crafted world map? Replaced with procedural generation. Quests? Streamlined into emergent objectives.
Make a list. Be ruthless. Ask yourself: “If this disappears, is the game still my game?” If the answer is no, fight to keep it. If the answer is maybe, reconsider.
Translating RPG Systems to Roguelike
This is where the real challenge begins. RPG systems often rely on long-term progression and permanence. Roguelikes are about impermanence and replayability. How do you reconcile that?
Think about abstracting your systems. For example, instead of a complex crafting system tied to specific locations, I opted for a simpler “infusion” system. Players could find elemental essences and infuse their weapons with them, granting temporary buffs and altered attack patterns. This preserved the feeling of character customization without requiring permanent resource management or backtracking.
Another crucial point: focus on meaningful choices within a single run. Gear choices become paramount. A single wrong turn can spell doom. Every decision matters. This intensity makes up for the lack of persistent character progression.
Prototyping the Core Loop
The most common mistake I see developers make is over-engineering before validating. Before you rewrite your entire codebase, prototype the core roguelike loop.
Strip everything back to the absolute basics: movement, combat, and a single type of loot. Can you create a 15-minute gameplay loop that’s genuinely engaging? If not, no amount of fancy systems will save you.
I built a simple prototype with placeholder art and minimal features. The goal was to answer one question: is this fundamentally fun? This focused approach saved me countless hours of wasted development time.
Communicating the Pivot
Announcing a major genre shift is terrifying. Your existing community likely signed up for something different. Transparency and clear communication are essential.
Explain why you’re making the change. Focus on the benefits: faster gameplay, increased replayability, and more frequent content updates. Show them the prototype. Let them experience the new direction firsthand.
Be prepared for pushback. Not everyone will be happy. But if you can demonstrate that the core appeal of your game remains intact, you’ll retain most of your audience.
I wrote a detailed blog post explaining my reasoning and included a video showcasing the prototype gameplay. I also actively engaged with comments and addressed concerns. This honesty built trust and helped the community understand my vision.
Balancing Convention and Creativity
Roguelikes are a well-established genre. Players have expectations. Ignoring those expectations entirely is a recipe for disaster.
However, simply cloning existing games will lead to genre fatigue. Find your unique angle. What can you bring to the genre that hasn’t been done before?
For me, it was the narrative. I doubled down on environmental storytelling and character flavor text. I wanted players to feel like they were uncovering a mystery with each run. This gave my game a distinct identity within the crowded roguelike landscape.
Actionable Steps
Here’s what I learned boiled down to a practical plan:
- Identify your RPG’s core elements. What absolutely MUST stay?
- Prototype the basic roguelike loop. Movement, combat, and loot. Is it fun?
- Translate RPG systems abstractly. Think about temporary buffs, emergent objectives, and impactful choices within a single run.
- Communicate transparently with your community. Explain your reasoning and showcase the new direction.
- Find your unique angle. What can you bring to the genre that hasn’t been done before?
Pivoting to a roguelike was a difficult decision, but ultimately the right one. It forced me to focus on what truly mattered: engaging gameplay and a compelling experience. It was about taking the soul of my RPG and reborn it in a new, more vibrant form. Embrace the challenge. Your game might surprise you.