The Game — Inheritance, Multiple Inheritance, and the Wrong Parent Class

"Every gamer is already an object-oriented thinker. They just don't know the name for what they're doing."

What Happens When You See a New Enemy

You're exploring a swamp. A creature lunges at you. You've never seen it before.

But you don't panic. In the first half-second, your brain does this:

1. "Bipedal, humanoid shape — probably melee, watch for swings"
2. "It's in a swamp — could have poison, movement might be different"
3. "Glowing patches on its skin — status effect, definitely poison or rot"
4. "Slower than the open-field version I fought earlier — swamp is reducing its speed too"

You didn't read a bestiary. You didn't look up a wiki. You inherited from every similar enemy you've fought before, noted the polymorphism (swamp variant, poison trait), and encapsulated whatever you don't know yet ("I'll figure out its attack pattern by dodging the first few swings").

That's OO. You've been doing it every time you pick up a controller. You just never had a name for it.

The Mob Hierarchy

Every game with enemies has an inheritance tree. Most players feel it instinctively. Let's make it visible.

The Base Class: Ground Mob

The most basic enemy in any game. Walks on land. Has HP. Has one or two attacks. Dies when HP reaches zero. This is the ancestor of almost everything you'll fight.

Properties inherited by default: HP pool, Movement speed, Basic attack(s), Aggro range, Drop table (loot).

Variants: Override One Thing at a Time

Notice the pattern: each variant overrides one or two things and inherits everything else from the parent. That's why you can read a new enemy in half a second — 80% is inherited from something you've already fought.

The Boss: Composition + Overrides

A level boss is not just "a stronger mob." Its design can compose movement, armor, magic, arena, and phase systems while overriding selected behaviors.

A typical boss might reuse ground movement, armored damage rules, and magic attacks, then add unique phase transitions and arena interactions. A particular engine may implement that with inheritance, components, traits, data, or a mixture.

That is composition at the design level. The familiar pieces help you predict behavior, while unique mechanics break the prediction. Do not infer a multiple-inheritance implementation or a reuse percentage from the player's experience.

The Weapon System

Weapons are the clearest polymorphism demo in gaming.

The Interface: attack()

Every weapon has an attack() method. Press the button, something happens. Same input, different output.

One button. Six completely different behaviors. That's polymorphism. The interface is identical (press R1), but the implementation depends on which class is equipped.

The Map: Environment as Inherited Modifier

Maps aren't just backdrops. They're classes too.

Scarlet Rot in Caelid is a strong example of design composition. It combines movement pressure, status buildup, environmental storytelling, and adapted enemies into an experience that feels unlike a regular poison swamp. Those ingredients do not prove a formal inheritance tree or an exact reuse percentage.

The Build: Your Character as Composition

When you build a character, you are composing capabilities.

Paladin build: Inherits from Warrior (melee combat, heavy armor, HP pool) + Faith caster (healing, buffs, holy damage) + Tank (shield mechanics, aggro management).

Spellblade build: Inherits from Swordsman (melee moveset) + Mage (spell scaling, mana pool). Overrides weapon damage to scale with Intelligence instead of Strength.

Glass Cannon: Inherits from Mage (spell power, range). Overrides defense to near-zero (encapsulates durability entirely). Maximizes a single axis: damage output.

Every build is a composition of stats, equipment, skills, and constraints. That can resemble traits from several archetypes, but allocating stat points is not itself multiple inheritance.

Malenia: When 知彼 Fails

This is Dad's story. And it's the most important lesson in this track.

Dad entered Malenia's boss fight at level 120+. Overleveled. Good build. Spirit summon ready. By every normal metric, this should have been manageable.

His mental model (parent class):

"She's a hard boss. But with enough level, stats, and a spirit summon, I can tank through her damage and out-DPS her. That's how boss fights work."

That model — "tough boss, but fundamentally the same combat economy" — had worked for every other boss in the game. It was a parent class with a 100% success rate.

What Malenia actually is:

Malenia has lifesteal. When she hits you, she heals. Not a little. A lot.

This isn't "a stronger boss." This is a boss that overrides the fundamental combat economy. In every other fight, trading hits is viable — you take damage, the boss takes damage, net HP goes down. With Malenia, trading hits can result in net zero or even net negative for you. You get weaker. She gets stronger. The longer the fight goes, the harder it gets.

The parent class was wrong.

Dad's preparation was perfect for the class he thought he was fighting. High HP, strong weapon, spirit summon to share aggro. But all of that is designed for a "normal hard boss" — a class that Malenia isn't in.

Malenia is a unique encounter, not a formal Singleton pattern. Her heal-on-hit mechanic changes the combat economy: avoiding hits matters more, and a spirit summon can become a source of healing for her.

知己 was fine — Dad knew his own build, his stats, his capabilities. 知彼 failed — he read the wrong parent class. And no amount of 知己 compensates for wrong 知彼.

Tool Unlock

Mold Hunt

Game designers use many reusable patterns because consistent rules and variation matter. OO is one implementation toolkit among several; a player's mental model does not reveal the engine's class hierarchy.

As a player, you navigate patterns instinctively. A new enemy invites inheritance-like comparison; a weapon interface invites polymorphism-like reasoning; a build invites composition. These are useful lenses, not claims about the source code.

You've been an object-oriented thinker for as long as you've been a gamer. The mold was always there. Now you can see it.

Pippa's Confession