HomeGamesUpdatesPricingMethodology
Steam News25 June 20251y ago

A journey to a Dream!

Hello everyone, I’d like to share everything that’s happened—all the progress and setbacks I’ve had during the development of this video game idea.

Full notes

Full Arc’s Glitch Defender update

Read the full published notes in a cleaner layout. The original post stays linked below.

Repeated intro

Hello everyone, I’d like to share everything that’s happened—all the progress and setbacks I’ve had during the development of this video game idea. It’s been an emotional journey, full of ideas, code, hours of work, optimisations, and more. From the very beginning, since conceptualising the idea, I’ve wanted to lay a solid foundation for future updates and thank myself later when it’s time to revisit mechanics. So, a big part of my time has been spent reading, studying the engine, and refreshing my knowledge of programming paradigms applied to games.

What changed

0 fixes0 additions2 changes0 removals
  • UI and audio
  • Compatibility
changedCurrently, I’m a software developer in my daily work, which is why topics like CI/CD, state machines, the single-responsibility principle, and SOLID have been the foundation of this project. Little by little, the game is taking shape, and it’s been amazing to see how many details can emerge during the process, so much so that I’ve had to delay the release a bit. But it’s for a good reason: first, to avoid burnout, and second, to deliver at least a quality product to you all.
changedAt this point, I’ve sent several beta versions of the game for review to gather feedback, but it would be great to expand this community, too. Perhaps there are many people out there eager to learn a little more.

Arc’s Glitch Defender changes

changedCurrently, I’m a software developer in my daily work, which is why topics like CI/CD, state machines, the single-responsibility principle, and SOLID have been the foundation of this project. Little by little, the game is taking shape, and it’s been amazing to see how many details can emerge during the process, so much so that I’ve had to delay the release a bit. But it’s for a good reason: first, to avoid burnout, and second, to deliver at least a quality product to you all.
changedAt this point, I’ve sent several beta versions of the game for review to gather feedback, but it would be great to expand this community, too. Perhaps there are many people out there eager to learn a little more.

Currently, I’m a software developer in my daily work, which is why topics like CI/CD, state machines, the single-responsibility principle, and SOLID have been the foundation of this project. Little by little, the game is taking shape, and it’s been amazing to see how many details can emerge during the process, so much so that I’ve had to delay the release a bit. But it’s for a good reason: first, to avoid burnout, and second, to deliver at least a quality product to you all.

I’ve been thinking a lot about how to improve community engagement and share updates with everyone who’s shown interest. But I’d like to ask you: How would you prefer to receive updates or see progress? I can’t promise daily posts, but at most once a week (otherwise, I’d stress myself out, hehe). Sometimes, I’ve seen that sharing progress can feel tedious for some developers, so I was considering using a Discord channel for more direct communication and updates. Would that be something you’d be interested in?

At this point, I’ve sent several beta versions of the game for review to gather feedback, but it would be great to expand this community, too. Perhaps there are many people out there eager to learn a little more.

I’m excited to keep building this together and hearing your feedback. Let me know what you think—I’m all ears!

Discord:

https://discord.gg/rjRDHc7M

Source

Steam News / 25 June 2025

Open original post

Changelog.gg summarizes and formats this update. How we read updates.