pebble_airdrops · v1.0.0

Installation

Requirements

Resource Notes
ox_lib Required.
oxmysql Required. The tables are created on first start.
pebble_bridge 1.2 or newer Required. Ships as its own open resource. Detects your framework, inventory, target, notifications and dispatch.
An inventory One of the inventories pebble_bridge supports.
pebble_looting Optional. Turns each drop type's loot into a template that staff edit in /lootadmin.

Supported frameworks: QBCore, Qbox, ESX, or no framework at all (standalone).

Install

  1. Download pebble_airdrops from your Cfx.re portal and put it in your resources folder together with pebble_bridge.
  2. Add them to server.cfg after your framework, inventory and target, in this order:
ensure oxmysql
ensure ox_lib
ensure pebble_bridge
ensure pebble_looting      # optional
ensure pebble_airdrops
  1. Give your staff access to the admin panel and commands (see Permissions).
  2. Restart the server. On the first start pebble_airdrops creates its tables and seeds the drop zones from Config.Locations and a first drop type from ServerConfig.Loot and ServerConfig.Hack.
  3. Join, run /airdropadmin and check the Drop zones and Drop types tabs. Start a test drop from the Live tab or with /airdrop start.

pebble_bridge picks your framework, inventory and other resources automatically. If you run more than one of a kind, or want to force one, set its convar. See pebble_bridge.

Permissions

The admin panel and the /airdrop command are allowed for players with the pebble_airdrops.admin ace, or a framework group listed in ServerConfig.AdminGroups (admin, god and superadmin by default). Every admin request is checked on the server again.

To use the ace, add it in server.cfg:

add_ace group.admin pebble_airdrops.admin allow

Database

pebble_airdrops keeps its data in four tables: pebble_airdrops_zones, pebble_airdrops_types, pebble_airdrops_settings and pebble_airdrops_audit. A versioned migration runner creates and updates them when the resource starts; you don't import any SQL by hand.

Updating

Replace the resource folder with the new version and keep your edited config/ and locales/ files. Migrations for the new version run on the next start, and your zones, drop types and settings stay in the database.