Why I Decided to Make a Game: Because I Couldn’t Find One I Truly Enjoyed

Lately, I’ve been having one simple thought when looking at games.

“There’s nothing I really want to play.”

There are more games than ever before.
New titles are constantly being released.

But somehow,
it has become harder to find a game that truly excites me.

I’ve spent years searching for something new,
jumping from one game to another,

only to end up returning
to the same old games I used to play.

I want something new,
but the kind of game I’m looking for just isn’t there.

At some point, a thought crossed my mind.

“What if I just make it myself?”

Of course, reality wasn’t that simple.

I have no background in game development,
and my programming knowledge is almost zero.

C, Python…
I’ve heard of them, but never really used them.

With a busy work life,
finding time to learn something new felt almost impossible.

But recently, I discovered something interesting.

We now live in a time where you don’t necessarily need
to know programming to start making games.

For example, :contentReference[oaicite:1]{index=1} offers a system called Blueprint,
which allows you to build games without writing code.

That changed my perspective.

“Maybe I can actually try this.”

So I decided to set a clear direction.

Not to make a game that everyone likes,
but to create something I genuinely enjoy.

I want to look back at the games I loved in the past
and understand what made them fun for me.

From there,
I’ll start shaping the kind of game I want to create.

It won’t be easy.

I don’t have much time,
and there’s so much I don’t know.

But at least now,
I want to move from being someone who searches for games
to someone who creates them.

This is the beginning of that journey.

댓글 남기기