The Villain Is Down. Why Is Everyone Suddenly an Idiot?
When writers sacrifice established character intelligence to manufacture drama, the real casualty isn't the villain. It's the audience's trust.
There is a particular kind of stupidity in fiction that drives me absolutely up the wall.
Not the stupidity of a character who is supposed to be stupid. Not the understandable mistakes of inexperienced heroes. Not even the occasional lapse in judgment by an otherwise intelligent person.
I'm talking about plot-induced stupidity: that magical moment when a character who has demonstrated intelligence, competence, and experience suddenly forgets everything they know because the screenplay needs something terrible to happen.
And I recently encountered a spectacular example while watching As a Reincarnated Aristocrat, I'll Use My Appraisal Skill to Rise in the World.
When a Punch Becomes a Plot Device
In Season 3, Episode 8, we find ourselves in the middle of a confrontation involving Ars Louvent, his exceptionally capable warrior Ritsu, and an antagonist named Vigo.
Ritsu has been captured and tortured. He escapes alongside Ars, and despite his physical condition, manages to knock Vigo down with a single punch.
So far, so good.
Ritsu is an extraordinary fighter. We've already seen what he's capable of. The scene reinforces his prowess, determination, and loyalty to Ars.
Except there's one tiny problem.
Vigo isn't unconscious.
He's down, certainly. But he's very much alive, capable of movement, and apparently only momentarily inconvenienced by having been punched in the face.
And what do our heroes do?
Nothing.
They leave him there.
Nobody restrains him. Nobody searches him. Nobody makes sure he can't reach for a weapon or trigger some other nasty surprise.
And, wouldn't you know it, Vigo recovers just enough to activate explosives that bring the castle crashing down.
Congratulations, gentlemen. You have successfully defeated your enemy while allowing him to accomplish precisely what you should have prevented.
These Are Not Rookie Adventurers
Here's what makes the scene so infuriating.
Ars and Ritsu aren't inexperienced children wandering into their first dangerous encounter.
These people are veterans of a civil war.
They've participated in military campaigns, confronted dangerous enemies, and survived situations in which tactical mistakes could mean death.
Ritsu, in particular, is an experienced warrior whose primary responsibility is protecting Ars.
He's not supposed to be merely good at hitting people. He's supposed to understand combat.
And any experienced combatant should know there's a rather significant difference between knocking an enemy down and ensuring that enemy can no longer threaten you.
Now, I'm not arguing that Ritsu necessarily needed to kill Vigo.
There's a perfectly reasonable argument for taking prisoners. There's also a perfectly reasonable argument for prioritizing escape when you're injured and responsible for protecting someone else.
But there is absolutely no reasonable argument for leaving a dangerous, conscious enemy unsecured when that enemy has already demonstrated his willingness to torture prisoners and use extreme violence.
Especially when you're still inside his castle.
If Ritsu had knocked Vigo unconscious, I'd have accepted the scene without complaint. The protagonists could reasonably believe the immediate threat had been neutralized.
But Vigo recovers almost immediately.
The narrative itself demonstrates that he was never effectively incapacitated.
And we're supposed to believe that an experienced warrior couldn't recognize that?
Give me a break.
The Entire Enemy Army Apparently Paused for Lunch
And the incompetence doesn't stop with the protagonists.
There's another particularly irritating detail: the other enemy soldiers appear to become little more than background decorations.
Nobody takes initiative. Nobody intervenes meaningfully. Nobody does anything that might alter the carefully scripted sequence.
The whole scene feels like a turn-based RPG in which everyone has exhausted their action points except the defeated boss, who still has one scripted attack remaining.
Vigo used Self-Destruct!
It's super effective!
And the writers apparently expect us to applaud the dramatic consequences.
The Infuriating Part? The Castle Needed to Collapse.
Here's where my criticism becomes more nuanced.
I actually liked what the writers were trying to accomplish with the castle's destruction.
The collapsing castle is essential to the character development of the people from Yoh.
Their prospective king is struggling with the symbolic importance of an ancestral sword. He believes that possessing this weapon is fundamental to his legitimacy.
The crisis forces him to confront a much deeper question.
What makes someone a king?
Is it an inherited artifact? A symbol of authority? A connection to an illustrious bloodline?
Or is it the ability to lead, inspire loyalty, and protect the people who depend on you?
The loss of the sword, the choices made during the disaster, and its eventual recovery provide an opportunity for genuine character growth.
The prospective king comes to understand that a sword does not make a king. A king gives meaning to the sword.
That's excellent thematic material.
It also beautifully complements the central premise of the anime.
Ars himself isn't an overpowering warrior. His extraordinary gift is identifying the capabilities of other people and bringing those talents together.
His leadership isn't defined by personal strength or some magical artifact. It's defined by his judgment, his relationships, and his ability to inspire others.
The Yoh storyline reinforces precisely that philosophy.
So why am I complaining?
Because none of this required Ritsu to become an idiot.
Have Vigo activate a timed explosive before the confrontation.
Have the castle's structural supports already compromised.
Have one of Vigo's loyal subordinates trigger the explosions after realizing their leader has been defeated.
Any of those alternatives would have preserved the catastrophe, the character development, and the underlying message.
And none would have required an experienced warrior to forget the first principles of securing a defeated enemy.
The writers had a perfectly good destination.
They simply chose an astonishingly stupid route to get there.
The Myth of the Honorable Duel
There is a possible cultural explanation for some of this.
Japanese martial-arts fiction frequently romanticizes the honorable duel: two opponents confront each other, one demonstrates superiority, and the defeated combatant is permitted to live.
The victorious warrior shows restraint. The defeated opponent acknowledges the outcome. Honor is preserved.
Fair enough.
But that convention shouldn't be confused with how actual warfare works.
Historical samurai were perfectly capable of ambushes, deception, surprise attacks, and ruthless tactical decisions. The romanticized warrior code familiar from popular fiction is not a comprehensive description of Japanese military history.
More importantly, Ritsu wasn't fighting a ceremonial duel.
He was escaping captivity with the nobleman he had sworn to protect.
This wasn't a sporting event, and there wasn't a referee standing nearby to declare the match finished.
There is a difference between showing mercy and abandoning basic tactical judgment.
Mercy doesn't require leaving an opponent free to resume attacking.
And honor doesn't require giving your enemy another opportunity to kill you.
Ender Wiggin Understood This Better Than Most Adults
Which brings me to a very different science-fiction story: Orson Scott Card's Ender's Game.
Early in the novel, Ender Wiggin is attacked by a bully named Stilson.
Ender fights back, knocks Stilson down, and then continues attacking him.
When questioned afterward, Ender explains that defeating Stilson in that particular confrontation wasn't enough.
He wanted to prevent future confrontations.
Later, in the infamous shower-room confrontation with Bonzo Madrid, Ender applies similarly decisive reasoning against a larger, stronger adversary who poses an immediate threat.
The consequences are devastating. Ender's actions ultimately prove fatal to both opponents, something he doesn't initially realize.
And that's important.
Ender's Game doesn't simply celebrate extreme violence. It examines the psychological and moral consequences of a child conditioned to approach conflict through overwhelming, decisive force.
Nevertheless, Ender's tactical reasoning is unmistakable.
Winning the immediate confrontation is not necessarily the same as eliminating the danger that caused it.
That distinction is the entire point.
Ritsu didn't need to behave like Ender. He didn't need to deliver another potentially fatal blow.
He simply needed to ensure that Vigo couldn't resume attacking.
Take him prisoner. Restrain him. Disarm him. Secure the room.
Anything.
Instead, an experienced military veteran apparently concluded that knocking a dangerous enemy onto the floor was sufficient to guarantee everyone's safety.
And the audience was expected to accept that.
The Problem Isn't That Characters Make Mistakes
Characters absolutely should make mistakes.
A story in which everyone always makes the correct decision would be both boring and implausible.
Intelligent people misjudge situations. Experienced soldiers make tactical errors. Fear, exhaustion, injury, desperation, and emotional attachment can all interfere with sound judgment.
Indeed, Ritsu's condition after being tortured could have provided an entirely convincing explanation for a serious mistake.
But the story would have needed to establish that connection.
Show him barely conscious. Show him struggling to remain standing. Show him trying to secure Vigo but physically unable to do so. Show Ars urgently ordering him to abandon the enemy because the building is already coming apart.
Give us a reason.
A character making a mistake because of believable circumstances is storytelling. A character making a mistake because the plot requires it is manipulation.
And audiences can tell the difference.
The Real Victim Is Character Consistency
The central problem with plot-induced stupidity isn't simply that it produces implausible events.
It's that it undermines the work the writers have already done.
For three seasons, Appraisal Skill has invested considerable effort in establishing Ars's companions as exceptionally talented individuals.
Their abilities are the foundation of the entire premise.
Ritsu isn't just another swordsman. He's one of the outstanding talents Ars has discovered and cultivated.
When the story suddenly requires him to behave like someone with no combat experience whatsoever, it diminishes that characterization.
It tells us that his competence is conditional.
He's brilliant when the story needs an impressive victory, but conveniently incompetent when the writers need a disaster.
And once a story establishes that its characters' intelligence can be switched on and off according to the needs of the plot, the stakes begin to feel artificial.
Why worry about whether a character can overcome an obstacle through skill and judgment when the writers might simply disable those qualities at the critical moment?
Why celebrate cleverness when stupidity is always available as a convenient plot mechanism?
That's how a story begins losing the audience's trust.
Stop Making Your Characters Stupid to Make Your Plot Work
I don't demand absolute realism from fiction.
I'm perfectly willing to accept reincarnation, magical abilities, dragons, interstellar civilizations, faster-than-light travel, and any number of wildly implausible premises.
That's what speculative fiction is for.
But accepting an impossible premise doesn't mean abandoning the expectation of internal consistency.
If your story establishes that a character is an experienced warrior, let him behave like one.
If your story establishes that someone is a brilliant strategist, don't make him overlook an obvious danger merely because you've run out of ways to create tension.
And if your story requires a castle to collapse so that a future king can discover the true meaning of leadership, find a way to collapse the damn castle without making everyone inside it suddenly forget how their own world works.
The irony is that the Yoh storyline delivers a worthwhile lesson about leadership.
A king is not made by a sword. He's made by the qualities that allow him to lead.
The episode understands that symbolism beautifully.
What it apparently doesn't understand is that the same principle applies to its own writing.
You cannot establish a character's competence through years of storytelling and then expect that competence to survive being casually discarded whenever the plot becomes inconvenient.
A sword doesn't make a king.
And knocking a villain down doesn't make him harmless.
Someone really should have told Ritsu.

Comments
Post a Comment