sm_smelterdelivery by SamuelTV combines ore collection, smelting, component crafting and customer deliveries. The reviewed manifest declares version 1.0.0 and imports ESX directly. It also uses ox_inventory, ox_target and ox_lib; it is not a standalone or QBCore resource.
Prepare the resource and inventory items
Use the sm_smelterdelivery folder containing fxmanifest.lua. Start compatible ESX and ox resources before ensure sm_smelterdelivery. Merge iron_ore, iron, steel_ore, steel and component into your inventory item definitions without overwriting existing items. The supplied steel_ore label incorrectly says Component; correct the display label while retaining its key.
The installation file gives conflicting image directories, web/build/images and web/build/img. Use the image directory and item-image setting of your installed ox_inventory version; do not create both paths blindly. Back up inventory configuration and test that each of the five supplied item images loads.
Understand recipes and customer jobs
Collection is configured in code to grant 3 iron_ore or 2 steel_ore. Smelting consumes 3 iron_ore for 1 iron, or 2 steel_ore for 1 steel. Crafting consumes 2 iron and 1 steel for 1 component. Client progress takes 10 seconds for collection and 6.5 seconds for smelting or crafting; those progress bars do not enforce server cooldowns.
Config.MoneyPerComponent defaults to 1400 in-game money per component. Easy customers request 1–3 components, Medium 3–8 and Hard 8–12, with configured client timers of 8, 5 and 3 minutes. Customer availability is shared across players. The hourly reset clears active deliveries as well as refreshing customers; it is not persistent job storage.
Resolve API and transaction problems before opening
The server repeatedly obtains exports.ox_inventory:Inventory() and calls methods on that result. Check this against the documented exports of your installed version rather than assuming compatibility. The two collection callbacks also omit the source argument documented by ox_lib and read the global source instead. Correct the callback identity and inventory integration before testing rewards.
The server records delivery ownership and rejects completed or foreign deliveries, but stores no destination or deadline for its completion checks. Collection and crafting also lack server distance and progress validation. Add authoritative location, timing and single-active-job checks; a client timer or target zone is not server authorization.
Inventory removals and additions are not checked for success, and delivery completion is marked only after waits following the reward. Reserve completion before yielding and make consumption and payment recoverable. The client clears its job without a successful server acknowledgement. Test full inventories, insufficient materials, repeated completion, timeouts, hourly reset and reconnects before using a live economy.
Reviewed on 10 September 2026 at revision 5fa8179ecaa18aecbacbb11234b6fc1812b9d1ec. All supplied Lua, manifest and installation instructions were read and official ox API documentation checked. No FiveM resource, crafting operation or payout was executed.
Read the pinned Smelter Delivery source