Skip to main content
There isn’t one. Since version 3 every setting lives in your database and is edited from the in-game admin panel: use /chopadmin in-game (it requires the lation_chopshop.admin ACE permission from the install guide). Changes save as you edit and sync to connected players; the few settings that need a restart are marked in the panel. If you want a copy of your settings, use Export in the panel to get a single JSON artifact, and Import to load it on another server.
Add the ACE permission to your server.cfg (or permissions.cfg on Qbox):
Then perform a full server restart. Make sure the identifier you play with is actually in group.admin; if you use a different group, replace group.admin with it.
  • Player data carries over. Levels, XP and lifetime vehicle and part stats are migrated automatically on first start.
  • Your v2 config files do not. Re-enter your settings in /chopadmin. Defaults are seeded so nothing is required before the resource works.
  • The v2 items are no longer used. ls_auto_parts, ls_torch, ls_lug_wrench and ls_vehicle_finder are replaced by the impact drill, the car jack, the chop contract and seven salvaged part items. Add the new items from the install folder; you can remove the old ones from your inventory whenever you like.
  • Groups, phone messages and the vehicle finder are gone. Jobs are now timed contracts for a vehicle class, any matching vehicle counts, and anyone standing at a chop vehicle can help without forming a group.
A contract asks for a vehicle class (compacts, sedans, SUVs and so on), not a model. The vehicle the player targets must be in the class printed on their contract. Which classes can be issued at all is set in /chopadmin under Contracts → Allowed Vehicle Classes, and each tier picks its classes from that list. If a tier ends up with no usable classes the panel marks it and it will never be issued.
By default players can chop anywhere. Open /chopadmin, go to Locations, turn on Restrict chop locations, set the Chop radius, and add coordinates. The Use current position button captures where you are standing. Each location can also show a map blip and its radius as a zone on the map, configured in the same tab.
The broker blip is under Start → Blip. Chop location blips are under Locations → Location Blips. Both have an enable switch plus sprite, color, scale and label, and update live.Chop location blips have two extra switches. Show chop zone draws the chop radius on the map as a shaded area rather than only a pin, and Contract holders only limits them to players actually carrying a contract. They also only appear while Restrict chop locations is on, since with restrictions off there is no area to point at.
The paper is only a key to the contract; the contract itself is stored on the server and survives a relog and a server restart. Have the player talk to the broker and choose View Contract: if the paper is missing, a replacement copy is printed and the case file opens. Someone else using a found paper sees an invalid contract and the paper is discarded.
Yes, and there is nothing to set up. Once the contract holder starts the chop, anyone standing at the vehicle with a car jack or an impact drill can place stands and remove parts. Each part pays whoever removed it; the on-time bonus goes to the contract holder.
Both hook files ship open under escrow. On the client, lua/client/utils/hooks.lua has Hooks.StartedChopping(entity, model), which runs when a chop starts. On the server, lua/server/utils/hooks.lua has Hooks.VehiclePartRemoved(source, entity, model, typeId, boneId), which runs after every part reward. Add your code inside those functions. The full list is on the exports pages.
Everything is tunable in /chopadmin under Minigame: the lug nut hold time and drill audio for wheels, the bolt count and hold time for doors, and the torque, connector and tap settings used in the engine bay. The car jack and impact drill can be made optional, and the drill’s break chance is set under Items.
Sorry about that! Please reach out to us on Discord or via email at support@lationscripts.com regarding your issue.
When working with, testing, or tweaking this resource; do not restart the script! To properly restart this resource you first must stop lation_chopshop then ensure lation_chopshop. Failure to do so can cause issues, errors, and unexpected behavior.