Hi, I just received Indiecade feedback on Quantum Pilot.
Gameplay video in my sig v v , or PM me for a download code if you'd like to try.
I would like your design & production advice on this feedback, which is not unique.
I think you have a neat idea that I've seen in other experiments! It will require fleshing out in order to be a more compelling experience. Right now it feels like a prototype of one mechanic.
I would encourage you to continue working on it, as it sounds like a very personal and passionate project of yours, and I wonder what a final game in its genre would look like from your unique perspective.
While the main hook is somewhat unique, it's not enough to carry the game. The idea of destroying past selves is a strong message, and the mechanics, design, and environments should reflect this. Find a way to enhance this core theme. Add variance to the enemy ships, maybe color-code the player ship so when the clone appears as the previous color, the player can make the association with past actions.
Interesting idea. It feels like an interesting experiment that could be fleshed out into more.
I had to focus very specifically in order to realize that I was fighting myself. If I hadn't been told beforehand, I probably wouldn't have noticed it and thought that it was just AI controlling the enemies. Perhaps some coloring or other visual cues would help with that.
In the time I had with the game, my strategy ultimately boiled down to (A) don't shoot too much, and (B) try to stagger when you shoot [for example, don't shoot always at the beginning of a round]. In the end, this felt pretty simple. For me, it didn't go as deep as I had hoped. Perhaps designing other mechanics and behaviors that really play to this mechanic could make it shine more.
Also, there is a lot that could go into polish on the look and feel of the game.
The color-coding clones has been brought up a few times. Currently, the color of the ship indicates what weapon you are using. This isn't very impactful early on in the game as the clones always have the same weapon as you. In the second half, your weapon is randomized each level so its helpful to see which clones have which weapons so you can anticipate their shots.
What do you suggest? Some possibilities: distinguish ship weapon by a symbol or mark of some kind. Show weapon name at bottom of screen or in icon format. Show weapon icon inside of enemy ship so you know what weapon by icon and what pattern by their color.
Hm now that I think of it, it's not critical that the color match weapon.. I did that to distinguish weapons & give a sense of progression. I see that even in the second half, remembering which color = which pattern you could still remember which weapon you had then.
Look and feel: It is very abstract. Ships are 4 vertex polygons, bullets are short segments. Pixel-perfect hit detection and very simple shrinking circular explosions. Every object is 1 color against a black background. I think a lack of distinguishing color between the bullets & ships is a failure here. Perhaps all bullets should be red, and enemy ships are never red?
A more complicated ship design could be in order here, perhaps something with multiple segments of different colors. I want any changes to still be very readable with regards to position. I originally had the clones be hollow outlines and they were difficult to track.
Additional layers & mechanics: Oh boy. The game is intentionally simple here and I haven't thought far beyond this. I've made a few experiments in multiplayer competitive but I'm not sure what layers I could add here. Open to suggestions.
"Mechanics, Design & Environments" - what could I do here that would be compelling & dramatic?