Square Head Zombies 2 - FPS Game

I try to approach every small solo-dev project with patience, because one person building a game from scratch deserves more than a five-second dismissal. Square Head Zombies 2 stretched that patience considerably. It is a low-poly, first-person shooter built around a simple goal: clear each level of blocky, square-headed zombies before they reach you. The settings shift across malls, city streets, beaches, offices, and farms, and the sequel introduces finite ammo pickups scattered through levels, a step up from the first game where bullets were infinite. The zombie roster does have some variety. Slow shambling types mix with faster, more aggressive enemies, and some attack at range while others close in on you directly. In concept, that is a reasonable skeleton for a budget FPS. In practice, the controls make all of that feel academic. There is no key rebinding. Mouse inversion is not an option. Community reports describe an input bug that causes the player character to drift constantly toward the rear right, with no way to correct it. Completing a level and hitting the next-stage button can lock up the game entirely, leaving players stranded on level one with no way forward. These are not minor friction points. They are structural failures that block the core loop before it has a chance to develop any rhythm. A shooter where you cannot reliably aim or progress is not really a shooter. The Steam community score sits at roughly 50 percent positive across a small sample of reviews, which feels about right. The people who land on the positive side tend to be achievement hunters treating this as a checkbox exercise rather than a game to enjoy. There is a full 100-percent completion guide floating around the community hub, and that context tells you a lot about why someone might be here. The pixel-art aesthetic is serviceable without being interesting, and there is no soundtrack worth noting. The soundscape is functional at best and absent at worst. For achievement collectors or anyone who simply wants the most frictionless route to a completed library entry, the game exists, and at deep discount it costs almost nothing. But honesty demands saying that the bugs documented by players are serious enough to prevent a normal run. If you hit the movement drift issue, the game is unplayable until or unless it resolves on its own. A solo developer putting something this rough on a storefront, without addressing reported game-breaking input problems years after release, is hard to defend no matter how warm I want to be toward small indie projects. Kai, Scout Team