This Was Supposed to Take a Week. It Took Months.

Four skins. Four moods. Four musical identities.

I wrote my last article in December.

At the time, I thought I’d be back with an update in a week or two. A quick continuation. A smooth progression. That didn’t happen.

Not because I lost interest.Not because the project stalled.But because the work turned out to be far heavier than I was prepared for. The truth is simple: this phase took much longer than expected.

The Part I Thought Would Be “Easy”

After December, I entered what I assumed would be a calmer phase of development.

Skins.Settings.Cleanup.Polish.

On paper, it sounded like the easy part. The phase where everything starts to come together.

Instead, it became one of the most demanding and humbling parts of the entire journey so far.

Skins aren’t just visual layers. They affect memory, performance, UI scaling, animation flow, and even how players emotionally read the game. Every choice introduced new constraints.

Every solution revealed new problems.

Nothing existed in isolation.

When Progress Becomes Invisible

One of the hardest parts of this period was that progress stopped being obvious.

Days went by where the game didn’t look different, but under the surface, everything was changing. Systems were rewritten. Settings were rebalanced. Edge cases were hunted down.

From the outside, it might look like nothing happened. From the inside, it felt like carrying the entire structure on my shoulders.

That kind of progress is hard to celebrate. There are no screenshots for it. No flashy features to show. Just quiet, exhausting work.

Why It Was So Mentally Heavy

This wasn’t beginner work anymore.

The game already existed.It already worked.It already had an identity.

That makes every decision heavier.

You’re no longer asking, “Does this work?”You’re asking, “Is this right?”

Is it better, or just different?Am I improving the experience, or just chasing perfection?Should I keep refining or move forward?

There were long stretches where the hardest part wasn’t coding, but deciding when to stop.

Hard, Slow, and Deeply Educational

I won’t pretend this period was fun.

It was difficult.It was mentally draining.And at times, it was frustrating in a way that only long-term solo projects can be.

But it also reshaped how I think about development. I learned more about structure, restraint, and long-term design here than in any fast-moving phase earlier. This is where shortcuts reveal themselves. Where weak assumptions collapse. Where you either rebuild properly,or carry the cost forever.

I chose to rebuild.

Why I Kept Going

There were moments when I questioned the pace. The delay. The effort.

But every time I played the game again, something important remained true:

It still felt good.

Even unfinished.Even imperfect.Even after long days of frustration.

That feeling became my anchor.

Karmo wasn’t just surviving this phase, it was becoming more honest, more stable, and more intentional.

And that made the work worth it.

Still Here, Still Building

Yes, it took longer than planned.Yes, the update came later than expected.

But the foundation is stronger because of it.

This wasn’t lost time.It was invested time.

Karmo is still moving forward, more carefully now, with more respect for the invisible work it takes to build something that truly feels right. And so am I.

Closing

I didn’t delay this update because I ran out of motivation or ideas.

I delayed it because I simply didn’t have the time to write.

For the last month, I’ve been working on Karmo close to 13 hours a day, mostly on small, unglamorous tasks. Tiny adjustments. Settings. Fixes no one will ever notice individually, but that all matter together. It’s been exhausting at times, no question about it.

But here’s the truth.

Even on the hardest days, I still love working on Karmo.

Because every time I test the game, it makes me smile. There’s a charm to it that’s hard to explain, something soft, positive, and joyful that you just melt into. That feeling is what Karmo is really about. Not perfection. Not speed. Not deadlines.

Joy.

That’s why I keep going.

This journey hasn’t been clean or predictable. It hasn’t followed neat timelines. But it’s been real, and deeply meaningful to me.

Still building.Still learning.Still committed.

Until next time - I’ll keep you updated.