> For the complete documentation index, see [llms.txt](https://baobab-interactive.gitbook.io/baobab-interactive-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://baobab-interactive.gitbook.io/baobab-interactive-docs/junk-removal-simulator/job-sites-and-editor.md).

# Job sites and editor

## Current deployed locations

The supplied ordinary catalogue contains:

* Small curbside pickup
* Stab City Trailer Cleanout
* Hospital Loading Area Cleanout
* Mechanic Garage Cleanout
* Construction Site Junk Removal

A separate container service supports rentals/exchanges. No machinery site ships enabled. Each authored job has its own XP requirement and rig allowlist. Hospital is available at zero XP. All five accept the Bison, C2HD pickup, C2HD gooseneck, C2HD roll-off and C2HD BP bumper-dump rigs. Optional equipment still requires its resources and compatible APIs.

## Create and deploy a location

`shared/jobs.lua` is authoritative for live jobs. Editor drafts and exports do not publish by themselves.

1. With administrator ACE access, open **Company → Job sites**.
2. Create a location, select the template and rigs, capture customer/parking/junk positions, save and preview.
3. Complete the field check and choose **Prepare checked draft**.
4. Optionally choose **Start test visit**. This is a private, real paid cleanup.
5. Set **Export: enabled** for locations that should be offered.
6. Choose **Export all jobs (.txt)**.
7. Retrieve `data/exports/job_sites.txt` from the server's `junk_removal` folder.
8. Replace the entire `Config.DeployedJobs` assignment between **BEGIN/END EXPORTED EDITOR JOBS** in `shared/jobs.lua`. Keep the markers and definitions above them; do not append a second block.
9. Review, upload and restart between jobs.

Exports include the latest prepared versions and file jobs not represented in the editor. Incomplete drafts and later unprepared edits are excluded. Review exports before deploying because an older editor workspace can replace newer file edits.

## Definition rules

Up to 32 custom file jobs are supported. Use stable unique IDs beginning with a lowercase letter and containing lowercase letters, digits or underscores. Do not use the reserved container-service ID or the `preview_` prefix.

Coordinates are absolute world positions. Each job chooses a template and supplies explicit placements. Junk types and item order must match that template. Exchanges add empty drop-off and full pickup poses; machinery jobs add a machine pose and three debris positions. The editor exports the required fields.

Invalid custom deployment data logs the failing record and leaves only the dedicated container service available until fixed. A Lua syntax error must be fixed before the resource loads.

## Pause, update and migrate

Set `enabled = false` to stop new inquiries while preserving the unchanged definition for compatible saved work. Removing a job or changing its ID, geometry, template or economics can block recovery.

Editor KVP stores drafts/private-test revisions separately. It cannot silently restore removed live deployments. Keep stable IDs and finish affected work before making changes.

For upgrades from 0.25.0 or earlier, former KVP-only locations must be exported in the current format and placed into `Config.DeployedJobs`. Do not delete KVP. Old `Config.JobSitePresets` text is not the new deployment format.