R.E.P.O.R.E.P.O.wiki
Community reference picture of Feather Drone from the R.E.P.O. Fandom wiki.
Community picture from R.E.P.O. Fandom Wiki, CC-BY-SA-4.0 (license), by Dimasic5838. It has been re-encoded for this page. It is not a screenshot taken by this site.

Gear and items · R.E.P.O. v0.4.0 · read from a local copy

The drone

The drone is an item with behaviour of its own.

R.E.P.O. ships a drone the crew can deploy: it carries its own list of things to aim at, covering valuables, players, enemies and ordinary objects, and runs itself from state to state.

What the game establishes

In play

The drone is an item in its own right. It has behaviour and states of its own rather than being a reskinned tool, which is why deploying one is a decision rather than a throw.

It knows what it is looking for. The game gives the drone separate targeting for valuables, players, enemies and ordinary objects, which is why one can be pointed at a kind of thing and not another.

It draws its own line. The drone keeps a line between two points, which is how it shows what it is working on instead of leaving you to guess.

It runs on a battery. The drone carries a battery drain setting along with a slippery material of its own, so it works for a while and then stops rather than going forever.

It has a sound for every step. Starting, ending, deploying, retracting and its idle loop each have their own sound, so the drone tells you where it is in its routine.

The list of sounds is wider than the routine. It also names a beam loop, so the noise of a drone working is kept apart from the noises of it being moved about.

It can be aimed at a player. Because players are on the targeting list, a drone is not only a tool for the loot, which is why the crew should agree before one goes out.

What this entry does not tell you: how long a battery lasts, what a drone costs, or what it can carry. We have not verified those numbers, so we do not print them.

Related

Version and sources

A local copy of the game, read only. Identifiers are listed on the technical reference pages; nothing here is estimated. Documented build: 0.4.0.