155 online 3 members  + Join RP Base  +
FreeScriptQBCore

mrfrost-processing

by MrFrostDev  ·  version 2026.07.30  ·  updated 3 days ago

No reviews yet

Downloads
0
Reviews
0
Size
84 KB
Code check
Clean
Licence
GPL-3.0
Released
Nov 2026

Item processing at world locations for QBCore, with a recipe template. Archived, unmaintained.

mrfrost-processing
mrfrost-processing
A QBCore item-processing resource for FiveM. Players walk up to a marked spot,
pick a recipe from a menu, sit through a progressbar, and their raw materials
are swapped for the finished item. Each processing spot is a small standalone
Lua file, so recipes can be added without touching the resource's own code.

Published as-is and no longer actively maintained — issues and PRs may not get a response.
Background
These scripts were written for a private GTA V roleplay server and ran there in
production. They are published here so the work stays available rather than
sitting on a disk, and so anyone who finds them useful can build on them.

Because they were built for one specific server rather than for general release,
they expect other resources that are not included here. You will
need to supply these yourself, or adapt the code around them:

  • qb-core
  • qb-target
  • qb-menu
  • ps-inventory
Requirements
Verified against fxmanifest.lua and the calls made in the source:

Dependency, Used for

qb-core, GetCoreObject, QBCore.Functions.GetPlayerData, GetPlayer, Notify, Progressbar, QBCore.Player.GetTotalWeight, QBCore.Shared.Items, and the shared locale.lua loaded by the manifest
qb-target, AddBoxZone — the only way to interact with a spot
qb-menu, openMenu — the recipe list
ps-inventory, HasItem, GetItemAmount, GetMaxWeight, AddItem, RemoveItem, and the inventory:client:ItemBox / inventory:client:UpdatePlayerInventory events

The inventory export names are hardcoded, so another inventory resource will not
work without editing the source. lua54 is enabled in the manifest.

Every item used by a recipe — both the product and each required material —
must already exist in qb-core/shared/items.lua, with a label and a weight;
the resource reads both and does not guard against a missing entry.
Installation
  1. Copy the mrfrost-processing folder into your server's resources/ directory.
  2. Add ensure mrfrost-processing to your server.cfg, after qb-core,
qb-target, qb-menu and ps-inventory. The manifest declares no
dependencies, so the load order is not enforced for you.
  1. Make sure the items your recipes use are defined in qb-core/shared/items.lua
and have images in ps-inventory. No SQL is required.
  1. Review shared/template.lua. It is loaded by the same shared/*.lua glob as
the real spots, so out of the box it registers a working "meat" spot at the
coordinates written in that file. Delete it or move it out of shared/ if
you do not want that spot on your map.

The resource also ships two example spots that form a chain: chicken to
plucked_chicken, then plucked_chicken to chicken_breast. Their labels and
progressbar text are German, as are the de locale strings.
Configuration
shared/config.lua holds only two globals. Everything else — locations, blips,
recipes, role restrictions — lives in one file per processing spot in the same
folder, each of which registers itself into Config.ProcessingSpots.

Key, Type, Default, Description

Config.ShowPolyDebug, boolean, false, Passed to qb-target as debugPoly; outlines every zone in the world. Read once at startup.
Config.ProcessingSpots, table, {}, Registry of spots, keyed by spotName. Filled by the spot files, not edited by hand.

Per-spot keys, set in a spot file:

Key, Type, Description

label / icon, string, Text and Font Awesome icon on the qb-target option and the menu header
blip, table, Optional. Omit the whole table for a spot with no map marker.
spots, array, One or more box zones; a spot can have several interaction points
items, table, The recipes. The key of each entry is the item produced.

See docs/configuration.md for every key with its type
and defaults, and docs/recipes.md for a walkthrough of adding
a new spot or recipe.
Events
The resource registers no exports and no commands. It has two net events, both
of them internal — they are the client-to-server hop of one processing action,
not an integration surface.

Event, Registered on, Arguments, Purpose

mrfrost-processing:client:processItem, Client, data table with spot, item, itemData, Fired by the qb-menu entry. Checks job/gang and materials, then starts the progressbar.
mrfrost-processing:server:giveItem, Server, item (string), itemData (table), Fired when the progressbar completes. Removes the materials and hands over the product.

Note that mrfrost-processing:server:giveItem takes the recipe table from the
client rather than looking it up in the config — see
docs/known-issues.md.
Documentation
Page, Contents

docs/configuration.md, Every config key, its type, default and effect
docs/recipes.md, Adding a new processing spot or a new recipe to an existing one
docs/localisation.md, Locale keys, and the differences between en and de
docs/known-issues.md, What turned up while reading the code
Licence
GPL-3.0