srp-core

Detects your framework and inventory on startup, then exposes one consistent API to every other SRP resource. Install it once and forget about it.

v1.2.0Free

Download Source

Frameworks

ESX
Standalone

Inventories

ox_inventory

Installation

Download the resource

Grab the latest release from GitHub and extract it into resources/[srp]/.

Add it to server.cfg

srp-core has to start before any resource that depends on it.


ensure ox_lib
ensure srp-core

Restart

Check the console on startup — srp-core prints which framework and inventory it detected.

Configuration

Bridges are configured entirely through convars in server.cfg. You should not need to edit any file inside the resource.

Convars

srp-core:bridge.targetstringdefault: 'ox'

Targeting bridge. Accepts ox.

srp-core:bridge.notifystringdefault: 'ox'

Notification bridge. Accepts ox or esx.


setr srp-core:bridge.target "ox"
setr srp-core:bridge.notify "esx"

Use setr, not set. Bridges are resolved on both the client and the server, and a non-replicated convar is invisible to the client — the bridge will silently fall back to its default there while working correctly on the server.

An unrecognised value logs a warning and falls back to the default rather than erroring, so a typo in server.cfg will not stop the resource from starting. Check the console on boot if a bridge is not behaving as configured.

Omit a convar entirely to use its default. There is no reason to set one to the value it already has.

Debugging

To see which bridge was resolved for each kind at boot:


setr srp-core:debug.srp-core true

See Debug gating for narrowing this to a single scope.

config.lua exists for development of the resource itself — it declares which bridge implementations are available to be selected. Editing it is not a supported way to configure your server, and your changes will be overwritten on update. Use the convars above.