Romance in progression fantasy almost always feels tacked on because the love interest stops progressing the moment she is caught. The fix is to treat the romance as its own progression arc, with stakes, setbacks, and earned milestones that scale alongside the power curve, rather than as a single resolved subplot that gets shelved when the MC moves to the next tier.
I think the reason romance is the single most-complained-about element in progression fantasy is structural, not a question of the writers being bad at love scenes. Power fantasy and intimacy want different things from a story, and most authors only notice the conflict between those two things after they have already locked themselves into a relationship arc that has nowhere left to go. My feeling about this is that you can have both, and some of the best-loved books in the genre prove it, but only if you stop treating romance as a subplot you "finish" and start treating it like everything else in the book: a progression curve with its own stages, its own setbacks, and its own earned breakthroughs.
What makes romance in progression fantasy feel forced
The romance feels forced because it gets one arc when the rest of the book gets fifteen. The MC trains in the basics for a hundred chapters before he unlocks his second skill, but he falls in love (and is loved back) inside a single rescue scene, and then the relationship is treated as settled forever. Think about that pacing asymmetry on its own. We accept that physical strength has to be earned in small, painful increments, and we accept that magic systems have to be discovered piece by painstaking piece, but we accept (or rather, we don't accept, and we complain about it constantly) that the emotional core of the book gets a single fight scene and a single yes. So the dungeon takes three chapters and the proposal takes two paragraphs, and the whole subplot reads like an afterthought because, structurally, it is an afterthought.
The other half of the problem is that progression fantasy MCs usually cannot be vulnerable. Lindon in Cradle can be vulnerable because he starts as Unsouled and earns his confidence in real time; Jason Asano in He Who Fights with Monsters by Travis Bagwell, sorry, by Shirtaloon, gets to be vulnerable because of his trauma; but the median power-fantasy MC is built specifically to avoid vulnerability, because vulnerability is the opposite of the wish-fulfillment readers came for. And good romance, the kind that actually moves people, requires both partners to be vulnerable in front of each other. The single most underrated scene in any love story is not the first kiss, it is the scene where one of them admits the secret they have been carrying since they met. Progression fantasy structurally resists that scene, because the MC has to be the strongest, the smartest, the most clever, and the most self-contained in every room he walks into. If he tells the love interest his real fear, he loses the thing the readers came to watch.
Treat the love interest as a second progression arc, not a reward
The fix that actually works, the one you see in the books that get held up as the genre's best examples of romance, is to give the love interest her own progression track. Path of Ascension by C. Mantis is the example that came up over and over in the genre community recently, and the reason it works is structural: Persi and Liz are not "the girls the MC saved", they are tracked characters with their own classes, their own training arcs, their own complications, and their own milestones. The romance feels earned because the romance is the outcome of a parallel progression, not the prize for the main one. The relationship has somewhere to go in book four because the partners had somewhere to go in book one, and book two, and book three.
Compare that to the Pokemon collection dynamic that readers complain about so consistently. The MC meets a beautiful warrior in chapter six, saves her from a stronger enemy, she falls madly in love, and then she gets parked in his sect, his dimensional storage, or his hometown for the next three hundred chapters while he travels and levels. The romance never progresses because the love interest never progresses. She is not a character, she is a trophy that talks. And once the reader notices this, the love interest stops functioning as a person and starts functioning as a stat block with a name and hair color attached. There is nothing in the love interest's arc that the reader cares about, so the romance has no payoff to deliver. She gives Jason a look that means everything, and she is still standing in the foyer when he returns from his tournament victory three months later. That sentence is what most progression-fantasy romance reads like, and it is the structural problem in miniature.
The mental shift is to ask: what does the love interest want, outside of the MC, that the MC cannot give her? Yerin in Cradle by Will Wight wants revenge for her master. Vella in Mother of Learning by nobody103 wants survival, then revenge, then a partner, in that order, and her arc is legible whether or not Zorian is in the scene. Erin in The Wandering Inn by pirateaba is not even primarily a romantic figure, but every character orbiting her has a clear independent project. If you cannot answer the question of what the love interest is doing when the MC is not in the room, the romance is going to feel like a transaction every time.
The pacing problem solves itself once the love interest has her own arc
This is the part I think most authors miss. Once you give the love interest a parallel progression, the pacing complaint about romance basically disappears, because you stop trying to "fit the romance in" and start writing the romance as one of the things the book is about. The dungeon chapter is three chapters because it advances the MC's progression. The conversation in the camp the next night is also a full chapter, not a paragraph, because it advances the love interest's progression, and the romance progression, simultaneously. 'You spent four hours staring at the same page of the cultivation manual after he left,' the older sister said, not looking up. That single line, dropped in a chapter from the love interest's POV, does more for the romance than ten pages of the MC noticing her hair. And it costs you almost nothing in word count, because you were going to write the camp scene anyway. You just allocated some of its weight to a second arc instead of letting it default entirely to the power system.
My advice, then, is to think about romance the way you think about any other progression curve in the book. There should be stages. There should be setbacks. There should be a clear in-world cost for moving to the next stage, and a clear in-world benefit. The first stage might be they fight together and learn to read each other's combat tells. The second stage might be one of them admits the thing they have not told anyone else. The third might be they have to choose between his progression and hers and one of them gives ground. None of those stages are unique to romance writing, by the way; they are the same beats you would hit in a master-student arc or a rival-to-friend arc, just with a different emotional charge. Romance is hard in progression fantasy not because love is hard to write, but because the genre's default storytelling mode treats every non-power-track element as a side quest, and a side quest can only carry so much emotional weight before the reader stops caring about it.
What this looks like on the page
Concretely, the rule of thumb I find useful is one scene per power-tier arc, plus one quieter chapter between major fights, plus at least one POV from the love interest per book. If you are writing in tight first-person and a POV switch is off the table, you can substitute a scene where the love interest is observed by a third character who is not the MC, which lets the reader see her acting without him in the room. Travis Baldree-style cozy progression fantasy gets away with a lot of off-screen romance because the books are calibrated for low-stakes vibes; high-stakes cultivation fantasy in the Cradle or Defiance of the Fall mold cannot afford the same shortcut, because the contrast with the rest of the book is too sharp.
The other concrete thing I would push back on is the one and done framing. A romance does not "resolve" once they get together, any more than a cultivation arc resolves when the MC reaches Silver rank. Getting together is a stage; you should have at least three more stages mapped out for the relationship after that, and each of those stages should have its own progression beats. Sky Pride by Hyperion is, in my view, the genre's strongest current example of a romance that keeps progressing after the partners are officially together, because the partners' goals keep diverging and re-converging as their power grows. The relationship feels alive because it is still doing work, still being negotiated, still costing both of them something. That is what makes it feel real, and that is what most progression fantasy romance fails to do.
So no, I don't think romance is impossible in this genre. I think the genre's structural defaults are pointed in the wrong direction, and most authors are fighting that current instead of redirecting it. If you write the love interest as someone with her own arc, give the romance its own stages, and pace it proportionally to the power system, the complaints that fill every genre forum on the topic mostly evaporate. The few books that have done this well have done so by treating intimacy with the same craft seriousness they bring to combat scenes, which is, when you think about it, a pretty low bar. We just don't clear it very often.
Common questions about writing romance in progression fantasy
Why does romance feel forced in most progression fantasy?
Because the romance gets resolved on a single arc while the power system keeps progressing forever. Once the love interest is won, she is parked off-screen while the MC keeps leveling, so the relationship has no further beats to hit. The fix is to keep the romance progressing on its own track with new stakes at each power tier, not to finish it in book one.
Can you have romance and a power fantasy at the same time?
Yes, but only if the romantic partner has her own arc. Path of Ascension by C. Mantis works because Persi and Liz progress alongside Matt and earn their own milestones. If the love interest exists only to admire the MC, the romance reads as a trophy, not a relationship, and most readers will check out of the subplot within a few chapters.
What is the worst romance trope in progression fantasy?
The instant-bond from a single rescue. The MC saves a girl from a monster or slavers in chapter three, she falls in love by chapter five, and the relationship is treated as settled forever. This collapses what should be the most dramatically rich part of the book into a single transaction and tells the reader that intimacy is something you earn with stats, not character.
How much page time should the romance get?
Roughly proportional to its narrative weight, which usually means one scene per power-tier arc, plus a single quieter chapter between major fights. If a dungeon fight gets three chapters and the romance resolution gets two paragraphs, the asymmetry will read as forced no matter how good the prose is. Match the pacing to the stakes.
Should the love interest be as strong as the MC?
Not equal in raw power, necessarily, but equal in narrative agency. She needs to want something the MC cannot just hand her, and she needs to act on it on the page. A love interest who is fifty levels behind but driving her own plot lines feels alive. A love interest who is the same level as the MC but exists to react to him feels like a stat block with hair.
by Jacob Tam · June 4, 2026
I run IlorisNovel, a platform for writers of web fiction. If this kind of craft writing is your thing, the rest of the blog lives here.