When the Moon Hatched Book Recap
Some of the links on this blog are affiliate links, which means I earn a small commission if you make a purchase. This helps support the blog at no extra cost to you. Thank you for your support! Click to read my Disclaimers for more info.
So the story kicks off with gods doing what gods do—creating a whole world and low-key causing problems in the process. You’ve got five Creators shaping everything: land, water, air, fire… and then Caelis, who basically set the stage but got stuck being invisible and ignored. Which—let’s be honest—already feels like a setup for future drama.
They create dragons (iconic), magic through songs (cool), and runes (also cool but slightly suspicious). But then people start killing dragons… and instead of just dying normally, these dragons turn into moons. Which sounds beautiful until those moons start falling out of the sky and wiping everything out.
After seven catastrophic moon crashes, everyone blames Caelis (because obviously), rips his essence apart, and traps him in the Aether Stone with a long-term babysitter situation that gets passed down through generations. Problem solved… for a few million years.
Until—surprise—a moon starts falling again. So yeah, things are not fine.
Now enter Raeve.
She’s an assassin pretending to be harmless, which is honestly her brand. She infiltrates this fancy club, lures out a terrible man (Tarik), and casually suffocates him with air magic like it’s just another Tuesday. Her mission? Kill him and grab his hand (yes, literally) so her people can access his operation where he’s exploiting kids. So, morally gray shadow daddy—but we’re still rooting for her.
On her way out, she runs into this random mysterious man who’s asking way too many questions. They have a weirdly charged conversation, and then part ways like that wasn’t suspicious at all.
Buy the Books
Raeve’s whole life is basically: trauma, missions, and trying to protect others the way no one protected her. The only soft place she has left is Essi—her best friend, the one person she actually loves.
And then… yeah. That gets ripped away.
Essi dies. Brutally. And Raeve has to sit there, hold her, and promise to burn her body. Which she does—along with their entire home—while admitting her feelings way too late (because of course).
That’s the moment Raeve completely breaks.
She unleashes The Other inside her (which is as terrifying as it sounds), goes on a full destruction spree, and gets captured by Rekk—the literal worst human alive, who also happens to be the one behind Essi’s death.
Now Raeve’s imprisoned, half-broken, and heading toward a trial that is very much a death sentence.
And guess who shows up?
That same mysterious man from earlier.
Except now he’s not just some guy—he’s Kaan. A king. And he recognizes her immediately… which is weird because she definitely does not recognize him.
He helps get her sentenced to death (rude), but then secretly sends a healer to fix her beforehand (sir… explain yourself).
Execution day comes, and Raeve is basically thrown into an arena covered in blood to attract dragons. The Queen starts singing to control the situation, everything is chaotic… and then a rare dragon shows up, scoops Raeve up, and just leaves with her.
So instead of dying, she gets dragon-napped and delivered straight to Kaan.
Which is when things get… complicated.
Check out 5 Books to Read After Fourth Wing for more high-stakes fantasy, dragon-filled worlds, and addictive romance vibes.
Now Raeve is in The Burn, and suddenly everything feels different. Kaan isn’t cruel. He’s intense, secretive, and clearly hiding something—but he’s not like the people she’s used to.
He takes care of her. Gives her space. Lets her bathe (honestly the bare minimum, but still appreciated). And slowly, very slowly, starts breaking down her walls.
Raeve, meanwhile, is like:
“I should kill him.”
“I should leave.”
“Why do I feel things???”
There’s tension, almost-moments, and one very chaotic scene where she literally straddles him with a weapon… and then gets distracted by feelings she absolutely does not want to unpack.
Meanwhile, we’re getting these journal entries from Princess Elluin, and at first it feels like a completely separate storyline.
Until it’s not.
Elluin’s life is tragic in a very royal, “everything is political and also deeply personal” kind of way:
- her brother gets injured
- her family is falling apart
- she’s being pushed toward an arranged marriage with the worst possible option (Tyroth—immediate no)
- and she’s just trying to survive it all
Then everything goes sideways—her family is murdered, she’s forced to take on the Aether Stone (which is basically soul-draining torture jewelry), and her entire life becomes about duty.
Back to Raeve—she tries to escape (because obviously), fails spectacularly (because cliffs are not her friend), and ends up dragged into a whole prophecy situation where people think she’s some chosen figure meant to save the world.
She is… not thrilled about this.
They literally try to marry her off via a fight-to-the-death situation (as one does), and Raeve is like “absolutely not” and demands to fight for herself.
Things go sideways, she gets poisoned, and right when it looks bad—Kaan shows up on a dragon like an absolute cinematic moment and shuts everything down.
He claims her in a way that gives her freedom instead of ownership (which… points for that), and from there, something shifts.
She starts seeing him differently.
Not as a threat—but as someone who might actually be on her side.
Then comes the reveal.
Raeve is Elluin.
Same person. Lost memories. Entire past buried.
And suddenly:
- Kaan recognizing her makes sense
- the connection makes sense
- the tension makes a lot of sense
Because they didn’t just meet.
They were in love.
Check out the Ultimate Guide to Spicy Fantasy Romance to dive deeper into the genre, spice levels, and what to expect.
And not just casual love—deep, secret, forbidden, life-altering love.
They built something real together. Fell hard. And then Elluin got pregnant… right as she was being forced to marry Kaan’s brother.
So she left.
Not because she didn’t love him—but because she was trying to protect him, their child, and everyone else.
Which means Kaan has been living with heartbreak and zero answers this entire time.
Back in the present, Raeve doesn’t remember any of it—but her body does. Her emotions do.
So when she’s around Kaan, it’s constant conflict:
“I don’t trust you.”
“I feel safe with you.”
“I want to leave.”
“I don’t want to leave.”
It’s messy, complicated, and honestly painful in the best way.
Then we get the “let’s pretend we’re still in love for one night” situation—which is already a bad emotional decision.
And surprise… it’s not pretend.
At all.
Meanwhile, chaos continues:
- Raeve is slowly remembering pieces of her past
- Kaan is still very much in love with her
- Rekk is back and still terrible
- Raeve finally gets her revenge (and it is earned)
And then the final bomb drops:
There’s a child.
Kaan’s child.
Alive.
And he has no idea.
By the end, everything is unraveling:
- Raeve is caught between who she was and who she’s become
- Kaan is holding onto a love that never really left
- the truth is coming out in pieces
- and the whole moon-falling-apocalypse situation is still looming
By the time I turned the final page, I just knew—this wasn’t just a good read, it was my favorite book of 2024. The mix of emotional depth, unforgettable characters, jaw-dropping twists, and that slow-burn, soul-crushing romance completely pulled me in and didn’t let go. It’s the kind of story that lingers long after you finish, living rent-free in your head while you sit there wondering how anything else is supposed to compare. Honestly, this one set the bar—and it set it high.
