Status
SteamPeaks
ChartsSalesUpcomingPatchesNewsCalculator
New on SteamEvery app, DLC and depot the minute Steam creates itAppsEvery app on Steam, newest change firstPackagesSubs and bundles, and what each containsDepotsDepots, manifests and install sizesTagsSteam's user tags and the games under themDevelopers & publishersCompanies and their cataloguesTechnologiesEngines, SDKs and anti-cheat found in the filesChange historyEvery PICS changelist as it lands
SignalsNineteen readings of the whole catalogueCompareAny games side by sideRecordsAll-time peaks and the days they were setReportsWeekly and monthly write-upsAlerts & newsroomWatch a game, get told when it movesSteam statusIs Steam up, right nowWeb API explorerTry the endpoints in the browser
NewsSteam's own announcements and the sales calendarCalculatorWhat a Steam account is worth, and its pile of shame
/
Sign in
/
SteamPeaks
The ultimate resource for Steam data.
ExploreChartsSalesSales and festsUpcomingPatchesNewsRecordsTrendingSignals
DatabaseAppsPackagesDepotsTagsDevelopersTechnologiesChange history
ToolsCalculatorCompareSearchAlertsSteam statusAPI
SiteMethodologyFAQDiscordSupportSign in via Steam
Not affiliated with Valve or Steam. Game names and artwork belong to their owners. All times UTC.
PrivacyCookiesFair useStatus
Droning On DemoNewsDevlog: You're Being Watched
Community

Devlog: You're Being Watched

Droning On Demo · published 25 Jul 2026, 19:00 UTC

All newsPlayers around this dateRead on Steam

A Droning On level used to be a quiet place. Walls, hazards, a grid, and Gizmo, who doesn't move until your code tells him to. Good for concentrating. Bad for atmosphere, and worse for the thing I was after, which is the sense that your maze isn't sitting in a vacuum. It's a test. Something built it, something is watching how you do, and you are not the only robot in the building. So I added drones, two kinds of them, to make the world feel alive and a little like you're under a microscope, without dragging your eye off the tiles you're counting.

The Observers

The first kind are observers. They fly the maze and watch Gizmo work, tracking him as he moves and hovering like they're taking notes on the run. They don't help and they don't interfere. They watch. That's the whole job, and the job is a feeling: you're not solving a puzzle alone in an empty room, you're solving it in front of something that carries itself like it's grading you.

The Haulers

The second kind are haulers, and they're the ones I'm fond of. Haulers carry the world around. Walls, obstructions, the other drones, and Gizmos. The observers make you feel watched; the haulers make the watching feel like part of an operation. Things in the world don't just exist, they get lifted and carried into place by machines that were plainly doing this long before you showed up. And when a hauler drifts past carrying a Gizmo that isn't yours, the implication writes itself: you're one run among many, and whatever this place is, it doesn't stop when you log off.

Keeping Them From Stealing Focus

There's a tension here I had to respect. The puzzle is a focus task. You're reading code and counting tiles, and the eye snaps to motion, so anything moving in the scene is a tax on attention. Ambient sparkle would be easy to dial down to nothing. Drones that track your robot and haul walls across your view are not ambient, and pretending they were would have been a cop-out. The honest goal was getting them to register when you look up and vanish when you don't. They're there to color the world, not to compete with it.

Why It Matters

None of this changes how you solve anything. Same code, same mazes, same robot doing exactly what you told him. What changes is everything around the solving. You glance up from a script and the world is busy: something is tracking Gizmo, something is hauling a wall into position, and somewhere a drone is carrying off a robot that was running a different maze than yours. The grid stops reading like an abstract exercise and starts reading like a test chamber, with you as the current subject. If you've played a certain first-person puzzle game about a polite, watchful laboratory, that's the exact nerve I'm reaching for. It cost the gameplay nothing and gave the world a pulse. I'll take that trade.


Thanks for reading. As always, your feedback is welcome. If you haven't already, drop a wishlist and come hang out in the Discord. It's the best place to share feedback, follow development, and engage.

More from Droning On Demo

Other announcements

All news
Community5 Sep 2026Devlog: Skip AheadBootcamp is twenty levels long, and it's the front door to everything else in Droning On. Puzzle Mode is behind it. Endurance Mode is behind it. So are the feature unlocks — collections, interactables, hazard detection, functions, classes — which the game hands you one chapter at a time as you earn them. That's the right structure for someone learning to code. It is a wall for someone who alrea…Community22 Aug 2026Devlog: Bring Your Own EditorDroning On ships with a code editor. It has syntax highlighting, error underlines, a console, a run/stop button, and it is a perfectly good place to write a solution. It is also, if you are the kind of person who has opinions about editors like me, somebody else's editor. We developers, are fickle. So the scripts aren't locked inside it. They're plain .py files sitting in a folder on your disk,…Community8 Aug 2026Devlog: Puzzle ModeBootcamp teaches you the language one idea at a time. Endurance Mode drops you on a virtual treadmill and speeds it up until you fall off. Puzzle Mode is the thing in the middle, and it's the part of Droning On I've spent the most time actually designing levels. Each level is built around a single idea, each one waiting to see what you do with it. Thirteen Hand-Built Problems Every one of the t…