The kind master problem
Isekai keeps handing its protagonist slaves and then asking to be judged on how nicely he treats them. Here is what that framing actually does, and why it is the one thing that makes me put these books down.
The pattern
It runs the same way almost every time.
An ordinary person from our world arrives somewhere pre-industrial. Fairly early, they encounter slavery. It is not presented as a horror to be overthrown; it is presented as a feature of the setting, like currency or weather. Then the protagonist acquires one or more slaves, usually children, usually non-human, usually mistreated by whoever had them before.
And then the book does the move it has been building toward the whole time: it invites you to feel good about how well he treats them.
I want to be precise about what I am objecting to, because “this fantasy world has slavery in it” is not the complaint. Plenty of good books have slavery in them. The complaint is about a specific narrative shape.
What the shape accomplishes
Three things, and they are the reason it keeps getting used.
1. It manufactures loyalty without earning it
Building a companion who trusts the protagonist takes chapters of shared risk. Buying one takes a paragraph. The dynamic arrives pre-installed: total dependence, gratitude, and an inability to leave. All the emotional payoff of found family, none of the work.
2. It makes ordinary decency look like heroism
This is the load-bearing one. Set the bar at “previous owner starved them,” and a protagonist who provides food clears it. He does not have to be brave or clever or right about anything. He has to be not cruel, and the book will treat that as a moral achievement.
It is a very cheap way to establish that your hero is good, and it works on readers, which is why it persists.
3. It puts a permanent power gap under the relationships
Which the books almost never examine, and which does a lot of quiet work when those characters are also drawn as romantic prospects, or as children, or both.
The version I read this week
Death March to the Parallel World Rhapsody, Vol. 1 is a useful example precisely because it is not a careless book. It notices. It just does not act.
It knows where the slaves came from. At 45 percent Zena mentions the war with the beastfolk ended ten years ago, and Satou immediately thinks: “I wonder if the beastfolk slaves in the city were prisoners of war from that period?” Neither character ever raises it again.
It writes the single best scene against itself. At 60 percent he offers three enslaved children honey pastries and none of them move:
That is a good scene. It is specific, it is quiet, and the narration draws the correct conclusion in the moment.
And then the paperwork. At 96 percent a civil official explains the legal position without a flicker of discomfort:
He is handed a temporary ownership certificate and directed to the town hall or a slavery firm for the permanent contract. There is an industry. It has firms, and a counter, and a queue.
His private response is the exact sentence the trope always supplies: I mean, I was planning to buy them and set them free, anyway, but still…
The volume ends there. Nothing I read shows him freeing them. What it closes on is a kind man holding a deed to three children, and the book treating that as a settled and pleasant state of affairs.
Why “he’s going to free them” is not an answer
It is the standard defense and it fails for a simple reason: the intention is doing the work that the action is supposed to do.
A book that wanted to deal with this would have to spend pages on it. Manumission is a legal process. Somebody has to go to the firm. There is a fee. There is a question of what three formerly enslaved children with no family do next, in a city that fought a war against their people ten years ago and lost interest in them afterward.
All of that is interesting. It is the story. And leaving it as a private thought means the book gets the credit for the good intention while keeping every structural benefit of the arrangement: the loyalty, the dependence, the permanent household.
Four questions worth asking
When a book hands its protagonist a slave, these separate the ones doing something from the ones doing the move.
1. Does the institution still exist at the end? Not “did our hero behave well.” Is the thing intact. If yes, the slavery was scenery.
2. Do the enslaved characters want anything the protagonist has not already provided? A character whose entire arc is gratitude is not a character.
3. Does anybody in the book find it objectionable? Not the protagonist thinking it privately for one line. Somebody saying it out loud, to another person, with consequences.
4. What is the emotional climax of that storyline? If it is freedom, the book is about something. If it is the slaves being happy in their new home, the book has used the institution to manufacture a family and is hoping you will not notice.
Death March, volume one: intact, no, no, and the new home. Four for four.
What I am not saying
I am not saying skip it. I reviewed it warmly, because the rest of it is genuinely charming and unusually smart about money and plumbing, and because the pastry scene is better writing than the trope deserves.
I am also not saying fantasy should not contain slavery. It should, when it means to. The books that handle it well tend to do one obvious thing: they let it be a problem with a cost, rather than a way of acquiring companions who cannot say no.
What I am saying is that a book cannot write the scene where three children will not eat without permission, correctly identify what it means in the narration, and then end on the protagonist filing ownership papers, and expect that to read as warm. It read as warm to a lot of people. That is what bothers me.
Written for CVM Sekai. RaeRae Rants. · Death March, Vol. 1 · The review · Novel 101: Isekai