Joe Abercrombie was cutting film trailers for a living when he started writing The Blade Itself. He was a freelance editor, working in a London flat, spending his evenings reading the same epic fantasy he'd loved since childhood. And something had started to bother him. The heroes were too clean. The villains too legible. Every quest ended with the right person holding the right sword for the right reasons, and Abercrombie, who spent his days assembling stories out of raw footage, knew that wasn't how stories actually worked.
So he wrote Logen Ninefingers, a barbarian who keeps promising he's changed and keeps proving he hasn't. He wrote Glokta, an inquisitor who tortures people for information and also happens to be the funniest, most self-aware character in the book. He wrote Bayaz, a wizard who looks like Gandalf and operates like a hedge fund manager. None of them deserved to win. All of them thought they did.
Abercrombie didn't set out to write "dark fantasy" as a category. He set out to write fantasy where the moral weight of the violence actually landed, where a sword through someone's chest ruined the person holding the sword too. The darkness wasn't the point. The cost of the darkness was the point.
That distinction is the thing most dark fantasy writing gets wrong early on. Bleak settings, grim characters, graphic violence. All of it can sit on the page and do nothing. Darkness in fiction only works when it puts pressure on the characters' ability to remain who they thought they were. When it forces a choice that can't be taken back. When it reveals something the reader wasn't ready to see about what people do under pressure.
Violence has to cost something the reader can feel
There's a fight in The Blade Itself where Logen kills someone in a way that's fast and ugly and then he sits there afterward, breathing hard, staring at what he's done. The scene doesn't linger on the gore. It lingers on Logen's face. On the gap between who he says he is and what his hands just did.
That's the difference between violence that serves the story and violence that's just there because the genre allows it. When you write a fight scene in dark fantasy, the question worth asking afterward isn't "was that brutal enough." It's "what does this character know about themselves now that they didn't know before the fight started." If the answer is nothing, the scene is decoration.
I'm not sure why so many early dark fantasy drafts default to escalating the body count when things feel flat. Maybe because it's the most visible lever to pull. More death, more darkness, more stakes. But readers don't actually feel stakes through volume. They feel stakes through specificity. One character losing something they can't get back will always land harder than a hundred nameless casualties.
An antihero needs a code, even a broken one
Evan Winter's The Rage of Dragons gives you Tau Tafari, a young man whose entire personality becomes revenge after his father is killed. The book is relentless. Tau trains until he's vomiting. He fights anyone who'll stand across from him. He doesn't grow kinder or wiser as the story progresses. He gets sharper and more dangerous.
But he isn't random. Tau has a code, even if it's a code most people would call self-destructive. He won't stop until the specific people responsible for his father's death are dead. That specificity is what makes him readable instead of exhausting. He isn't cruel for its own sake, he isn't chaos, he's a person operating from a grief so total that it's become the only logic he has left, and the reader can follow that logic even while disagreeing with every choice it produces because they can see where it comes from and they can feel how it narrows his life down to a single burning point.
When your antihero is just "dark" without a governing principle, readers lose the thread. They don't know what to root for. They don't know what a win looks like for this person, which means they don't know what a loss looks like either. An antihero's code doesn't have to be good. It has to be legible.