The Dragon's Covenant (WIP)

You can already choose a name if you romance either Zatus or Arael, but in Chapter 2 there will be an option for everyone to pick a new name, regardless of romance choices.

As for appearance customization, I originally planned to leave it up to the reader’s imagination—aside from the white hair and red eyes, which are the only defining traits. That said, I could add a few dialogue choices at the beginning for things like skin tone, hair length, etc, if people would prefer it. I just wasn’t sure it would add much since i dont think i’ll mention anything specific about that, but I’m open to including it!

16 Likes

Time to replay then, i played as “beneath it all over powered MC”.
So i didn’t care much about interaction beside my siblings.

2 Likes

Can Ruby or any of the other ROs help name us, i just really like that moment.

3 Likes

There will be a conversation about choosing a name with Ruby and Walls, but since they both believe the Warden should choose their own name—like a personal rite of passage, just as they did—they won’t offer any suggestions, unlike Arael or Zatus.

14 Likes

I figured they wouldn’t want to choose for you, what about the princess and prince?

4 Likes

I’m still unsure about them for now. When the Warden meets them again, I imagine they’ll have already chosen a name—even if they’re not in a romance—since quite some time will have passed since the end of Chapter 1. If they were going to pick a name, they probably would’ve done it by then. But that said, nothing is set in stone yet—I’m still figuring out the best way to handle it.

12 Likes

Did Ruby name herself after the eyes you get as part of the experiments?

3 Likes

No, Ruby is actually one of the very few experiments who can use dragonfire, and she takes great pride in that. Her flames burn a deeper red than most, which made her stand out. A few years ago, during a battle she was sent to, she overheard some soldiers talking—one of them was showing off a ring he’d taken from an enemy’s corpse, a red gemstone that shimmered in a way that reminded her of her own fire. She was captivated by it. When she learned the gem was called a ruby, she felt it was fitting—and decided to take it as her name.

22 Likes

How big was Azgor compared to other dragons?

3 Likes

The dragon the Warden faces in the arena had only just reached adulthood and was considered small by dragon standards—standing at about five meters tall and measuring sixteen meters from head to tail. In comparison, the largest dragon spotted in recent years would be three to four times that size. However, dragons of such immense size are incredibly rare nowadays. They take centuries to grow that large, and most of the truly massive ones were hunted down by the Aurelians during the height of their empire.

There are rumors of dragons even larger than that, said to dwell deep within the Dragonfell Mountains, hidden away from the world—but whether those stories hold any truth is still a matter of debate.

Humans know very little about dragons—their life cycle, culture, or society remain largely a mystery. The leading theory among scholars is that dragons continue to grow for as long as they live, without ever truly stopping.

Azgor, for instance, was said to rival the size of the largest Aurelian floating islands. He towered over even the biggest dragons known today. As for why he was so much larger than the rest, no one really knows—and so far he has refused to speak about his life before the war with the Aurelian Empire.

29 Likes

Cinema

3 Likes

Update 4 (12/04/2025)

Hey everyone!
Sorry this update took longer than expected—college has been rough lately. This update adds around 40k new words, bringing the total word count to 180k. It includes a follow-up to the end of Chapter 1 to help set the stage for what’s coming next, and also introduces two new romance options, who have been added to the Codex.

The stat screen has also received some changes. In addition to Combat Skill, you’ll now see Magic Skill and Flight Skill, both of which you’ll be able to train throughout the story. However, these new stats aren’t fully implemented just yet in this version.

This update is more of a sneak peek, mainly because I really needed some feedback. At the moment, choices in Chapter 2 don’t affect stats or relationship values. That will be added later, along with the full integration of the new skills, once I get a better idea of how everything is working.

Some Design Struggles

I ran into a few complications while writing this part, especially having to create two separate versions of scenes: one if you brought Arael with you, and one if you didn’t. Writing these branching paths is incredibly time-consuming and gets confusing quickly—and that’s just for one character.

  1. Optional Companions vs. Narrative Depth

Originally, the two new ROs were supposed to be optional companions—you could recruit them or send them away. But juggling every possible combination of companions quickly felt overwhelming. If I want to keep developing deeper, meaningful interactions with each character (which I really enjoy doing), this path feels unsustainable.

So I’m thinking of two options:

  • A) Make companions non-optional, allowing for richer, more integrated scenes.
  • B) Keep companions optional, but reduce their involvement in main scenes, instead reserving their content for side interactions or standalone relationship events.

I’m not the biggest fan of option B, but it might be the only feasible approach if I want to keep them optional and avoid burnout. I’d love to hear what you all think: would you rather have deeper scenes with non-optional characters, or keep the choice of companions even if their role is more surface-level?

  1. Too Many Arael Variations

I may have gone overboard with the variations in Arael’s path. Originally, when returning to Emberford, if she went with you, you could choose to carry her, leave her behind, or slow your pace so she could keep up. If you chose to slow down, you’d arrive late in Emberford. I had plans for that, but it started branching too far and became hard to manage—plus, I think most players would rather get there on time anyway, so i decided to cut it off for now.

From now on, I think I’ll need to simplify how I handle Arael’s path. I thought of two potential solutions:

  • A) Make it so Arael can’t become an enemy during the first encounter. She always sticks around after Chapter 2, either as just a companion or a romance option.
  • B) If you’re not romancing her, she disappears after Chapter 1 and hides somewhere else—essentially being written out. This way, I’d only have to write two versions (enemy and romance) instead of three.

Again, I’d really appreciate your thoughts on this. I’ll probably make a poll later, but for now i’d like to hear your reasoning or any suggestions you guys might have of alternative options!

Lastly, I was juggling so many variations that I might’ve missed some continuity details. If you notice any mistakes or inconsistencies, please let me know here so I can fix them.

Thanks so much for all the support and feedback so far—it really keeps me going.

38 Likes

There’s an error when I didn’t accept Azgor’s new power after the end of the Aurelian Battle and entering to chapter 2.

" Uncaught Error: afterbattlearael line 224: label ‘rescue’ is already defined on line 119 "

4 Likes

Option A sounds more logical. I’m all for lots of path variations but i think choosing who to interact with the most is sufficient. No real issue with a set number of companions.

Gonna go with A again here. I’d still like to have her around on a Ruby romance playthrough.

18 Likes

Thank you for reporting! It should be fixed now.

5 Likes

Yeah, I’m leaning more toward those options too right now. I didn’t want to remove the possibility for the MC to push back against her in that first scene, but it’s starting to feel like that might be the best call. I’ll just need to rework the scene a bit to make it fit better.

7 Likes

Honestly I think there’s probably too many ROs tbh, are those 2 new ones needed cause it’s up to 8 romance paths now.

Also error on solo non transformation path

4 Likes

I prefer both A) versions:

Making the companions non-optional in favor of depth sounds a lot better for the story. You can still add a lot of options to define your relationships with the characters without forcing a good relationship on anyone.

I’m also in favor of making Arael always a companion. Being on Zatus’ romance route I was sad to lack the option to being friends with her. Maybe you could add a few friendly meetings to keep in touch and then make her join MC on the way to Emberford?

Regarding the update I stumbled upon a few mistakes:

  • I couldn’t explore the non transformation route due to the error depicted above
  • Walls and Ruby suddenly knew my MC’s new name without having talked about it
  • a few references about being four people (“the four of us” etc. and Arael landing) despite not having Arael with me; but this might of course change anyway if you implant her as a non-optional companion

I really liked the remains of the transformation and am curious to see how everyone will react to those changes. My MC has found a good standing with the soldiers thanks to Zatus, so I’m really hoping this hasn’t ruined everything, lol.

I’m definitely excited to see where you are going with this!

6 Likes

Eight is a bit more than I originally planned, but I like all of them, and I think it’s still manageable for now. That said, I don’t think I’ll be adding any more.

Also, thanks for pointing out the error — it should be fixed now!

14 Likes

Thanks for pointing that out! I went through and fixed all the errors I could find, but if you notice any others, let me know and I’ll take care of it.

I originally planned to release this update right after finishing Zatus’ part, but I needed some feedback before moving forward. A follow-up update should be coming soon — it’ll cover their arrival at the camp and the decision on which path to take next.

8 Likes