u/RivakGamesStudio

When I started sharing my thoughts and asking questions here, I expected different opinions.

What I didn't expect was how direct people can be.

Some comments have been incredibly helpful. They pointed out mistakes I hadn't noticed and made me think differently.

Others were much harder to read. A few people immediately assumed I was using AI, some dismissed my ideas without much explanation, and a few replies honestly made me question whether I should keep posting at all.

I'm still at the beginning of my journey, and I'm trying to build an indie game studio from the ground up. Like everyone else, I'm learning as I go.

I'm not writing this because I want people to stop criticizing me.

In fact, I think criticism is one of the fastest ways to improve.

What I'm still learning is how experienced developers deal with criticism that isn't really constructive.

How do you know when someone is genuinely trying to help, and when it's better to simply move on?

Did you ever have a period where every piece of feedback felt personal?

Or does that become easier with time?

I'm genuinely interested because I want to improve—not just as a developer, but also as someone who wants to be part of this community.

Many studios spend months—or even years—iterating on gameplay, rewriting stories, redesigning characters, removing mechanics, and cutting content that simply doesn't improve the final experience.

It made me realize that game development is often more about making good decisions than just building new features.

So I'm curious:

If you were leading a game project, would you rather release it earlier or delay it until you're truly happy with the result?

I'd love to hear different perspectives from both players and developers.

When we started working on our studio, we thought the hardest part would be coming up with ideas.

It wasn't.

The hardest part has been making decisions.

Sometimes we spend hours exploring a feature, only to remove it because it doesn't make the game better.

It's frustrating, but it's also part of the process.

We're still early in our journey, and one lesson keeps repeating itself:

Building a game isn't about adding everything you can. It's about choosing what truly matters.

I'm curious about other developers or aspiring creators here:

What's the toughest lesson you've learned while building your first project?

I'd genuinely love to read your experiences.

Motivation is unreliable by nature, it comes and goes regardless of how much the work actually matters. The projects that survive are the ones where showing up became a habit instead of a feeling.

Genuinely curious how people here handle this. Do you treat consistency as something you build like a muscle, or does it come more naturally once you're deep enough into a project you care about?

Yesterday I spent way longer than I should've fixing what looked like a tiny bug.

Fixed it. Felt good for about five minutes.

Then found out it had quietly broken three other things that were working fine before.

Anyone else have that moment where "fixing" something feels like it set you back further than if you'd left it alone? Curious how other devs deal with that feeling.

Hey everyone,

We're RIVAK Games, a small independent game studio.

Right now, we're working on our first project. It's still early in development, but we're excited to share the journey from the very beginning.

Here you'll find:

• 🎮 Development updates
• 🛠️ Behind-the-scenes progress
• 💡 Ideas and experiments
• 📸 Screenshots and gameplay clips
• 💬 Honest discussions about game development

We're here to learn, improve, and connect with other developers and players.

Thanks for stopping by.

— RIVAK Games