OpsLab Books
Realplay Scripts /Introduction
Help Sign in Sign up
rps_smallresources

Introduction

RPS Small Resources is a modular collection of lightweight, performance-focused FiveM resources designed to provide useful roleplay, quality-of-life, and server utility features while remaining easy to configure, maintain, and integrate into existing FiveM servers.

The main goal of RPS Small Resources is to provide multiple useful features without forcing server owners to completely change their existing framework, inventory, notification, target, fuel, dispatch, radial, door-lock, or gang systems.

Instead, RPS Small Resources is designed to work together with the RPS Lib (rps_lib) advanced bridge system, which acts as the central integration layer between the individual resources and the systems installed on your server.


What Is RPS Small Resources?

RPS Small Resources is a collection of independent FiveM resources that can be used individually or together.

The package is designed around the idea that small gameplay features should not require large, complicated dependencies or extensive framework-specific modifications.

Depending on the resources included in your installation, RPS Small Resources can provide features such as:

  • Player interaction systems
  • Hands-up functionality
  • Kneeling functionality
  • Carry systems
  • Crosshair controls
  • Map and ESC menu customisation
  • Vehicle radio controls
  • Roleplay utility features
  • Target interactions
  • Framework job checks
  • Inventory interactions
  • Notifications
  • Fuel integration
  • Dispatch integration
  • Radial menu integration
  • Door-lock integration
  • Gang integration
  • Server-side transaction handling
  • Permission checks
  • Developer integration APIs

Each feature is designed to perform a specific task while remaining compatible with the larger RPS ecosystem.


RPS Lib Integration

One of the most important components of the RPS ecosystem is rps_lib.

rps_lib provides a central bridge system that allows RPS resources to communicate with different FiveM frameworks and third-party resources without requiring every individual script to contain separate integrations.

Instead of writing:

```lua local QBCore = exports['qb-core']:GetCoreObject()

local Player = QBCore.Functions.GetPlayer(source)

if Player.PlayerData.job.name == 'police' then -- Police functionality end