Aiming Without Breaking Stealth: A Shadow Strike Design Case Study

From 2D to 3D

From a 2D UOC Prototype to a 3D Stealth Game

Shadow Strike began as a small 2D stealth game designed and developed for a programming assignment during my game development studies at the UOC.

The original version already contained the core fantasy of the project: infiltrating hostile spaces, avoiding enemies, interacting with doors, and using shadows as the main way to stay hidden. Enemy detection was not purely binary. Whether the player was detected depended on factors such as distance, line of sight and how much light was hitting the character.

The game also included night vision, which allowed the player to see in dark areas but became a disadvantage in brightly lit spaces. This created a simple but interesting relationship between light, visibility and player vulnerability.

When I started reimagining the project in 3D, I wanted to preserve that original identity. The new version still uses an angled top-down perspective for exploration, keeping the tactical readability of the 2D prototype, but it also uses the third dimension to create new navigation and interaction possibilities.

For example, vents can exist below the floor and become alternative infiltration routes. Lights and lamps can be placed on ceilings, not just walls or props at character height. This made the world feel more believable and opened new design opportunities.

But it also created a new problem.

Comparison between the original 2D Shadow Strike prototype and its current 3D version.

The Design Challenge

In the 2D prototype, aiming and interacting with the environment was straightforward because every relevant element existed on the same visual plane. Once the game moved into 3D, that was no longer true.

The player can use a weapon for two very different purposes:

To stun enemies and temporarily remove threats.
To destroy lights, create distractions or generate new areas of shadow.

This is central to the game's identity. Shooting is not meant to turn Shadow Strike into an action game. It is a tactical tool used to manipulate the space.

The problem appeared when different targets could share the same position on screen while existing at different heights in the 3D world. For example, an enemy could walk directly below a ceiling lamp. From an angled top-down camera, both the enemy and the lamp could appear almost aligned, even though one target was on the floor and the other was above the player.

In that situation, what is the player aiming at?

The enemy?
The ceiling lamp?
Something behind them?

A purely top-down aiming system could make that decision unclear. In a stealth game, that kind of ambiguity is dangerous. A missed or unintended shot is not just a small control issue: it can break the player's plan, alert enemies and make the game feel unfair.

Diagram showing an enemy and a ceiling lamp overlapping from the player's perspective.

Rejected Paths

Why the Obvious Solutions Did Not Work

Before settling on the final solution, I considered several possible approaches.

Option 1: Target Priority System

One solution was to use an automatic priority system. For example, if two targets overlapped, the game could always prioritize the highest object, or always prioritize the enemy before the light.

This solved the technical ambiguity, but it created a design problem: the game would be making tactical decisions for the player.

In Shadow Strike, choosing whether to stun an enemy or destroy a light is part of the strategy. If the system decides which target matters most, the player loses control over one of the most important decisions in the game.

Option 2: Removing Ceiling Targets

Another option was to avoid the problem entirely by removing ceiling lights and other overhead devices.

This would have made aiming simpler, but it would also have reduced the value of moving the project into 3D. Ceiling lights are useful for level design because they allow the environment to feel more believable and give the player more ways to manipulate visibility.

Removing them would have made the spaces less interesting and less flexible.

Option 3: UI Target Selector

I also considered a UI-based target selector. If multiple objects were under the reticle, the player could cycle through them before shooting.

On paper, this gives the player full control. In practice, it would be slow and uncomfortable.

Imagine trying to shoot a lamp at the exact moment an enemy walks underneath it, or deciding quickly whether to stun the enemy instead. Having to scroll through a target list would interrupt the flow of the moment and make the interaction feel more like menu navigation than stealth gameplay.

Option 4: Full First-Person Camera

A first-person camera would solve aiming precision almost immediately. However, it would also change the identity of the game.

Shadow Strike relies on the angled top-down camera because it gives the player tactical awareness: enemy positions, patrol routes, light areas, shadow zones and possible paths through the environment.

Turning the whole game into first person would make the player more vulnerable, reduce the strategic overview and push the experience closer to an action game. That was not the fantasy I wanted.

Chosen Solution

The Chosen Solution: Two Cameras for Two Types of Decision

The final solution was to split the experience into two camera modes:

Exploration and infiltration

Angled top-down camera.

Precise aiming

Over-the-shoulder camera.

During normal play, the camera stays in an angled top-down perspective. This gives the player the information needed to move through the level tactically, read patrol patterns, understand light and shadow zones, and plan their route.

When the player aims, by holding right mouse button or the left trigger on a gamepad, the camera transitions briefly into an over-the-shoulder perspective. In this mode, the ceiling becomes visible and the player can clearly see what the character is aiming at from the character's own perspective.

The player can then choose precisely between targets at different heights: a lamp, an enemy, or another shootable object.

Releasing the aim button returns the camera to the angled top-down view.

Animated transition from Shadow Strike's angled top-down view to over-the-shoulder aiming view.

Why It Works

Why This Works

This solution keeps the core identity of Shadow Strike intact.

The angled top-down camera remains the main way to experience the game. It supports planning, stealth readability and tactical movement.

The over-the-shoulder camera only appears when the player needs precision. It does not replace the main perspective; it complements it.

This separation creates a clear UX distinction:

In top-down view, the player reads the situation.
In aiming view, the player commits to a specific tactical action.

That distinction is important because shooting in Shadow Strike is not meant to be the default state of play. It is a deliberate action. The player enters aiming mode, makes a decision, takes the shot or cancels, and returns to broader spatial awareness.

Diagram showing the two-mode flow from exploration to aiming, then shooting or cancelling, and returning to exploration.

Scope Guardrail

Preventing the Game from Becoming a Shooter

One key decision was to prevent the player from moving while aiming.

This may seem restrictive, but it supports the intended experience. If the player could freely move while aiming from an over-the-shoulder camera, the game could easily drift into third-person shooter territory.

That is not what Shadow Strike is about.

By limiting movement during aiming, the game reinforces the idea that shooting is a tactical commitment rather than a default combat stance. The player needs to choose when it is safe to aim, what target matters, and whether the shot is worth the risk.

The player temporarily loses some global awareness while aiming, but this is acceptable because they can instantly return to the angled top-down camera by releasing the aim button. The game is not designed around constant action pressure, so aiming usually happens during planned moments rather than chaotic firefights.

This balance helps maintain the fantasy: the player is not a soldier clearing rooms through direct combat, but an infiltrator using the environment to create opportunities.

Future Feedback

UX Feedback and Future Improvements

The current aiming mode uses a reticle to make the intended target clear. In future iterations, I would like to expand this feedback with contextual information about what will happen when the player shoots.

For example:

A lamp could show that it will be destroyed and generate noise.
An enemy could show that they will be stunned.
A device could show that it will be disabled.

This kind of feedback would help the player make faster decisions without turning the system into automatic targeting. The goal is not to remove decision-making, but to make the consequences of each decision readable.

Design Takeaway

The main lesson from this feature is that moving a mechanic from 2D to 3D is not just a matter of translating the action. It changes how the player perceives space, reads intent, confirms decisions and experiences the fantasy of the game.

In Shadow Strike, the challenge was not simply "how do I let the player aim?"

The real question was:

The final solution respects both needs. It gives the player clear, precise control when shooting, while preserving the tactical overview and slower, more deliberate rhythm of a stealth infiltration game.

For me as a designer, this case study represents the way I like to approach game design problems: define the intended player experience first, identify where the design creates friction, explore multiple solutions, and choose the one that best supports the fantasy of the game rather than blindly following genre conventions.

More Work

View more work and explore the rest of the case study library.

View more work