Target Shooter

Overview

Target Shooter is a fast-paced aim-training game I developed in one week. With such a short timeframe, I focused on what makes shooting feel good instead of trying to build a large or complex game.

The prototype is built around responsive controls, clear hit feedback, and a steady rhythm of targets. Keeping the scope small let me spend the available time testing and refining the core interaction, then polish the presentation around it.

Design & gameplay

Responsive shooting

The shooting system is built around immediate feedback. When the player fires, a raycast registers the shot at once, making the controls feel fast and precise.

Targets react as soon as they are hit, reinforcing the connection between the player's input and the result. This direct response is central to making the shooting feel satisfying, so I kept the interaction immediate rather than adding delays or extra steps.

Feedback & clarity

Clear feedback was central to the experience. A distinct sound confirms each successful shot, and targets disappear on impact. Their presentation also makes them easy to track.

These signals make a successful hit easy to understand and more rewarding. Moving targets add challenge and variety while keeping the same simple shooting mechanic at the heart of the experience.

Reference-based design

I took inspiration from aim trainers such as KovaaK's FPS Aim Trainer, especially their emphasis on responsiveness and feedback. I applied those fundamentals through instant shots, clear audio confirmation, and simple, readable targets.

From there, I developed the presentation in my own direction while keeping the focus on a clear, responsive shooting experience. The references helped me identify what to prioritize, while testing shaped how those ideas worked in my prototype.

Development

Building the core mechanic

I began by recreating a simple shooting system to understand how it worked. I used a raycast to detect hits instantly, matching the responsiveness I wanted from an aim trainer.

I then added basic feedback, including hit sounds and target reactions. Testing these elements early helped me judge whether the central action felt right before building more systems around it.

Rapid prototyping & iteration

Because the project had a short timeframe, I tested ideas quickly rather than spending too long planning. I prototyped target spawning, movement, and shooting interactions, then adjusted or removed anything that didn't feel right.

I also tuned details such as fire rate, spawn timing, and target speed. Changing these values affected both the difficulty and rhythm, so I tested them together to create a more balanced experience.

Focus on the core over complexity

I kept the visuals minimal early on so I could focus on how the shooting felt. Once the mechanics were working well, I refined the presentation.

This order kept development focused on what mattered most: making a simple mechanic feel as good as possible before adding polish. It also gave me a clear way to prioritize work within the one-week limit.

What I learned

• Responsiveness is criticalEven a small delay can make shooting feel sluggish. Immediate input and hit registration make the experience feel precise and satisfying.
• Feedback drives satisfactionSound and visual reactions reinforce successful actions. Each hit needs a clear, immediate confirmation.
• Simple mechanics can be powerfulOne well-executed idea can be more effective than many underdeveloped features. Testing helped me trust the focused scope.
• Rapid iteration saves timeTrying variations and discarding what does not work kept development moving within the short timeframe.
• Build the core before polishingKeeping visuals minimal let me focus on shooting first, then add polish to support an already solid mechanic.