Overview

Target Shooter is a fast-paced aim training game developed within a one-week timeframe. The goal was to create a simple but satisfying shooting experience by focusing on responsiveness, feedback, and core gameplay feel rather than complex systems. Instead of adding many features, I prioritized the fundamentals that make shooting enjoyable. The design centers on instant input response, clear hit feedback, and consistent pacing. By keeping scope small, I delivered a polished, functional experience within the time limit.

Features

Shooting Responsiveness

The shooting system is built around instant feedback. When a player clicks, the shot registers immediately using a raycast. This removes any delay and ensures the game feels fast, precise, and responsive. Targets react instantly when hit, reinforcing the connection between input and outcome. This direct interaction is essential for satisfying gameplay.

Feedback & Clarity

Clear feedback was a major focus to enhance the experience. A distinct hit sound confirms successful shots, targets disappear instantly on impact, and visual clarity ensures players can easily track and hit targets. Even though these elements are simple, they significantly improve how rewarding the game feels. Moving targets provide more challenge and engagement than static ones, adding variety while keeping the core mechanic unchanged.

Reference-Based Design

The project was inspired by aim trainers like Kovaak's FPS Aim Trainer, particularly its focus on responsiveness and feedback. Key elements taken include instant shooting without delay, clear audio feedback on hit, and minimal, readable target design. These fundamentals were used as a base and expanded with improved visual presentation.

Development

Reverse Engineering the Core Mechanic

I began by recreating a simple shooting system to understand how it works. A raycast was used to detect hits instantly, matching the responsiveness of aim trainers. Basic feedback was then added, such as hit sounds and target reactions. Even at this stage, the gameplay already felt close to the intended result, showing how important core mechanics are.

Rapid Prototyping & Iteration

Due to the short timeframe, I focused on quickly testing ideas rather than detailed planning. Simple prototypes were created for:
Target spawning
Movement behavior
Shooting interactions

If something didn’t feel right, it was immediately adjusted or removed. This allowed me to focus only on features that improved gameplay. Small variables like fire rate, spawn timing, and target speed were tweaked multiple times to achieve a balanced and satisfying experience.

Focus on Core Over Complexity

Visuals were kept minimal during early development so I could prioritize gameplay feel. Once the shooting mechanics felt solid, I refined the presentation. This approach ensured that time was spent on what mattered most. Instead of building complex systems, I focused on making a simple mechanic feel as good as possible.

Key Learnings

Responsiveness is critical.
Even a few frames of input delay makes shooting feel sluggish and unsatisfying. Removing delay entirely transforms the experience from frustrating to satisfying.

Feedback drives satisfaction.
Sound and visual reaction combine to reinforce successful actions. Each hit needs immediate audio and visual confirmation.

Simple mechanics can be powerful.
I initially worried the core mechanic was too basic, but testing showed that one solid idea executed well beats ten mediocre features.

Rapid iteration saves time.
Testing ideas quickly and discarding what doesn't work keeps momentum. Spending days perfecting something that doesn't feel good is wasted effort. Getting multiple iterations done in hours is far more valuable.

Core gameplay first, visuals second.
I kept visuals minimal during development to focus on shooting feel. Once the mechanic felt solid, polish was easy to add to make a fun and satisfying experience.