Cherreads

Chapter 341 - Chapter : 339 : This Is To Let You Better Understand The Game Development Ideas

The difficulty of a video game fluctuates on a massive spectrum, but at its core, it truly tests a developer's fundamental talent. First, consider the most simplistic and brutal approach: basic numerical scaling.

Under a purely numerical system, a boss on simple difficulty might hit for modest damage with a modest health pool of 100. Dial that up to hard, and suddenly the boss's attack power and health balloon to a staggering 1000.

You see this lazy approach most often in cash-grab mobile titles or predatory online games. The sole purpose is to hit a player with an artificial wall, forcing them to open their wallets, drop real cash on microtransactions, and buy their way through the level.

For the vast majority of gamers, especially in an era where game development continues to evolve at a rapid pace, this style of difficulty is downright repulsive. Even in a loot-heavy, grind-focused game, relying entirely on raw stat-bloat to challenge players feels insultingly brain-dead.

True challenge extends far deeper into game design. In a well-crafted hard mode, a boss might unveil a completely new second-stage transformation, or collaborative maps might introduce tricky environmental hazards that force players to rethink their strategy. This represents genuine, thoughtful difficulty planning: to the player, a greater difficulty level unlocks a brand-new experience.

For the upcoming game Sekiro: Shadows Die Twice pulled straight from his dream memories, John knew he had to maintain an absolute, unflinching control over its difficulty curve.

He had no intention of making it easier. Granted, most modern games hand-hold the player through an accessible "Normal Mode" so anyone short of a complete fool can coast through and watch the story unfold. But for a title like Sekiro: Shadows Die Twice, and the uncompromising genre it belongs to, diluting the difficulty meant ripping out its very soul.

Whether you look at grand dark-fantasy masterpieces like Dark Souls or samurai-and-ninja action epics like Sekiro, their brilliance doesn't just stem from their aesthetic backdrop. It comes from the spirit woven into their core design: persistent struggle, relentless trial, and the triumph of self-transcendence.

That core spirit is sculpted entirely by gameplay mechanics and uncompromising difficulty. Everything must be meticulously calibrated: the intricate architecture of the maps, the deadly, deliberate attack patterns of the bosses, and the underlying mathematical balance.

Of course, plenty of casual observers claim this genre is a niche, sadistic taste. But in reality, these games masterfully construct a smooth, rewarding learning curve. Barring those who genuinely lack hand-eye coordination, the struggle isn't about being talentless; it's about practice.

As players push forward, they slowly but unmistakably feel themselves growing stronger. You start out struggling to survive against low-level mobs, clawing through five-on-one brawls by the skin of your teeth. Soon, you're standing toe-to-toe with colossal bosses. Before you know it, a boss that once felt entirely impossible falls to your blade, leaving you breathless with only a sliver of health remaining.

Players can actively measure their own growth at every turn. Neither Dark Souls nor Sekiro ever suffered from artificial difficulty for the sake of being cruel.

Beyond action mechanics and world design, the thematic backdrop demanded careful handling. John wasn't keen on simply copying the historical Sengoku-era Japanese setting wholesale. He preferred an abstracted, fictionalized world. After all, John himself had no deep personal connection to traditional Japanese samurai and ninja folklore; trying to force a pixel-perfect historical replica based purely on memories of his past life would only result in a hollow, lifeless imitation.

Polishing fluid combat mechanics was well within reach. With PixelPioneers' current talent pool, John was fully confident in their ability to execute top-tier action. But when it came to capturing authentic cultural nuances, he knew they'd fall short if they tried to fake an ethos they didn't live and breathe.

Much like some developers' obsession with medieval chivalry, other gaming culture has its own classic staples. Yet whether crafting a sweeping epic or an intimate personal story, 

In John's view, Sekiro's core mechanics actually possessed a strong, fluid martial arts sensibility that translated beautifully to a broader Eastern aesthetic, likely because Japanese warrior tradition historically drew deep inspiration from mainland culture.

At the same time, as legendary as Sekiro: Shadows Die Twice was, John wasn't blind to its flaws. Asset recycling on enemy models and an overly sparse, borderline cryptic tutorial were clear defects born from budget and time constraints.

Many hardcore fans argued that a vague tutorial enhanced immersion and environmental exploration. But was it really better to copy mobile games with a mind-numbing, thirty-minute hand-holding sequence that treats players like toddlers? Absolutely not. Still, when a player dies, the game should at least clearly communicate why they died.

Where the original game cut corners to save on production costs, John was determined to refine and elevate every last detail.

The following morning, inside the PixelPioneers Game Studio conference room.

John stood at the head of the long table, sweeping his gaze across the assembled team. Front and center were Koch and Evelien, the battle-tested veterans who had stood by him since the company's humble beginnings, surrounded by a fresh cohort of talented new hires.

"I called this meeting because I think most of you already have a hunch," John announced, his voice steady and commanding. "Starting today, we are kicking off development on our next major title. And it will define a completely new genre of gaming."

Turning to his workstation, John fired up the projector, displaying a single slide on the wall behind him.

The team blinked, staring at the screen in utter confusion. ??? What was this supposed to mean? They were supposed to be brainstorming a groundbreaking new release, so why were the main headlines on screen pointing to Getting Over It and Jump King?

The developers exchanged bewildered looks. Normally, when starting a project, wouldn't the boss present a master design document or an art direction brief?

"How many of you have played either of these games for more than an hour?" John asked calmly, leaning against the podium.

Silence filled the room. The team glanced at one another, but not a single hand went up. It wasn't that they hadn't tried them; every developer in the room had fired them up out of curiosity, only to rage-quit shortly after. After all, those games weren't just hard; they were pure, unadulterated torture!

"Starting today, everyone in this room will spend one hour every single day playing these two titles," John declared with a straight face. "And no, this won't be on your personal time. You'll do it during work hours, and you will upload a video recording of your daily progress to the team chat on schedule."

It was the ultimate anti-slacking protocol.

Back when he led Evelien and the crew through the development of Outlast, he had dragged them to an actual abandoned asylum at night to soak in the terror. Now, with no existing market template for this new genre, forcing the team to endure Getting Over It and Jump King was the fastest way to hammer home the mechanics of punishing difficulty and the thrill of personal breakthrough.

The developers stared at John with wide, horrified eyes. Play what?! Spend work hours suffering through THOSE two games?! Are we actually making a game, or are you just trying to break our sanity?!

"Oh, right," John added casually, catching himself mid-thought. "Since you three are leading art, audio, and narrative, you're exempt from the playtests. But for numerical balance, level design, and systems planning... you guys get an extra half-hour of playtime added to your daily quota."

Instantaneously, smug grins broke out across the faces of the three. Opposite them, the level designers and balance testers slumped in their chairs, expressions instantly shifting to pure, unmitigated despair.

Watching the color drain from his team's faces, John cleared his throat lightly, a subtle smirk playing on his lips. "Look at it as an immersive study session. It's the best way to grasp the spirit of what we're building. Because the new game we're about to make... is called Sekiro: Shadows Die Twice."

More Chapters