Horror Game Developer: My games aren't that scary! novel Chapter 22

Chapter 22: Developing Game [4]

What makes a good horror game?

Is it the constant jump scares or the blood and gore that come along with the scares?

"It's none of that."

I sat in a daze, staring blankly at my computer while the hum of the fans echoed through the otherwise silent room.

Several hours had slipped by since I first sat down and opened my computer, yet in all that time—two long hours—I'd done nothing but stare blankly at the screen.

Developing a game wasn't difficult.

With the current available tools and applications, I was confident in developing a playable game.

But that wasn't the issue.

The issue was making the game scary. Especially in a world where scary games had less effect on the normal folk.

"...This is so much harder than I expected."

I scratched the back of my head, feeling a headache coming.

For a horror game to truly be good, it needed to perfect several elements.

1. The atmosphere.

Tension was needed to build up before the jumpscare.

2. Sound and visuals.

Perhaps some of the most crucial elements lay in how the game engaged the five human senses. Tapping into these, especially sound and music, was essential for crafting the perfect horror experience. The right audio could unsettle, mislead, or completely immerse the player in dread.

3. Storytelling.

This was crucial to instill a psychological seed in a player's mind. It was a developer's job to use that seed and grow it into something bigger.

There were other elements that one needed to take into account when creating a horror game, but these three were generally the most important.

"Hmm."

Click!

I pressed onto the mousepad and opened U-Engine. This was the main developer app that I used back at the old company to develop and program the games.

"...Considering that I need to get this done as fast as possible, I should settle for something simpler."

The good thing about U-Engine was that it had a lot of available templates that I could use to develop the game. The coding could also be kept to a minimum.

"Regarding the game mechanics..."

In order to save time, those also had to be kept to a minimum.

However, it wasn't necessary for the game to have complicated mechanics.

"All I need the character to do is move forward and run."

I tapped my fingers against the table, deep in thought. The engine already provided sound and music, which meant the only pieces I was missing now were the storyline and the overall direction of the game.

"Should I use my most recent experiences as the baseline for the story and direction?"

I sat in silence for a few seconds before pursing my lips.

"Yes, that could work."

There were two scenarios in my head. The first scenario was with the orchestra, and the second scenario was of the most recent trial.

Of the two, the easiest one to develop was the second experience.

The mechanics were simple, and so was the 'monster'.

With my current skill level, developing a monster on par with the conductor was almost impossible. In fact, I was still having trouble handling said conductor.

For now, I could only settle for the second scenario.

With everything planned out in my mind, I cracked my fingers and got to work.

I had no time to waste.

*

Like that, four days passed.

Takakakakaka—

The rapid clatter of keyboard keys echoed loudly through the room. My eyes began to strain from the relentless glare of the computer screen, my head starting to hurt as a result.

Nonetheless, my gaze never wavered from the computer.

And then—

Tak!

"Done!"

With the last press of the keyboard, I pulled my hand back and stared at the product before it.

"...It's still not done, but it should be playable now."

I had incorporated everything I'd learned from my recent experiences. While it wasn't an exact replica, I did my best to recreate the same atmosphere and tension I had felt, capturing as much of that essence as I could.

To Tok—