Helvengard #004
Building a Game Together

Up to this point, game development was something I did mostly on my own.

I was experimenting, learning, and trying things out.

But that changed when my son got involved.

He saw what I was doing, got curious, and at some point we decided to build something together.

That moment changed everything.

It was no longer just a hobby or a side activity.
It became a real project.

We didn’t overcomplicate things at the beginning.

We chose a game idea that felt manageable. Something inspired by a game I played as a kid — pushing blocks, solving small challenges, interacting with enemies in a structured environment.

Clear mechanics.
Small levels.
A simple concept.

At least, that’s what we thought.

We divided the work in a very natural way.

I focused on coding, game logic, and the engine.
He took care of graphics, assets, and the visual side.

This worked extremely well.

We didn’t need constant coordination for every step.
Each of us could move forward in our own area.

And that created speed.

The beginning was one of the best parts of the entire project.

We made fast progress.
We saw results almost every day.
We built features, tested them, and improved them.

Sometimes we even took entire days just to work on the game.

That time was incredibly valuable.

Not because everything worked perfectly,
but because we were building something together.

As the project developed, it became more than just a collection of features.

It started to feel like an actual game.

Levels connected.
Mechanics interacted.
The world began to make sense.

We could play it.

We could test it.

We could see what worked — and what didn’t.

Working together added a completely different dimension.

It wasn’t just about solving technical problems anymore.

We had to communicate ideas.
Align expectations.
Make decisions together.

And that changed how I approached development.

It became less about isolated features
and more about the overall experience.

Step by step, we moved forward.

Not perfectly.
Not efficiently.
But consistently.

And eventually, we reached the point where the game was finished.

Not perfect.
Not polished like a AAA title.

But complete.

Playable.
Stable.
Released.

We published it on Steam.

This project means a lot to me.

Not just because we built a game,
but because we finished it together.

That experience stays with you.

It shows you what it really takes to bring something to the end.

Looking back, this was one of the most important phases in my journey.

It showed me that building a game is not just about code or design.

It’s about commitment.
Consistency.
And finishing what you start.

And that’s when reality started to catch up.