Pixelshifting System

Category: Drone-Specific Perception and Collectable Logic
Context: Pixelshifting was a drone-specific visibility mechanic in Data Division. The core idea was that certain objects existed in a tainted or alternate-state form that the player could not properly perceive through the main human view, but could detect through the drone.

What The Mechanic Was

When the player controlled the drone, they could view pixelshifted objects through the drone’s vision.

These objects were framed as things tainted from other realities or alternate states. In practical gameplay terms, they served as:

hidden objects the player could only meaningfully detect with the drone
future collectable hooks
a modifier-driven layer for venue variation

So the system was not large, but it was structurally useful. It gave the drone a perception role beyond simple scouting.

Core Visibility Rule

The implementation intent was simple:

a pixelshifted object uses a pixelated / altered shader
it is hidden from the player’s main camera
it becomes visible when the player is using the drone view

That means the mechanic is not only about art style. It is about viewpoint-gated information.

The player does not just “see a weird object.” They need the correct platform to perceive it at all.

Drone Interaction

The intended interaction path was:

The player switches to the drone.
The drone view reveals pixelshifted objects.
The player scans or identifies the object.
At later drone levels, the drone can actively pick up the item instead of only revealing it.

That progression mattered because it turned the mechanic into more than a binary hidden-object gimmick. The drone was supposed to move from:

perceiving
to identifying
to interacting

Relationship To Collectables

The system was also meant to support planned collectables.

The original design note tied pixelshifted objects to:

future collectable spawns
level-data-driven spawn chance modifiers
special items from alternate timelines or contaminated states

So while the standalone mechanic is simple, it plugs into the broader level architecture. The useful design connection is:

That is why it belongs in the portfolio archive. It is not just a shader trick. It is a drone-gated perception system that was intended to feed future collectable and venue-variation logic.

Why This System Mattered

Pixelshifting is small, but it does three useful things:

gives the drone a unique perception affordance
creates viewpoint-dependent world state
supports later collectable and progression hooks

That is enough to make it worth documenting as a real mechanic, even if it was not one of the heaviest systems in the prototype.