SkyWatch Recon

What it is

Overwatch for search-and-rescue, perimeter watch, and events — every flight audited, every deployment rate-limited, and no weapon path by design, so it stays an infrastructure tool rather than an arms race. Designed to hand sightings off to the CaseLink record. For owners who want eyes in the sky with receipts on the ground. Designed for Qbox, QBCore, and ESX Legacy through ForgeCore. Escrow split publishes at release. In development; no runtime proof published — pending Shadow bench.

The problem it exists for

A drone on an RP server is either banned or broken: banned because the last one turned into an all-seeing wallhack that ruined every pursuit, or broken because it streams a camera nobody throttled and the server pays for it in frames. The legitimate uses — finding a lost hiker, watching a perimeter, covering an event — get outlawed along with the abuse, because the tool shipped with no rules.

Why we're building it

Recon is an infrastructure problem pretending to be a toy. The difference between a surveillance tool a server can allow and one it has to ban is limits — who can fly, where, for how long, and what record it leaves — so we're building the limits first and the camera second. Eyes in the sky is the easy part; eyes in the sky that a pursuit, an event team, and an admin can all live with is the actual product.

What it's designed to do

Design intent, not shipped behaviour — none of this has been built yet.

• Designed as a logged tool: every flight has an operator, a duration, and a record someone can pull afterward.
• Designed with hard limits — throttled use, bounded range, explicitly non-combat — because the version without limits gets banned within a week.
• Designed for the jobs that justify it: search-and-rescue sweeps, perimeter watch on a locked-down scene, overwatch for event staff.
• Designed so what the drone saw can matter afterward, feeding scene awareness into the same law-and-order records the rest of our stack shares.

What is not proven

The section every product page should have and almost none do.

• In development and not purchasable — authored in the studio repo, with no runtime proof published pending the Shadow bench.
• No resmon figure — [MEASURED-PENDING]. A streamed camera is one of the easiest ways to spend frames in FiveM, which makes the unmeasured number the most important thing on this page.
• $34.99 is a planned target, not a commitment until the studio pricing lock.
• No release date.

What we're building toward

A crisp drone-cam sweep gliding over a locked-down scene, tagging targets.

Current status, stated exactly

• resmon [measured-pending]
• escrow manifest — at release
• framework support — decided at build, published at release
• open-vs-escrowed manifest — published at release, file by file

What to verify before buying any law & order resource

This applies to every product in this category, ours included, whenever it arrives. Hold SkyWatch Recon to exactly these when it launches — and if it fails one of them, don't buy it.

• Ask what the drone costs while flying, not while parked — a live camera feed is where the frame budget goes (see /guides/fivem-resmon-script-performance).
• Ask what stops it from becoming a wallhack: range limits, altitude limits, flight logs, and who can read them. A recon tool with no audit trail is a cheat with a propeller.
• Ask whether flight permissions are enforced server-side, not by hiding the controller in a menu (see /guides/fivem-server-security-net-events).
• Our July 2026 survey recorded two drone prices, $14.99 and $46.99 — a thin sample with a threefold spread, which usually means the listings aren't selling the same kind of product. Read what's included before comparing numbers (see /guides/fivem-script-prices).

Universally: ask for the measured resmon figure with its method and date, the exact list of which files ship open versus escrowed, a dated changelog, and the refund window. Four answers. Any of them missing is an answer too.