CHAPTER 10: First Blood
Alucard couldn't fight.
He could walk, run, jump, fall, move through Marcus's Marble Gallery with Lena's music playing in the background. He could exist in a beautiful world. But he couldn't do the one thing a son of Dracula needed to do in a castle full of monsters: attack.
The first week of May, George sat down to fix that.
The combat system was, alongside exploration, the other half of the game's heart. You could have the most beautiful castle in the world, the most atmospheric music, the most intelligent map, but if fighting felt bad, none of the rest mattered. The player was going to spend most of their time fighting, and every fight had to be satisfying. Not "acceptable". Not "functional". Satisfying. That was the standard.
George started with the sword.
Alucard's basic attack was a horizontal slash: a clean arc covering a range in front of the character. In the original game, the attack was fast, responsive, with a clear visual impact and a sound that made you feel like you had hit something solid. George needed to recreate that feeling with the tools he had: sprites, hitboxes, and timing.
He wrote to Marcus asking for the attack animations. The email was specific to the extreme: six frames for the basic attack, with the sword moving from a retracted position behind the head to a full extension in front of the body. The arc needed to cover approximately 120 degrees. The cape had to react to the movement, swirling behind Alucard. The last two frames had to be the recovery, where Alucard returned to the neutral position.
Marcus delivered the sprites in three days. They were impeccable, as everything he made was: the sword traced an arc you could feel with your eyes, with a motion blur effect made from semi-transparent pixels that gave the impression of speed. The cape swirled exactly as George had asked.
George integrated them into the engine and programmed the attack: when the key was pressed, Alucard executed the six animation frames, and during frames three and four, the point in the arc where the sword was fully extended, an invisible hitbox activated in front of the character. Anything that touched that hitbox would receive damage.
He tested the attack in an empty room. Pressed the key. Alucard swung the sword. The arc was fluid, fast, with the cape moving behind him like a flag in the wind. The hitbox blinked red in debug mode, showing exactly where it was lethal.
It felt good. But it felt incomplete. Something essential was missing: something to fight against.
George had asked Marcus for the first enemy two weeks earlier: a skeleton. The most basic enemy in any gothic-themed game. A pile of bones that walks, throws things, and dies in a few hits. The skeleton was the perfect placeholder for testing the combat system because its behavior was simple: patrol, detect the player, attack.
Marcus delivered the sprite sheet on a Monday afternoon, along with an email that said simply: "hope mr. bones is up to the job."
He was up to the job.
The skeleton was thirty-two by forty-eight pixels: shorter than Alucard, wider, with a hunched posture that communicated animal menace. Marcus had given it a jaw that hung open in every frame, as if the skeleton were perpetually screaming without sound. The eyes were two red dots in the empty sockets. It carried a rusted sword in its right hand and a broken shield in its left. It had six walking frames, four attack frames, and three death frames where the bones crumbled into a satisfying pile.
George programmed the skeleton's artificial intelligence. He used the word "intelligence" generously: the skeleton walked left to right between two points, and if Alucard entered a detection range, the skeleton turned toward him and began walking in his direction. If it was close enough, it attacked. If it took damage, it stepped back. If its health reached zero, it played the death animation and disappeared.
Simple. Predictable. Exactly what a first enemy should be: a manageable threat that taught the player the rules of combat without killing them unfairly.
George loaded the skeleton into the Marble Gallery test room. He placed it halfway through the hall, patrolling between two columns.
Compiled. Ran. Lena's music began to play. Alucard appeared in the left corner of the room. And to the right, between the flickering chandeliers, the skeleton walked back and forth with its red eyes glowing in the marble's dim light.
George walked toward it.
The skeleton detected him. Turned. Began walking toward Alucard with its open jaw and its raised rusted sword. Lena's music kept playing, indifferent to the small drama unfolding between two sprites in a room of tiles.
George pressed the attack key.
Alucard swung the sword. The arc caught the skeleton at the exact frame when the hitbox activated. The skeleton took the hit. George had programmed a pause on impact, a two-frame freeze frame, barely perceptible, that stopped the action for a fraction of a second to give the blow weight. The skeleton stepped back. Its health bar, invisible to the player but visible in debug mode, dropped by a third.
George attacked again. Another arc. Another impact. Another freeze frame. The skeleton stepped back again.
Third hit. The skeleton's health reached zero. The bones crumbled into the satisfying pile Marcus had drawn. The red dots in the eyes went out. The pile of bones flickered three times and disappeared, leaving a small flash where it had been.
The Marble Gallery was empty again. Just Alucard, the chandeliers, and Lena's ghost waltz.
George leaned back in his chair with a smile he couldn't control. He had just killed a skeleton in a vampire castle, and it had been satisfying. The impact freeze frame, the knockback, the disintegration into bones: every element combined to create a micro-moment of satisfaction that the player would feel hundreds of times throughout the game, and that every time had to feel good.
But something was missing.
George frowned, placed the skeleton back in the room, and faced it again. He attacked. Hit it. The skeleton stepped back. And George identified the problem: the skeleton didn't attack back. It was programmed to, but its attack range was too short and its reaction too slow. By the time the skeleton raised its sword, Alucard had already killed it. There was no real danger. No tension. It was like hitting a punching bag with red eyes.
Balance was the invisible art of game design. The difference between a game that felt fair and one that felt boring or unfair lay in numbers the player never saw: the enemy's attack speed, its detection range, how much damage it dealt, how much health it had, how many frames passed between spotting you and attacking.
George spent two days adjusting these numbers.
He gave the skeleton a faster attack: instead of six anticipation frames before the strike, he gave it three. Now, when the skeleton raised its sword, the player had less time to react. He increased the detection range so the skeleton began walking toward Alucard from farther away, giving less time to prepare. He added a second attack pattern: in addition to the sword slash, the skeleton could throw a bone in an arc, a slow but annoying projectile that forced the player to move.
He tested again. This time it was different. The skeleton was a real threat. It could damage Alucard if you weren't careful. But it wasn't unfair: its attacks were telegraphed, with clear animations that told you what was coming, and if you paid attention and reacted, you could dodge or counter-attack every time.
Then he added knockback for Alucard: when an enemy hit him, Alucard stepped back and had a second of invincibility with a visual flicker. This prevented the player from taking several hits in a row and also gave a clear signal that you had been struck. Without knockback, hits felt confusing, imprecise. With knockback, every hit received was an unambiguous statement: you got hit, it hurt, react.
George fought the skeleton about thirty times. He adjusted the damage: too low and the skeleton was irrelevant; too high and it felt unfair for a first zone. He adjusted the experience it gave on death: enough for the player to feel progress, not so much that they leveled up in five enemies. He adjusted the patrol speed, the aggression radius, the cooldown time between attacks.
At the end of the second night, the skeleton was a perfect enemy for the Marble Gallery: dangerous enough that you respected its presence, weak enough that three sword strikes dismantled it. A teacher, not a tyrant.
George couldn't fill a castle with skeletons alone. He needed variety.
He sent Marcus a list of the next enemies in order of priority: a bat that flew in erratic patterns, a zombie that walked slowly but absorbed a lot of damage, a Warg, a dark wolf that charged at high speed, and a ghost that appeared and disappeared, immune to physical attacks except during the seconds when it was visible.
Marcus delivered them over two weeks, one every three or four days, each with the same relentless quality he had shown since the first Alucard sprite. The bat was small, sixteen by sixteen pixels, but its wings flapped with a fluidity that was almost dizzying. The zombie was a swaying mass of gray flesh dragging a broken leg. The Warg was a black silhouette with yellow eyes that ran with a four-frame animation conveying speed and ferocity. The ghost was a technical marvel: Marcus had used semi-transparent pixels to create an ethereal effect that made the ghost look as if it were made of colored smoke.
George programmed the AI for each one. The bat followed a sinusoidal wave on the vertical axis while advancing toward the player: predictable if you watched it, but hard to hit because it was never still. The zombie was slow but had a lot of health and its bite attack dealt considerable damage if it caught you: a tank enemy that forced you to be patient or dodge it entirely. The Warg detected the player from far away and charged in a straight line at a speed that left little reaction time: a danger that taught you to use the backdash. And the ghost forced the player to wait, to observe its appearance and disappearance cycle, and to attack only in the correct window.
Four enemies. Four different combat lessons. Four ways of teaching the player that the castle was a dangerous place and that survival required attention, patience, and reflexes.
The second Sunday of May, George went for lunch with his parents.
Margaret had made lasagna. The house smelled of bechamel and the blend of spices his mother used for the ground beef: oregano, garlic powder, a pinch of nutmeg that was her secret ingredient and that everyone in the family knew about but pretended not to, so as not to ruin the mystery.
Claire was there. She brought a cake from a bakery in the Richmond District, wrapped in a white box with a red bow that looked like a Valentine's Day survivor. Richard opened the door in his usual flannel and his usual coffee mug and his usual expression, which was that of a man who was genuinely glad to see his children but would die before admitting it with more than a grunt.
They ate. The lasagna was perfect. The cake was chocolate and too sweet, which did not stop George from eating two slices.
The conversation was the usual: Claire complained about Henderson and his fax; Margaret asked if either of them had met anyone special; Richard ate in silence, chewing each bite with the methodical determination of a man who believes food is fuel and not an experience.
After lunch, George helped Margaret with the dishes. It was something the twenty-one-year-old George would never have done voluntarily, and Margaret accepted it with the silent suspicion that had replaced surprise after weeks of unusual behavior.
In the kitchen, with his hands in the soapy water, Margaret spoke without looking at him.
"Your father went to the doctor last week."
George almost dropped the plate he was drying.
"To the doctor? Why?"
"His chest hurt. Here." Margaret pointed to her left side with her elbow, without taking her hands out of the sink. "He didn't want to go. I had to threaten to stop cooking until he did. You know how he is."
George felt the floor tilt beneath his feet. The chest pain. Richard. His heart. The ticking clock George knew was there but didn't know when it would start counting down.
"And what did they say?" His voice came out more controlled than he felt.
"That he's fine. That it's probably stress. They sent him to have some blood work done next week. And they told him to lose weight and stop eating so much salt." Margaret huffed. "As if your father were going to give up salt. He'd rather die."
The word "die" floated in the kitchen like an insect nobody wanted to look at.
"Mom. Let me know when the results come in."
Margaret looked at him for the first time. Something in George's tone stopped her: something too serious, too adult for a twenty-one-year-old boy asking about his father's blood work.
"Of course I'll let you know. Why?"
"Because I care. I want to stay on top of it."
Margaret studied him for three long seconds. Then nodded and went back to the dishes.
"I'm going to tell him to call his son every now and then. Maybe the shame will make him go to the doctor more often."
George smiled, but the smile didn't reach his eyes. He finished drying the plates in silence, his mind somewhere else: on a future he hoped he could change and on a heart he was not going to let stop. Not this time.
Before leaving, George sat with Richard in the living room. The Giants game was on television. Richard wasn't a baseball fan but he watched it on Sundays for the same reason most fathers watched sports: because it was something you could do without talking.
George sat on the couch and watched the game without seeing it for a few minutes. Then:
"Dad, Mom told me you went to the doctor."
Richard made a sound that was half grunt, half sigh.
"Your mother and her mouth."
"Are you okay?"
"I'm fine. My chest hurt a little after loading some tires at the shop. That's all. Your mother acted like I was dying."
"Dad, chest pain has to be taken seriously."
Richard looked at him with the expression of a man who had spent thirty years ignoring his body's signals and had no intention of changing that policy.
"I'm fifty-five, George. At fifty-five everything hurts. If I went to the doctor every time something hurt, I'd live in the hospital."
"I'm just asking you to go get the blood work done. And if the doctor tells you to change something, to do it."
"Since when are you my doctor?"
"Since you matter to me."
Richard went quiet. On the television, someone hit a fly ball to center field. The crowd booed. Richard took a sip of coffee and didn't look at George as he said:
"I'm getting the blood work done on Thursday. Happy?"
"Yes."
"Good. Now let me watch the game."
George let him watch the game. He stayed another hour, sitting on the couch next to his father, in a silence that for the first time in his life didn't feel like distance but like company.
That night, back in the apartment, George opened the game and fought the enemies of the Marble Gallery for half an hour.
Skeletons crumbling into piles of bones. Bats falling from the air like dead leaves. Zombies swaying and collapsing. Wargs charging and dying with a silent howl. Ghosts dissolving like smoke.
Lena's waltz accompanied every fight. Marcus's chandeliers flickered. Alucard moved through the hall with his cape and his sword, killing monsters in a castle that grew every day, every week, with each sprite Marcus delivered and each track Lena composed.
George stopped playing and looked at the screen. Alucard waited in his idle pose, breathing, his cape swaying. Around him, the Marble Gallery gleamed with a dark and melancholic beauty that existed in no other game in the world.
It was early May. He had been in development for a month and a half. He had a functional engine, a combat system with five enemies, one artistically complete zone, and two finished musical themes. Lena had sent the Long Library theme the previous week: a harpsichord that sounded of dust and centuries, exactly as George had described it.
There was still a great deal to do. Thirteen more zones. Seventy-five more enemies. Fourteen boss fights. The complete RPG system. The inverted castle. Distribution, marketing, sales. Months and months of work.
But the heart of the game was beating. George could feel it in every sword strike, in every piano note, in every pixel of cracked marble. The game was alive. Imperfect, incomplete, embryonic, but alive.
And somewhere in San Francisco, his father was going to the doctor on Thursday. That was more important than any game.
George turned off the monitor. Got into the futon. Closed his eyes.
Before falling asleep, he made a mental note: call Margaret on Friday to ask about Richard's results. He was not going to forget. Not this time. Not in this life.