When it came to marketing the upcoming release, John had no intention of leaning heavily on the plot. It wasn't that the story of Wolf: Shadows Die Twice lacked flavor, far from it. The narrative was intricate, thrilling, and deeply engaging, featuring a branching paths system with multiple distinct endings depending on the player's choices and progression.
Take the most common route: the "Immortality Severance" ending. After a grueling battle where the protagonist, Wolf, finally overcomes Juggernaut One Heart, he carries out the solemn request of his young master. Using the blade of immortality, he severs the young master's mortal ties, then quietly retreats to the dilapidated temple to take up the mantle of the Buddha Carver, trapped forever in the next lonely, unbroken cycle.
Alternatively, should a player walk the dark path, Wolf transforms into an avatar of Shura, an unfeeling, bloodthirsty killing machine. Or, in another tragic conclusion, after defeating the ultimate enemy, Wolf helps his young master return to a normal human life, choosing to end his own existence so that the gift of immortality is extinguished forever.
And, of course, beyond these three tragic fates lies a hidden, elusive fourth ending, one where both the young master and Wolf find a way to survive together.
From a narrative perspective, using the plot as the main promotional hook for Wolf: Shadows Die Twice was certainly viable; the writing and world-building were exceptional. However, John recognized a fundamental truth: at its heart, this was a high-octane action game. He wanted players' undivided attention anchored directly on the core gameplay mechanics.
In an action game, a compelling storyline is undeniably a great asset, but it is rarely the main selling point. John wanted players to be completely spellbound by the sheer adrenaline, fluid responsiveness, and raw impact of the game's combat system.
To achieve that level of martial fluidity, John and his production team had poured immense effort into the action design. They had even brought in Boyce Zheng, one of the most celebrated action choreographers in the film and game industry, to ensure every swing, parry, and strike felt uniquely visceral.
In the original, the protagonist operated as a ninja, but his execution moves were somewhat repetitive and limited to a few static animations: grabbing an enemy to drag and plunge the blade in, plunging down from above to slam into the earth, or slashing across before driving the steel home.
John wasn't satisfied with that. Under his direction, the team engineered over a dozen custom execution animations tailored specifically to different enemy types, from low-level fodder to towering, intimidating bosses.
To John, this added layer of polish was absolutely essential. For players, executing a magnificent, bloody finisher provided an irreplaceable surge of satisfaction and achievement. After enduring relentless danger, dodging lethal strikes, and finally bringing a devastating boss to his knees, watching an extraordinarily stylish, cinematic execution sequence before the boss transitioned into his second phase, was that really too much to ask?
Naturally, all execution animations adhered strictly to three core principles: quickness, precision, and lethality. There was no place for overly flashy, impractical acrobatics. True to an assassin's nature, every movement targeted the fastest, most effective method to eliminate the target instantly. To heighten the sensory impact for the player, strategic camera angles and brief slow-motion frames were woven in at critical beats.
However, John kept these dramatic close-ups strictly reserved for boss encounters. If every common soldier triggered a slow-motion close-up upon death, it would quickly drag down the pacing and ruin the fluid rhythm of combat.
As for the specific animation variations, as well as necessary additions or deletions during production, those details would depend entirely on feedback gathered from internal testing.
Looking back at Wolf: Shadows Die Twice from his dream memories, some might wonder: why didn't the original version feature such a rich variety of execution animations? Was it considered unnecessary? Of course not! The real culprit was simple: money! Did people truly believe high-quality execution animations were cheap to produce?
Creating a polished execution sequence that felt genuinely satisfying to play required astronomical resources. Even with a complete combat design already in place, setting up a single day of motion capture runs anywhere from $25,000 to $50,000. That cost only covers standard gestures and basic body movements, allowing a team to record roughly a hundred sets of standard motions a day.
Specialized combat maneuvers, however, especially execution moves requiring unique choreography, custom physical items, additional stunt actors, and extensive post-production processing, were far more expensive.
What about skipping real-time engine rendering and just dropping in pre-rendered CG cutscenes? That would be even more prohibitively expensive!
Even excluding post-processing refinements, capturing the raw movement data for a single complex execution sequence alone could easily swallow $50,000 to $80,000 in motion capture costs. It wasn't that developers lacked the vision; they simply lacked the budget to burn.
Furthermore, unlike dedicated fighting games, combat executions in a single-player action-adventure didn't fundamentally alter the balance of the core loop. For instance, in a classic fighting game like Street Fighter 4 from his dream memories, developing a single playable character cost roughly one million dollars.
When fighting games sell downloadable DLC characters for around ten dollars each, casual onlookers often accuse developers of being greedy. Yet, from a pure production cost perspective, a single character truly required that level of investment to break even.
While an individual execution animation in Wolf: Shadows Die Twice didn't reach quite that staggering price tag, when factoring in all associated design overheads, a single high-tier execution sequence still easily racked up a $120,000 price tag.
"Sir, the testing program is ready." Inside the spacious executive office, Koch walked up to John's desk and reported his progress.
"Finished already? Hand it over to me," John replied, coughing slightly to clear his throat as his eyes darted toward the monitor at the adjacent workstation. On Koch's screen, a bold, blood-red icon for "DEATH" was glaringly displayed. "I don't need you to bring over the video footage; I'll handle capturing the gameplay materials myself."
Taking the flash drive from Koch, John plugged it into his computer and booted up the utility program. The interface was extremely spartan, clearly put together using placeholder assets found in the temporary database, but John didn't mind the aesthetics. Functionality was all that mattered.
Clang! Clang! Clang! The sharp, crisp sound of clashing steel echoed from the monitor's built-in speakers. A satisfied, self-assured smile spread across John's face as he parried in rhythm. However, a split second later, his smile froze.
Without him realizing it, the posture bar of his character, Wolf, had filled up completely. In the blink of an eye, the enemy boss cleaved downward, hacking his character to death like a helpless chicken.
"Hesitation is defeat..." The cold, indifferent voice line replaced the rhythmic sound of clashing metal.
John looked up, casting a quick glance around the quiet, deserted office. He looked back at the grayed-out game over screen on his monitor, silently closed the game window, and opened the internal messaging app. Navigating to the project group list, he initiated a private chat with Koch.
John: Add an infinite health toggle to the developer utility tool. We'll definitely need it for later balance testing anyway. Since we're making the tool, we might as well make it feature-complete.
Koch: ???
Staring at the message from John, Koch sat frozen at his desk for a moment, an awkward silence washing over him. Then, without a word, he opened his development environment and began modifying the software's source code.
The justification sounded perfectly reasonable on the surface... but the more he thought about it, the more he realized he had just stumbled onto a top-secret truth. Wait... is the President actually terrible at his own game? Koch mused secretly to himself as his fingers flew across the keyboard.
Since it was just a basic command flag, the modification took virtually no time at all. By the afternoon, John successfully received the updated software from Koch. With God-mode safely activated, he recorded a flawless, dramatic victory over the boss.
Thoroughly satisfied with the result, John closed the game and forwarded the freshly recorded footage directly to the marketing department's group chat.
John: Cut a promotional trailer using this footage. Edit out the parts where the player gets hit or triggers the passive posture break, and focus entirely on making it look like an intense, flawless duel between legendary warriors. Once the draft is ready, send it over for my approval.
The entire Marketing Department: ???
Opening the forty-minute raw recording, the marketing team members stared at the screen, their lips twitching in unison as a collective silence fell over the room. Ten minutes of killing the boss, and thirty minutes of getting beaten black and blue?!