Custom Car Stickers

Requirements

Dependency	Required	Purpose
oxmysql	✅ Yes	Stores stickers, designs, versions, printed copies, and kiosk placements
OneSync	✅ Yes	Server-side vehicle entities for ownership, persistence, and nearby rendering
Qbox, QBCore, or ESX	For standard installs	Player identity, owned-vehicle checks, jobs, and money
ox_inventory or qb-inventory	For the standard production workflow	Physical printed stickers and scraper items
ox_lib	Optional	Menus, prompts, notifications, and progress UI
ox_target or qb-target	Optional	Target-based workstation and vehicle interactions
qb-menu / qb-input / progressbar	Optional	Alternatives when ox_lib is unavailable

Note

oxmysql is the only hard manifest dependency. Standalone frameworks and unsupported inventories require custom adapter implementations; the standard production workflow still needs a functioning inventory and player identity.

Installation Steps

1. Install the Resource

Download the resource from your Cfx.re Keymaster and place it in your server’s resources directory.

Resource path

resources/[retro]/rs_car_stickers/

Keep the folder name exactly rs_car_stickers. Bundled artwork paths and inventory exports depend on that resource name.

2. Install Inventory Items

Install these three included items:

Item names

vehicle_sticker
sticker_remover
vinyl_sheet

Inventory	Item definitions	Image destination
ox_inventory	install/ox_inventory_items.lua → merge into ox_inventory/data/items.lua	ox_inventory/web/images/
qb-inventory	install/qb_inventory_items.lua → merge into qb-core/shared/items.lua	qb-inventory/html/images/

Copy the three PNG files from install/item_images/ into the appropriate inventory image folder. Merge the supplied item entries rather than replacing the inventory’s existing item table.

Caution

Keep stack = false and consume = 0 for the relevant ox_inventory items. For qb-inventory, keep unique = true for vehicle_sticker and sticker_remover. Printed stickers have individual serial numbers and must not merge into a stack. vinyl_sheet is optional unless you configure it as a printing material.

3. Configure the Resource

Open rs_car_stickers/config.lua and review framework detection, inventory providers, production pricing, and allowed image hosts.

config.lua — key values

Config.Locale = 'en'
Config.Framework = 'auto'
Config.Production.enabled = true

Leave provider detection on auto unless you need to select a specific inventory or target system.

4. Add the Resource to server.cfg

Start rs_car_stickers after the database, framework, inventory, and optional UI dependencies.

server.cfg

# Qbox example
ensure oxmysql
ensure ox_lib
ensure qbx_core
ensure ox_target
ensure ox_inventory
ensure rs_car_stickers

For QBCore, start qb-core, your qb-inventory and target resources before rs_car_stickers. For ESX, start es_extended and the installed inventory/interaction resources first.

5. Set Admin Permissions

server.cfg

add_ace group.admin command.decaladmin allow
add_ace group.admin rs_vehicle_decal.admin.ban allow

command.decaladmin grants access to the admin panel, kiosk placement/calibration, garage diagnostics, and operations review. The separate rs_vehicle_decal.admin.ban ACE permits sticker ban management. Give these only to trusted staff.

6. Place Your First Sticker Kiosk

No physical printer is placed by default. Join the server with administrator permissions and run:

In-game command

/decalkioskplace

Aim at suitable ground, use the mouse wheel to rotate the kiosk, and left-click to confirm. The kiosk is stored in the database and restored after restart.

If the model’s display needs alignment, look at the kiosk and use:

Optional screen calibration

/decalkioskcalibrate

7. Restart and Verify

The resource creates and migrates its own SQL tables automatically when it starts. There is no .sql file to import. Your database account must be able to create and alter tables.

After starting the server, verify the following:

1. The console detects the correct framework and inventory provider.
2. The kiosk appears and opens through target interaction or the available Press E prompt.
3. /stickers opens the design library; design editing and printing work at a workstation.
4. Publishing and printing charge the intended amount and create individual vehicle_sticker items.
5. A directly owned, parked vehicle accepts a printed sticker.
6. Applied stickers remain visible after retrieving the vehicle from the garage.
7. A sticker_remover removes the selected sticker without returning a replacement copy.

Optional Discord Moderation Webhook

Use a server-only convar to send publication and moderation events to your Discord webhook.

server.cfg — optional

set rs_vehicle_decal_webhook "YOUR_DISCORD_WEBHOOK_URL"

Caution

Use set, not setr. Do not place a private webhook URL in the client configuration, NUI assets, or item metadata.

General Installation Guide