Fantasy readers argue more than almost any other book community, and most of the arguments happen in the same three or four places: whether a prologue was necessary, whether a magic system needed a rulebook, whether the newest doorstopper needed an editor, whether “romantasy” counts as “real” fantasy. These are not small disagreements. They’re proxy wars for a bigger question that fantasy readers rarely state directly — what is this genre actually for, and what is it allowed to do that other genres aren’t.
The following seven takes are not contrarianism for its own sake. Each one pushes back on a consensus position that has calcified into “everyone knows this,” when a closer look suggests the consensus is doing less work than it claims. None of them require you to agree. They require you to have read enough fantasy to have an opinion worth defending.
The Prologue Isn’t the Problem — the Skippable Prologue Is
“Skip the prologue” has become reflexive advice in fantasy reading circles, repeated so often it now functions as received wisdom rather than a judgment call. The reasoning is usually that prologues are info-dumps in period costume, throat-clearing before the actual story starts, and that a reader loses nothing by starting at Chapter One.
Sometimes that’s true. It’s also true that a huge number of fantasy prologues are doing something a first chapter structurally cannot: showing the reader a piece of the story’s past that no living POV character has access to. The White Walkers in the frozen north before Ned Stark ever appears. A god’s fall before the mortals who worship (or forgot) that god enter the frame. A magic system’s origin, cast in myth, before a character explains its rules more prosaically two hundred pages later. This is not the same information delivered later, just earlier — it’s information the main narrative frequently can’t deliver at all without an awkward flashback or an exposition dump disguised as dialogue.
The actual test for a prologue isn’t length or tone. It’s whether the payoff requires the reader to have seen it. If a book’s final twist, its magic system’s real cost, or its villain’s motivation lands with less force because you skipped the prologue, the prologue was load-bearing and the “skip it” advice cost you the ending you were supposed to get. If nothing in the last hundred pages calls back to it, it was decoration and the advice was right that time. The blanket rule is the mistake, not the prologue.
Brandon Sanderson’s Hard Magic Rules Aren’t the Gold Standard — They’re One Valid Approach Among Several
Sanderson’s Laws of Magic have become the default framework fantasy readers use to judge every magic system in the genre: can the reader predict what the magic will do, are the rules and costs explicit, could a clever character theoretically solve a plot problem using magic-as-puzzle-piece the way you’d solve a chess problem. Systems that meet this bar get called “well-designed.” Systems that don’t — where magic stays mysterious, costly in ways nobody fully explains, and unpredictable even to the characters using it — get called “underdeveloped,” as though the author simply hadn’t finished the homework.
This ranking gets the two approaches backward. A hard magic system is built for a story where magic functions as the plot’s actual mechanism — the reader needs the rules explicit because the climax depends on the reader (and often the character) combining known constraints in an unexpected way, the genre equivalent of a fair-play mystery. This is what Sanderson himself is doing, and it’s genuinely difficult to execute well. But Ursula K. Le Guin’s true-name magic in Earthsea, the deliberately vague and costly power in The Name of the Wind, or the way magic operates as barely-understood force of nature in The Poppy War aren’t failed attempts at Sanderson’s model. They’re doing something a rules-forward system structurally can’t: preserving the sense that power is dangerous precisely because it isn’t fully knowable, which is often closer to what magic means thematically — an intrusion of something larger than human systems of control, not a system you can master with enough study.
Neither approach is more rigorous. Hard magic serves stories about ingenuity and constraint. Soft magic serves stories about wonder, cost, and the limits of human control. Judging a soft-magic novel by hard-magic standards is judging a horror novel for not resolving its mystery — it’s applying the wrong genre’s success criteria and calling the result a flaw.
The Chosen One Trope Isn’t Lazy — Badly Executed Destiny Is
“Chosen One fatigue” gets cited constantly as a reason fantasy needs to move past prophecy plots entirely, and there’s a real phenomenon behind the complaint: a lot of fantasy has used prophecy as a shortcut, letting a character’s destiny do the work that character development should be doing. If the protagonist wins because a prophecy said they would, the story hasn’t earned its ending. That’s a legitimate critique of specific books, not a sound argument against the trope itself.
Go back to where the structure comes from — myth, and the hero’s journey scholarship built on it — and the Chosen One was never supposed to mean “protagonist wins by birthright.” It meant a character marked by fate encounters a series of trials that test whether they’ll become the person the prophecy assumed they already were. The prophecy is the setup; the character’s actual choices under pressure are the payoff. Frodo is arguably a Chosen One — he’s the ring-bearer by circumstance, not merit — and the entire trilogy’s tension comes from whether he can survive being asked to do something no amount of destiny actually prepares a person for. The prophecy names him. It doesn’t save him.
The trope fails when a story treats “chosen” as the answer instead of the question. It succeeds — in The Poppy War’s subversion of the trope, in Harry Potter’s insistence that Neville Longbottom could have been the “chosen one” just as easily, in the original Star Wars trilogy — when destiny sets the stakes and the character’s decisions under those stakes are what actually resolves the story. “Chosen One fatigue” is really fatigue with authors who forgot the second half of the structure. The trope survived three thousand years of storytelling because the good version of it works.
Doorstopper Fantasy Doesn’t Need a Ruthless Editor — It Needs the Right Reader Expectation
Every fantasy series that crosses 800 pages per volume eventually gets the same complaint: it needed a harder edit, a shorter book, fewer subplots, a more disciplined author. This complaint treats length itself as evidence of bloat, as though a tighter 400-page version of the same story necessarily exists inside the longer one, waiting to be cut free.
Sometimes that’s accurate — plenty of doorstoppers really do sag under redundant scenes that repeat information the reader already has. But the complaint often mistakes pacing preference for objective flaw. A 1,000-page fantasy novel that spends 60 pages on a political council debating trade routes isn’t necessarily failing to entertain — it might be doing exactly what immersive epic fantasy promises: total residence in a world dense enough that trade routes matter to the people living in it. Readers who want propulsive plot mechanics are reading the wrong subgenre if they pick up a doorstopper and then object that it behaves like one. That’s not a defense of every 1,200-page book on the shelf; some genuinely are undisciplined. It’s an argument for separating “this didn’t work for my taste” from “this is objectively bloated,” which are different claims wearing the same complaint.
The actual tell isn’t page count. It’s whether the density serves an experience the reader came for. A Storm of Swords holds its length because the political texture is the point. A 900-page book that could tell its actual story in 500 pages and simply hasn’t figured out what its actual story is — that’s the real failure mode, and it has nothing to do with word count on its own.
Romantasy Isn’t “Fantasy for People Who Don’t Read Real Fantasy” — It’s a Structural Hybrid, Not a Lesser Version
The most tired argument in current fantasy discourse is the claim that romantasy — Fourth Wing, ACOTAR, Throne of Glass, the entire wave of dragon-riders-and-fae-courts fiction currently dominating bestseller lists — represents a diluted, romance-first version of “real” fantasy, worldbuilding and stakes softened to make room for the love triangle. This gets the genre mechanics backward.
Romantasy isn’t fantasy with romance bolted on. It’s a structural hybrid that has to satisfy two different genre contracts simultaneously — the fantasy plot needs stakes, magic, and worldbuilding that function on their own terms, while the romance plot needs emotional escalation, tension, and payoff that function on romance’s terms, and the two need to reinforce rather than compete with each other. That’s a harder needle to thread than writing either genre in isolation, not an easier one. Sarah J. Maas’s Night Court politics in the A Court of Thorns and Roses series carry real narrative weight independent of Feyre and Rhysand’s relationship; Rebecca Yarros’s War College in Fourth Wing has functioning military stakes that exist whether or not Violet and Xaden end up together. Readers dismissing romantasy as fantasy-lite are usually judging it by only one of its two genre contracts and ignoring that it’s succeeding at both simultaneously.
This isn’t an argument that every romantasy title clears the bar — plenty subordinate the fantasy plot to the romance to a degree that earns the “lite” label fairly. It’s an argument that the genre’s best entries are doing something more technically demanding than pure epic fantasy, not something easier, and the dismissal usually comes from readers who haven’t actually tested that claim against the books doing it well.
An Unfinished Series Doesn’t Retroactively Ruin the Books That Are Already Great
George R.R. Martin hasn’t published The Winds of Winter. Patrick Rothfuss hasn’t published The Doors of Stone. Both situations generate a specific, recurring argument: readers shouldn’t start these series, because investing in an unfinished story that may never conclude is a bad use of reading time, and the books themselves are somehow diminished by an ending that doesn’t exist yet.
This treats a book’s value as contingent on a sequel it doesn’t control. A Game of Thrones is a complete, structurally whole novel — it has its own arc, its own losses, its own devastating final movement with Ned Stark’s execution. The Name of the Wind is a self-contained frame narrative that resolves its own day’s events even as it opens a larger unresolved question. Neither book is incomplete on its own terms. What’s incomplete is a separate, larger story that hasn’t finished being told — a real disappointment, but a different kind of disappointment than “the book you already read failed to deliver what it promised.”
The stronger version of this advice isn’t “don’t read unfinished series.” It’s “know what you’re signing up for before you start” — go in expecting a wait, possibly a permanent one, rather than assuming completion is owed to you on a schedule. Refusing to read A Song of Ice and Fire until Martin finishes it means refusing, indefinitely, five of the best fantasy novels published in the last thirty years over a frustration with the sixth one that doesn’t exist yet. That’s a trade a lot of readers are making without fully pricing in what they’re giving up.
Multi-POV Epics Aren’t Diluting Their Protagonists — Single-POV Fantasy Is Often Hiding a Weaker World
A recurring complaint about sprawling multi-POV fantasy — A Song of Ice and Fire, The Wheel of Time, The Stormlight Archive — is that spreading attention across a dozen viewpoint characters dilutes investment in any single one of them, and that a tighter single-POV structure would generate more emotional intensity per character.
That’s true in the narrow sense that any individual character in an ensemble gets less page time than the sole protagonist of a single-POV novel. It misses what multi-POV structure is actually built to do, which single-POV fantasy structurally cannot: let the reader watch the same event from opposing sides and understand why each side believes it’s righteous. Multi-POV fantasy can show a war from the perspective of soldiers on both sides who each have legitimate grievances, can reveal that the “villain” of one chapter is the sympathetic protagonist of the next, and can build a sense of a world too large and too morally contested for any single perspective to contain it honestly. Single-POV fantasy, however emotionally intense its central character, is committed to that character’s blind spots for the entire book — you only know what the world looks like as this one person understands it, whether or not their understanding is complete or even accurate.
The actual weakness in multi-POV fantasy isn’t the structure — it’s when an author adds viewpoint characters as worldbuilding delivery devices rather than because their perspective genuinely complicates the reader’s understanding of the story. That’s a craft failure specific to certain books, not evidence that multi-POV is inherently diffuse compared to single-POV. Done well, it’s the format most capable of making a fictional world feel morally and politically real, because reality doesn’t have a single protagonist either.
What to Do With a Genre That Argues About Itself This Much
None of the above is an argument that fantasy readers should stop having these fights. The opposite: a genre this argued-over is a genre people take seriously enough to disagree about, and that’s a healthier sign than universal agreement would be. What’s worth examining is how quickly specific, defensible critiques — some prologues are unnecessary, some magic systems are underdeveloped, some doorstoppers really do sag, some Chosen One arcs really are lazy — calcify into blanket rules applied to every book regardless of what that particular book is actually doing.
The better habit isn’t picking a side in “prologues good or bad,” “hard magic versus soft magic,” “romantasy real fantasy or not.” It’s asking what a specific book is trying to do on its own terms, and judging whether it succeeded at that rather than at some other book’s version of success. That’s a more demanding way to read fantasy than repeating the consensus take. It’s also the only way to actually notice when a book is doing something worth defending.
Keep track of which fantasy hills you’re willing to die on — log the ratings, the rereads, and the arguments you’re winning in Bookdot.
Related Articles
Frequently Asked Questions
- Is it bad if a fantasy book has a long prologue?
- Not inherently. A prologue earns its length when it plants information the reader needs before the main POV can supply it — a prior era, a different character's death, a magic system's cost. It becomes a problem only when it's doing worldbuilding the first three chapters could handle just as well, delaying the reader's actual entry point into the story for no structural reason.
- Do fantasy magic systems need strict rules like Brandon Sanderson's?
- No. Hard magic systems with explicit rules serve stories where the magic itself is the puzzle to solve — the reader is meant to predict outcomes. Soft magic systems, where power stays mysterious and costly, serve stories where wonder and consequence matter more than mechanics. Neither approach is more sophisticated than the other; they're built for different kinds of stories.
- Is the Chosen One trope actually bad writing?
- The trope itself isn't the problem — its execution is. A Chosen One story fails when destiny substitutes for character growth, so the protagonist wins by birthright rather than by earning it. It succeeds when the prophecy is the setup and the character's actual choices are the payoff, which is closer to how the trope originally worked in myth than how it's often parodied now.