LRSCRIPTSLRSCRIPTSPREMIUM FIVEM RESOURCES
Home/Documentation

Documentation

Install clean.
Configure with confidence.

A permanent path from purchase to a working resource—without relying on lost chat messages or undocumented assumptions.

Purchase & delivery

Use purchase links from LRSCRIPTS.com or the official LRSCRIPTS Tebex store. Each product page states its current release status, requirements, build notes, and supported delivery path.

Released product pages and their linked guides are the current source of truth. In-development resources remain clearly marked until their release build and documentation are locked.

Standard installation flow

Product guides include their exact steps, but the supported FiveM release flow remains predictable:

1. Obtain the resource from the official delivery path
2. Place it in your server resources folder
3. Review configuration before the first start
4. Install only documented dependencies
5. Add ensure resource_name in the correct load order
6. Restart or refresh the affected resources
7. Check startup logs and test the main workflow

Do not rename a protected resource unless its release notes explicitly permit it.

Configuration

Editable configuration remains separated from protected implementation code where practical. Product guides identify framework selection, integration toggles, optional modules, permissions, and any required server configuration.

Updating safely

Read the changelog first. Back up edited configuration and database changes, compare the new config against the live one, and avoid blindly overwriting server-specific values.

LRS Navigation is a free standalone FiveM GPS script with flowing 3D road guidance, turn-by-turn voice instructions, street-name support, ETA, distance tracking and a customizable navigation HUD. It requires no framework, database, inventory, target or additional dependency.

Installation

1. Download or claim LRS Navigation through the official LRSCRIPTS Tebex package
2. Place lrs_navigation inside the server resources directory
3. Add ensure lrs_navigation to server.cfg
4. Restart the resource or server
5. Set a normal GTA waypoint and begin driving
ensure lrs_navigation

Commands

/lrsnav         Open navigation settings
/lrsnavmode     Open route settings
/lrsnavcycle    Cycle navigation route modes
/lrsnavrepeat   Repeat the current voice instruction
/lrsnavrefresh  Force a route refresh
/lrsnavdebug    Display navigation diagnostics

Route modes

  • Chevrons: flowing road guidance.
  • Line: a continuous racing-style navigation line.
  • Hybrid: combines route guidance styles.
  • HUD Only: disables world route effects while retaining navigation HUD guidance.

Dependencies

None. LRS Navigation runs standalone and does not require QBCore, ESX, SQL or any framework dependency.

LRS Navigation product page

LRS Test Drive · v1.4.4

LRS Test Drive is a free standalone-first FiveM Test Drive system with an in-game location builder, searchable vehicle catalogs, timed sessions, GPS-guided returns and optional refundable deposits. It requires no framework, database, inventory or target resource. QBCore, Qbox, ESX and a custom bridge are optional integrations.

Installation

1. Obtain lrs_test_drive through the official LRSCRIPTS Tebex package
2. Place lrs_test_drive in your server resources folder
3. Review config.lua and the included locales
4. Configure standalone or an optional framework/custom bridge
5. Add the builder ACE permission for authorized administrators
6. Add ensure lrs_test_drive to server.cfg
7. Restart the resource or server and review startup logs
8. Use /testdrivebuilder to create and test a location

No SQL import is required. OneSync is recommended for synchronized sessions and reliable temporary-vehicle cleanup.

Builder ACE

add_ace group.admin lrscripts.testdrive.builder allow

Only trusted administrators should receive this permission.

Commands

/testdrive         Open the nearest configured Test Drive location
/testdrivebuilder  Open the authorized in-game location builder
/returntestdrive   Route or return the active Test Drive vehicle
/endtestdrive      End the active Test Drive session

Builder workflow

  1. Open /testdrivebuilder.
  2. Choose to create a Test Drive Location.
  3. Enter its label.
  4. Enter a unique location key.
  5. Select the Test Drive Attendant model.
  6. Select an attendant scenario.
  7. Ghost-place the Test Drive Attendant.
  8. Ghost-place the Vehicle Spawn.
  9. Ghost-place the Return Zone.
  10. Configure the map blip and interaction distance.
  11. Choose the vehicle catalog and session rules.
  12. Review deposits, timers and GPS behavior.
  13. Save; the location becomes available in real time without a restart.

Placement controls: E confirms, Backspace cancels, the mouse wheel rotates by 15°, and Shift plus mouse wheel rotates by 3° for fine adjustment.

Attendant selection and scenarios

Select a supported ped model and scenario for each Test Drive Attendant. The builder previews the ped as a ghost before saving, so position and heading can be checked in-world.

Vehicle Spawn, Return Zone and blip

Each Test Drive Location stores its attendant, Vehicle Spawn, Return Zone, interaction range and optional map blip. Saved changes update in real time. GPS can guide the driver back to the Return Zone, where the temporary vehicle is cleaned up and an eligible deposit is refunded.

Framework and bridge options

  • Standalone: complete core gameplay with no framework requirement.
  • QBCore and Qbox: optional player, vehicle-catalog and economy integrations.
  • ESX: optional player and economy integration; this does not claim a native QBCore-style shared vehicle table.
  • Custom bridge: customer-configurable callbacks for supported server-specific integrations.

Vehicle catalogs and images

Configure framework catalogs where supported, standalone vehicle lists, extra custom or addon models, categories, exclusions, allowed vehicle types, local image overrides and supported image providers. Players can search by name, brand, model or spawn name and filter by category.

Deposits, timers and GPS

Deposits are optional and require a configured economy integration. A valid return can refund the deposit; expiration, disconnects and invalid sessions are handled through server-authoritative cleanup. Drive duration, return grace period, GPS routing and deposit values are configurable.

Notification priority

  1. LRS Notify, when installed and configured.
  2. ox_lib, when available.
  3. Qbox, QBCore or ESX framework notifications.
  4. Config.CustomBridge.Notify.
  5. Native FiveM notification fallback.

LRS Notify is optional, not a required dependency.

Accessibility

The interface provides KINDA BLIND and SUPER BLIND accessibility modes. Both are disabled by default for the normal presentation and may be enabled by players who need increased readability.

Configuration

Review location defaults, framework mode, custom bridge callbacks, vehicle catalogs, extra vehicles, excluded models and categories, image providers, deposits, timers, GPS, blips, interaction distance, notifications, accessibility, ped models, scenarios and locale selection in the documented customer-editable files.

Safe updating and runtime data

Preserve your existing dealers.json. This runtime file contains saved Test Drive Locations. Do not delete it or overwrite it during an update. The v1.4.4 package intentionally does not ship an empty replacement; the server creates the file after the first successful builder save.

Before updating, stop the resource and back up dealers.json, config.lua, locales and custom bridge changes. Replace release files, restore or merge customer configuration, keep the runtime data file in place, restart and test one saved location. Older installations that stored runtime data at data/dealers.json should preserve that file and follow the documented migration path into the current root-level runtime file before removing the legacy copy.

Troubleshooting

  • Confirm the folder is named lrs_test_drive and starts successfully.
  • Verify lrscripts.testdrive.builder is granted before testing the builder.
  • Confirm every location key is unique and placement was saved.
  • Check that the selected vehicle model exists and is not excluded.
  • For deposits, verify the selected economy integration and account mapping.
  • Confirm the Return Zone and GPS settings match the saved location.
  • Capture the first relevant server-console or client F8 error before requesting support.

LRS Test Drive product page

LRS Notifications · v1.1.0

LRS Notifications is a standalone FiveM notification system. Normal notification use does not require a framework. Optional routing can auto-detect QBCore, Qbox or ESX, while optional QBCore and ESX notification-event compatibility listeners are disabled by default to avoid duplicate interfaces.

Installation

1. Obtain LRS Notifications from the official LRSCRIPTS delivery path
2. Place lrs_notify in your server resources folder
3. Review config.lua
4. Add ensure lrs_notify to server.cfg
5. Restart the resource or server
6. Test your integrations

Basic client notification

exports['lrs_notify']:Notify({
    type = 'success',
    title = 'VEHICLE',
    message = 'Your vehicle has been repaired.',
    duration = 4500
})

Player settings

When enabled by the server owner, players can open /lrsnotifysettings. The server controls which preferences may be changed, including position, sound volume, UI scale, animation, theme and layout.

LRS Style Studio

Administrators with the configured ACE permission can open /lrsnotifystudio for live local previews and presentation-value output. The studio does not rewrite server files.

Routing

Server exports support all-player, job, jobs, gang, gangs, nearby-player and ACE-group audiences. Routing can run standalone or use QBCore, Qbox or ESX player data when configured.

Compatibility note

Enable only the optional compatibility adapter that is intentionally replacing an existing notification path. Leaving unnecessary adapters disabled helps prevent duplicate notifications.

LRS Notifications product page

LRS Bounce · v1.5.30

LRS Bounce is a synchronized vehicle Show Mode and True RGB lighting system for FiveM. It is standalone and framework agnostic; optional framework detection is used only when a server chooses job or group access.

Installation

1. Obtain LRS Bounce from the official LRSCRIPTS delivery path
2. Place lrs_bounce in your server resources folder
3. Review config.lua
4. Start any optional framework or lrs_notify before LRS Bounce
5. Add the lrs.bounce.admin ACE permission
6. Add ensure lrs_bounce to server.cfg
7. Restart the resource or server
8. Use /bounceadmin to configure server-wide settings

Commands

/bounce       Enable or disable Show Mode
/bounceStyle  Cycle or change the current bounce style
/bouncePanel  Focus or unfocus the player control panel
/bounceadmin  Open the server administration panel

Admin ACE

add_ace group.admin lrs.bounce.admin allow
# Optional for servers that use a god group
add_ace group.god lrs.bounce.admin allow

A framework admin or god role does not automatically grant this ACE unless the server maps the permission.

Access modes

Choose Everyone, ACE, framework job/group, ACE or Job, or a customer-defined custom integration. Optional access detection supports QBCore, Qbox/QBX, ESX Legacy, ox_core and ND Core; none of those frameworks are required or included.

Vehicle policies

Universal permits configured Show Mode use across vehicles. Blacklist excludes listed vehicles. Allowlist limits Show Mode to explicitly listed vehicles.

Show Mode Kit

Servers can run with no kit requirement or require an installed Show Mode Kit. The customer-editable integration bridge can connect that requirement to mechanic, dealership or garage gameplay.

Optional lrs_notify integration

Start lrs_notify before LRS Bounce when using the optional integration. If it is absent, LRS Bounce uses its built-in notification fallback.

Basic RGB configuration

Server owners can configure RGB defaults, linked or independently supported lighting, neon zones, effects and effect speed. Players can use HEX or RGB input and live preview where permitted by server configuration.

Per-vehicle overrides

Use intended configuration fields to define overrides for addon vehicles with unusual mass, suspension, wheelbase or handling characteristics. Do not copy or publish protected internal calibration values.

Troubleshooting

  • Confirm lrs_bounce starts after any optional framework and lrs_notify integration.
  • Verify the vehicle policy, player access mode and optional kit requirement.
  • Confirm lrs.bounce.admin is mapped before testing /bounceadmin.
  • Test the vehicle below the configured Show Mode speed limit.
  • For addon vehicles, review only documented per-vehicle override settings.
  • Capture the first relevant server-console or client F8 error before requesting support.

LRS Bounce product page

Troubleshooting checklist

  • Confirm the required framework and dependencies start before the resource.
  • Capture the first real server-console or client F8 error.
  • Verify resource names and configuration values against the guide.
  • Temporarily disable scripts that control the same UI, zone, job, or event.
  • For LRS Notifications, check whether an older notification resource or compatibility listener is also active.
  • Include resource, framework, and dependency versions when requesting support.