Integration Guide
Guidelines for wiring Pursuit Scripts into existing economy, jobs, and progression systems.
Framework Compatibility
- Qbox, QBCore, and ESX are supported through auto-detection.
- Ensure only one framework is active to avoid callback collisions.
Dependency Hooks
Use these hooks as your baseline integration points:
-- Inventory
exports.ox_inventory:AddItem(source, itemName, amount)
-- Notifications
exports.ox_lib:notify({ title = 'Pursuit', description = 'Action complete' })
-- Logging
PerformHttpRequest(webhookUrl, function() end, 'POST', payload, {
['Content-Type'] = 'application/json'
})
Recommended Integration Pattern
- Map your item names and reward tables first.
- Wire server-side validation before client UI polish.
- Add Discord webhooks after gameplay is stable.
- Benchmark performance in a populated test server.
Cross-Script Synergy
| Pairing | Why It Works |
|---|---|
| prp-shops + prp-storerobbery | Creates risk-versus-reward loops around active stores. |
| prp-trashhunt + prp-zombies | Noise and scavenging escalate combat pressure naturally. |
| prp-pawn + prp-trashhunt | Scavenged goods become meaningful economy sinks. |
Tip: Keep reward logic and anti-exploit checks server-side only. Treat client events as request intents, not authority.