1Evolve Development’s garbage job spawns a trash truck and collection bags, then pays for recorded disposal events. The reviewed manifest declares version 1.0.0. This resource needs additional checks before use on a public economy server; client-side animations alone do not prove that a payable collection happened.
Correct folder and dependencies
The repository contains the actual resource inside 1evolve-garbagejob. Move that inner folder into resources and start it with ensure 1evolve-garbagejob, not start Garbage-Job. Its manifest declares es_extended, ox_inventory, ox_target and ox_lib, including the ESX imports file. Start those dependencies first even though the earlier guide listed only ESX and ox_target.
Use config.lua for Config.posizioniRaccolta, Config.npc, Config.Scritte and Config.Soldi. The checked defaults have two active collection positions and a payment multiplier of 50 per recorded bag. That value is in-game economy configuration, not a purchase price. The truck spawn and return waypoint are hardcoded separately from Config.npc.
Collection and repeated shifts
The route selects and removes positions from a table that directly references Config.posizioniRaccolta. Starting another shift reuses that same depleted table instead of making a fresh copy. Test a complete second shift and correct the route reset before promising varied repeatable work.
The pickup handler loops over the first stored bag rather than using the targeted entity. Collection targets are added with addLocalEntity but removed with removeGlobalObject. The vendor options use addGlobalPed rather than being restricted to the spawned vendor. Review target scope and cleanup so interactions stay on the intended objects and NPC.
Payment and lifecycle checks
The server increments a per-player disposal count when a network event arrives, without validating an active shift, bag, truck, proximity or rate. Selling multiplies that count by Config.Soldi, resets it and pays cash, but does not check vendor proximity. Add authoritative shift and collection validation before enabling rewards for public players.
No truck-capacity limit, disconnect cleanup for the server count or resource-stop cleanup is implemented in the inspected files. Test cancelled shifts, disconnect/reconnect, repeated starts, prop removal and payment after a valid route. Do not describe a full-truck requirement or clean restart behavior as an existing feature.
Source checked on 10 September 2026 at revision 9eeaac32ba0b11cbc682a457b34ca25fad8cac3e. Manifest, configuration, client and server were read in full. No FiveM collection, payment or multiplayer test was performed.