One of the reasons I picked up game dev was my years of being a dungeon master in Dungeons and Dragons. I always made my own campaigns, created entire worlds, and eventually our group even built an entirely new ruleset. After years of DMing I felt confident in my storytelling, crafting obscure and cryptic plots and weaving in philosophical, sociological, and psychological dilemmas.
So I thought: let’s do this in a video game, right?
My first game idea was exactly that. Luckily it took me only about three months to realize that the scope of a big narrative RPG was far beyond my limited game dev experience. So I scaled down, both in design and story.
I needed an idea that was simple but still compelling. Something people recognize at a glance so the game can build identity around it, while still having enough nuance to avoid being boring.
Who doesn’t like dragons? They’re a classic fantasy trope with endless variations. Is the hero going to slay the beast or seek its counsel? Is the dragon a ferocious monster or a mischievous companion? Or are dragons just a metaphor for an atomic bomb?
So I came up with a simple story and made the dragon the protagonist... or antagonist? You rule a small island and your job is to feed the beast. The deal is simple: keep its belly full and the island prospers. There are many dangers out there, from invaders and sea people to bloodthirsty pirates, sea monsters, krakens, and horrors from the deep. The dragon is your protector, but it comes at a cost.
Okay, maybe the atomic bomb metaphor actually fits.
At first I wanted to keep the storytelling minimal, giving small hints and bits of lore so players could form their own backstories. But then my publisher stepped in and immediately started coming up with ways to use the story when showing the game to the public. The game should tell a story, not hide it!
So you're telling me I should set my inner dungeon master free? Alright then. Let me tell you a story about a hungry dragon... cracks knuckles