Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

šŸŽ® Fun & Gameplay:

The game has the foundations of a solid arcade shooter, but several quality-of-life and pacing issues hold it back. Booting up the game takes too long, and getting into a run is bogged down by too many unskippable screens. Adding a "Skip All" button and saving the game state between screens would drastically improve the onboarding flow. When the player's ship is shown, they should be able to play with it immediately! Additionally, the lack of a pause or settings menu is a noticeable omission.

In combat, the controls feel sluggish. Pressing the shoot button doesn't trigger an immediate reaction, which hurts the moment-to-moment feel. The decision to punish players with limited ammo and slow regeneration feels unsatisfying rather than challenging. Furthermore, hitting enemies lacks impact; adding visual cues like enemy hit flashes would help immensely. 

There are also a few confusing design choices: it's not obvious that "A" refers to the gamepad button rather than the keyboard key (which is unbound), and the large monster traversing the screen doesn't seem to damage the player, leaving its purpose unclear.

The hacking function is confusing, it should be better introduced in the game or maybe just explained better in the description.

šŸŽØ Graphics & Audio:

Visually, the game struggles with clarity. The UI elements are too crowded with unnecessary details, and the fonts are inconsistent and sometimes too small to read comfortably. While the HUD is clearly styled after modern recreations of classic console shooters, it ends up being very distracting. 

The playfield composition feels unbalanced, as the left marquee is larger than the right one and the action isn't properly centered. In-game, the player ship and enemies share the same brownish color palette, making it difficult to distinguish between them—better contrast is essential here. The scanlines also muddy the high-resolution visuals rather than enhancing them, and the basic explosion effects fail to deliver a satisfying impact.

Audio is a mixed bag. The gameplay music is a highlight and fits the theme perfectly, but the title screen music feels entirely disconnected from the in-game tracks. Sound effects are overwhelmingly loud, which is compounded by the lack of a volume slider. The firing sound is particularly grating due to its repetitiveness; adding slight variations in pitch and volume would make it much more pleasant.

šŸ¤– AI Implementation:

It is currently unclear how AI tools were utilized in the development of this project, as no obvious generative art or AI-driven mechanics stand out. If AI was used, highlighting its specific contribution to the game's scope or systems in the description would be helpful.

šŸ’” Final Thoughts:

Neon Vanguard has the bones of a great retro-inspired shooter and features some excellent gameplay music. However, it needs significant polish to address sluggish controls, cluttered visuals, and audio balancing. With a focus on snappier onboarding and improved combat feedback, this could be a fantastic arcade experience. Great effort, keep refining it!

(+1)

respect. Saves me from having to guess what worked and what didn’t.

First off, thanks for the encouraging parts. I’m glad the core arcade feel and especially the in-game music landed, because that’s very much the heart of what I’m trying to build.

I do agree with some of your criticism, especially around onboarding and clarity. The intro flow has grown a bit… ambitious, and it’s fair that it slows players down instead of pulling them in. That’s something I’m actively reworking. Same goes for readability and feedback in combat, there’s definitely room to tighten things up so hits feel more satisfying and information is easier to parse.

That said, some of the points about sluggish gameplay and long load times raise a bit of a different question. The game is fairly lightweight under normal conditions, so when it starts feeling slow or unresponsive, it often points more toward hardware limitations than pure design issues. That’s still on me to optimize better, but it might explain why the experience felt especially heavy on your end.

Also, small correction: there is actually a pause menu in the game. It tends to fly under the radar, which probably says something about how clearly it’s communicated, but it’s there… and I’ll shamelessly claim it’s a pretty nice one too.

On the music: I get why the title screen track feels disconnected, but that part is very intentional. The contrast is meant to create a slightly chaotic, punky tone rather than a perfectly cohesive soundscape. It’s less ā€œconsistent moodā€ and more ā€œattitude.ā€ So that one I’ll stand by.

For context, this is also my first real game, and I’m basically vibe-programming my way through it after not touching code since the QBasic era. So a lot of what you’re seeing is me learning in real time, sometimes elegantly, sometimes… less so.

Overall though, this kind of detailed feedback is genuinely useful. Underneath the rough edges, you clearly saw what the game is trying to be, and that part matters.

(+1)

Ooh, an old geez like me! I was in your place a couple years ago and AI assistance was not even there. Nowadays it's a very powerful tool in the hands of experienced developers. Anyway, it's awesome as a first real game! Keep at it!