Content Builder

What the Builder creates

The Content Builder is a loopback-only local browser application. It copies selected files into local projects, validates them, and downloads ZIPs for manual review and installation; it never edits a live FiveM server.

• The Builder does not install Node.js, transcode or master audio, prove media rights, edit a live resource, merge arbitrary Lua semantically, install ZIPs, or replace multiplayer testing.
• Its local HTTP routes and CommonJS exports are implementation/test internals, not a supported SDK.
• Keep the Builder outside the FXServer resources tree and never add it to server.cfg.
• A Build button validates the current project and creates a content ZIP; it does not compile the Builder software.

Install Node.js and start locally

node --version
npm --version
cd "/full/path/to/San Andreas Sound Suite Content Builder"
npm install --omit=dev
npm start

npm start
npm test
npm start -- --port 5000

Workbench, autosave, and local projects

San Andreas Sound Suite Content Builder/
  data/
    projects/<project UUID>/
      project.json
      uploads/
    exports/
    imports/

Build a Dispatch resource

1. Choose Dispatch, enter resource identity and rights information, then add independent channels.
2. Complete player-facing metadata, timing, vehicle hints, and the separate scanner profile ID for each channel.
3. Add real MP3 clips and wait for browser duration measurement and server signature validation.
4. Audition every complete call in a trusted local player; the preview is visual and does not play recordings.
5. Remove privacy-sensitive or inappropriate content, then reconfirm the current channel's privacy review after every media change.
6. Resolve all Project Health and deeper export errors, then use BUILD RESOURCE ZIP.
7. Inspect RADIO_INTEGRATION.lua, BUILD_AUDIT.md, media rights notice, README, and portable project metadata before installation.

Build a Server Radio station pack

1. Choose Server Radio, set the stable resource name, anchor, seed, author, and private rights record.
2. Add stations with unique uppercase IDs and complete display metadata.
3. Add authorized artwork, music, and optional identifiers; correct inferred artist/title values and verify measured durations.
4. Use the main and mini previews to review presentation. The preview does not prove FiveM playback.
5. Resolve missing tracks, invalid IDs, duplicate IDs, missing duration, file role, token, and rights-confirmation errors.
6. Build and inspect the complete resource ZIP before deployment.

Build a Suite Setup configuration bundle

Suite Setup creates complete config.lua replacements for selected resources plus reports and a start-order example. It is not another FiveM resource and does not include Station Pack media.

1. Select New or Existing Installation and a starting preset.
2. Enter the exact installed resource folders and select only components that exist.
3. Keep advanced controls at defaults until a measured test or component guide justifies a change.
4. Resolve dependency conflicts: Sound when Radio selects it, Dispatch for local calls, Radio for Server Radio, and Radio/scanners for the voice bridge.
5. Review enabled behavior, deduplicated start order, every generated file, and integration warnings in the deployment plan.
6. Confirm backups and line-by-line review, then build the configuration ZIP.

Validation and import limits

Output contents and safe deployment

Config.ScannerProfiles = Config.ScannerProfiles or {}
for _, profile in ipairs(GeneratedScannerProfiles) do
    Config.ScannerProfiles[#Config.ScannerProfiles + 1] = profile
end

Config.EmergencyScanner = Config.ScannerProfiles[1]

1. Back up Radio config, server.cfg, current component configs, and the downloaded ZIP; deploy first to a development server.
2. Read every generated README, install report, configuration summary, source report, audit, integration snippet, rights notice, and warning.
3. For Suite Setup, replace only the matching config.lua after line-by-line comparison; do not copy or ensure the bundle root and do not modify manifests.
4. Merge relevant ensure lines into the real server.cfg and preserve provider/catalog-before-Radio order.
5. Test generated Dispatch in an eligible vehicle with two clients, its public metadata, offsets, and restart behavior.
6. Test generated Station Packs for catalog, artwork, metadata, two-client offsets, boundaries, exterior volume, and restart reconstruction.
7. Keep recoverable backups until all component and multiplayer tests pass.

Import and revise projects

Local security, privacy, and rights

• The server binds to 127.0.0.1, uses a per-process request token, applies restrictive browser headers, rejects unsafe static paths, and validates archive paths.
• Do not expose or forward the Builder port, bind it publicly, or run the Builder as administrator.
• Uploads are working copies; the Builder does not modify original source files. Keep independent backups because local data can still be lost.
• BUILD_AUDIT.md may contain original filenames, hashes, private provenance notes, media roles, durations, and privacy-review status. Keep a private compliance copy and remove sensitive audit details from a public distribution copy when appropriate.
• A checkbox records the operator's declaration; it does not establish copyright ownership, redistribution rights, consent, privacy compliance, stream terms, availability, or attribution completion.
• Listen to every scanner clip and keep public metadata lore-friendly. A file that passes structural validation can still fail in a specific FiveM CEF, so test the chosen codec on representative clients.

Verification, maintenance, and troubleshooting

npm test