BIOS Drone — Advanced Drone System for FiveM

🚁 BIOS Drone is a complete, server-authoritative drone system for FiveM.
Players deploy a physical persistent unit, control it from a dedicated monitor,
carry equipment, manage its battery and recover it after a failure or crash.
Every drone preserves its unique identity, owner, condition, flight time,
position, battery, loaded ammunition and onboard inventory across reconnects
and server restarts.

⚠️ Required dependencies — read before purchasing

⚠️ The following third-party resources are required and are not included in > the purchase. They must be installed and started before BIOS Drone.

- 🧠 OneSync — required for authoritative networked entities, positions and
ownership.
- 🧩 One supported framework — Qbox (qbx_core), QBCore (qb-core) or ESX
(es_extended).
- 🎒 ox_inventory 2.45.0 or later — required for drone items, controllers,
batteries, onboard storage and service lockers.
- 🛠️ ox_lib — required for interfaces, callbacks, notifications and
animations.
- 🎯 ox_target or an API-compatible community fork — required for physical
drone and locker interactions.
- 🗃️ oxmysql — required for persistent drone records and inventory data.
- ❌ The default ESX inventory is not supported. ESX installations must use
ox_inventory.
- ▶️ Start order: start the selected framework and every dependency first,
then bios_drone_assets, followed by bios_drone.

🚁 Flight and controller experience

- 🎮 Dedicated controller monitor with responsive manual flight, camera
gimbal limits, configurable flight modes, zoom and a clean cinematic view.
- 🛫 Complete ground lifecycle including placement, take-off, landing,
shoulder follow mode, recall, storage and physical recovery.
- 📡 Real signal management with configurable range, delayed signal loss,
recovery hysteresis and an owner-only tracking blip during failsafe flight.
- 🕹️ Visible networked controller with synchronized operator animation,
model-specific sounds, navigation lights and a searchlight.
- 🧱 Volumetric collision protection for manual flight, autonomous tracking
and return navigation against terrain, walls, vehicles and world objects.

🧭 Advanced Return-to-Home navigation

- 🏠 Recorded Home Point at take-off, with the return target configurable
between the Home Point and the current operator position.
- 🧵 Reverse flight-trail return that records the flown route and can retrace
it backwards when a direct climb or straight-line return is unsafe.
- 🌉 Dedicated under-bridge recovery: when the drone is below a bridge or
covered structure, it can follow its recorded path, use road-node escape
routes and search for a reachable edge instead of trying to rise through the
bridge deck.
- 🛣️ Road-aware escape routing keeps the drone below the structure while it
exits an underpass, then resumes the normal return once open air is reached.
- 🏢 Obstacle and roof-aware cruising samples the route, calculates safe
clearance above encountered structures and respects the configured altitude
limit.
- 🧠 Stall detection and route recovery can change navigation strategy when
progress stops, while committed waypoints prevent oscillation between equally
valid escape directions.
- 🚨 Safe fallback behaviour triggers an emergency landing and final GPS
position when the drone cannot complete its return within the configured
safety limits.

🎥 Camera, tracking and situational awareness

- 🎯 ActiveTrack for players, pedestrians and vehicles while normal flight
controls remain available.
- 📍 World-space tracking points for observing a selected location without
locking onto an entity.
- 🌡️ Thermal vision and night vision on supported profiles.
- 🔦 Synchronized searchlight, red/green/white navigation lights and an
anti-collision beacon visible to nearby players.
- 📊 Flight OSD with altitude, signal, battery, integrity, radar, return
state and Home Point information.

🔋 Battery, range and flight safety

- 🔋 Replaceable batteries with persistent charge and separate full/empty
inventory items.
- 🧮 Predictive battery failsafe estimates the energy required to return and
starts RTH before the drone can no longer reach safety.
- 🛬 Critical-charge landing and vertical emergency landing when the battery
is removed, exhausted or the return fails.
- 📍 Private proximity finder and GPS tools help the owner locate a grounded
or unreachable drone without exposing it to other players.
- 🌊 Physical water behaviour allows an unpowered drone to sink and require
underwater recovery instead of teleporting back to the owner.

📦 Onboard storage and payload

- 🎒 Persistent onboard inventory powered by ox_inventory, with capacity
configured independently for every drone profile.
- 🔐 Public or private access selectable for each deployment session.
- ⚖️ Real payload consequences: carried weight can affect flight speed,
battery consumption and the weight of the recovered inventory item.
- 🔫 Profile-specific onboard fire control with server-persisted magazine,
storage-based reloading and configurable ballistic behaviour where enabled.

🛡️ Damage, wear and recovery

- 💥 Weapon, collision and mechanical wear damage with server validation of
accepted damage and persistent integrity.
- 🧰 Repair and diagnostic workflows with configurable items and authorized
service jobs.
- 🧩 Recoverable wrecks preserve the drone identity and support configurable
cleanup instead of silently deleting the unit.
- ♻️ Remote recovery fallback is server validated and reserved for genuinely
stalled or unreachable drones.

🆔 Ownership and persistence

- 🔢 Unique serial numbers identify every physical drone and its paired
controller.
- 👤 Registered ownership and protected transfers prevent duplicated or
mismatched credentials.
- ⏱️ Real airborne flight-hour tracking, persistent condition, last position,
routing bucket and operational state.
- 💾 Automatic database creation and upgrades, with a manual SQL schema also
included for restricted database accounts.

🚓 Service drones and administration

- 🚔 Civilian and law-enforcement profiles with independent models, access,
range, camera capabilities, storage, durability, equipment and tuning.
- 🗄️ Shared job lockers for service-issued drones, validated by the server
and automatically restored after supported inventory restarts.
- 🛠️ Administrative registry with search, filters, GPS, teleport, restore and
permanent deletion actions protected by ACE permissions.
- 🔒 Server-authoritative validation for ownership, inventory, storage,
batteries, damage, repair, administration and persistent entity state.

⚡ Multiplayer scalability

- 📍 Proximity-scoped replication sends live position updates only to nearby
players inside the same routing bucket instead of broadcasting every drone to
the entire server.
- 📶 Distance-aware update frequency reduces network work for far observers
while preserving smoother updates near the drone.
- 🔄 State changes are synchronized only when needed, avoiding repeated
state-bag writes for unchanged lights, battery and operating modes.
- 👥 Shared player-position registry avoids repeating expensive player and
native lookups for every drone update.
- 💤 Demand-driven workers and visuals stop or sleep when no relevant drone
session or persistent entity is active.
- 🗃️ Deduplicated and batched persistence paths avoid database queries per
frame and group bulk maintenance operations.
- 📏 No unsupported capacity claim: real limits depend on server hardware,
player population, active drones and configuration, so production owners can
tune synchronization distances and intervals for their environment.

🌍 Configuration, localization and privacy

- ⚙️ Readable configuration and drone profiles expose permissions, jobs,
controls, flight tuning, return behaviour, batteries, damage, storage and UI.
- 🌐 English and Italian included across HUD, OSD, menus, notifications,
administration and documentation; additional locales can be added without
changing runtime logic.
- 🔔 Framework-aware notification and Text UI adapters support ox_lib, ESX,
QBCore, Qbox and custom providers where configured.
- 🛡️ No telemetry, remote licence checks, automatic updates or external runtime
services are used by the resource.

📦 What the customer receives

- 🔐 bios_drone, delivered through Cfx Asset Escrow.
- 🚁 bios_drone_assets, containing the drone, wreck and controller models,
with supported model formats protected through Cfx Asset Escrow.
- ⚙️ Editable configuration, drone profiles and English/Italian locales.
- 🗃️ SQL schema, ox_inventory item images and item-definition generator.
- 📚 Complete English and Italian installation, configuration, usage and
troubleshooting documentation.
- 🔄 Future package updates through the Cfx/Tebex delivery channel.

Compatibility and requirements

BIOS Drone supports Qbox (qbx_core), QBCore (qb-core) and ESX
(es_extended). One supported framework must start before the resource.

Required resources:

• OneSync;
• ox_inventory 2.45.0 or later;
• ox_lib;
• ox_target or an API-compatible community fork;
• oxmysql.

The default ESX inventory is not supported.

Configuration and privacy

The package is protected through Cfx Asset Escrow, while config.lua, drone
profiles under drones/, and locale files under locales/ remain readable and
editable. Server owners can configure permissions, job access, controls, HUD,
storage, batteries, damage, flight behaviour, return logic and translations.

BIOS Drone performs no telemetry, remote licence checks, automatic updates or
calls to external runtime services. Sensitive operations such as ownership,
inventory access, batteries, damage, persistence, administrative actions and
entity state are validated by the server.

Delivery and installation

The purchase includes the protected bios_drone script resource and the
bios_drone_assets model resource, whose supported YFT and YDR files are also
protected by Cfx Asset Escrow. Install both, start the asset resource first, then
start the script:

BLOCK0

The database tables are created and upgraded automatically through oxmysql. A
manual SQL schema is included for database accounts without CREATE permission.
The documentation also includes the generated ox_inventory item definitions,
item images, commands, controls, permissions, configuration and troubleshooting.

What the customer receives

• bios_drone, delivered as a protected FiveM asset;
• bios_drone_assets, containing the drone, wreck and controller models;
• editable configuration, drone profiles and English/Italian locales;
• SQL schema, ox_inventory item images and item-definition generator;
• English and Italian installation and configuration documentation;
• updates to the purchased resource through the Cfx/Tebex delivery channel.

Support

Use the public support link shown on the package page. Include the server console
startup summary, the output of bios_drone_status, the active framework and
inventory versions, and the steps needed to reproduce the issue.