Overview
lsf_company is the standalone Los Santos Freight Co. fleet-asset pack. It streams LSFC texture dictionaries for supported vanilla delivery vehicles and trailers and replaces metadata for seven tractor models so they can attach to additional vanilla trailer types; it contains no gameplay scripts or framework integration.
Requirements
- Platform
- FiveM
- Resource name
- Keep lsf_company
- Framework
- None
- Exclusive assets
- Do not run with the duplicate LSFC assets included in ls_trucking
- Conflict review
- Check other resources for the same YTD names or seven replaced vehicle metadata entries
Installation
- 01
Check the server for another copy of the LSFC assets or resources that stream the same texture dictionaries and tractor metadata entries.
- 02
Copy the repository into the server resources directory as lsf_company.
- 03
Add ensure lsf_company to server.cfg and do not start the duplicate asset copy from ls_trucking alongside it.
- 04
Restart the server and validate the supported liveries and tractor-to-trailer combinations in a development environment.
Configuration
Keep the standalone resource intact
Copy the repository as lsf_company and keep its data and stream directories together. The resource has no framework, inventory, database, script, map, or configurable runtime dependency.
Choose the asset source
Use lsf_company when the server needs the LSFC fleet presentation without the complete ls_trucking job. When ls_trucking already supplies the same assets, leave this standalone resource disabled.
Audit other streamed replacements
Search the active resource tree for matching YTD names and metadata entries before installation. Another vehicle pack that replaces the same vanilla dictionary or tractor entry can take precedence and produce partial, inconsistent, or missing results.
Usage and validation
Verify the streamed liveries
Spawn the supported vanilla delivery vehicles and trailers and inspect their LSFC textures at normal and high detail. Test at least the dictionaries for benson, benson2, burrito2, mule, mule2, pounder, rumpo, tanker, tanker2, trailers2, trailers3, and tvtrailer2 when those models are available.
Verify expanded trailer attachment
Test barracks2, hauler, hauler2, packer, phantom, phantom3, and phantom4 against every additional vanilla trailer type the server intends to use. The pack changes compatibility metadata; it does not provide a job, spawn menu, or coupling workflow.
Package contents
- Runtime scripts
- None
- Framework integration
- None
- Database or inventory
- None
- Map files
- None
- Manifest version
- 1.0.0
Streamed texture dictionaries
The stream directory contains replacement YTD assets for the supported LSFC delivery vehicles and trailers, including high-detail dictionaries where the source model uses them.
Tractor metadata
Seven data subdirectories provide VEHICLE_METADATA_FILE replacements for barracks2, hauler, hauler2, packer, phantom, phantom3, and phantom4.
Differences from ls_trucking
Assets without the freight career
lsf_company extracts the LSFC fleet presentation and vanilla tractor compatibility into a standalone asset resource. It does not include ls_trucking contracts, routes, progression, service systems, commands, UI, or persistence.
Updating
Back up the complete asset set
Back up the active resource before replacing it, compare every YTD and vehicles.meta change, and retest both texture resolution and tractor-to-trailer attachment after an update.
Known limitations
Replacements are global
The pack replaces matching vanilla texture dictionaries and vehicle metadata rather than adding independently named models. Load-order conflicts cannot be isolated per player or job.
No runtime controls
There is no configuration file, command, event, export, or framework permission layer. Enable or disable the resource as one complete server asset pack.
Licensing and provenance
Repository terms need completion
The repository identifies DrSnyder as creator but does not include a license or per-asset provenance notice. Describe it as a public source repository with license not specified, not as open source, until explicit terms are added.
Troubleshooting
A vehicle still shows its original texture
Confirm lsf_company is started, the exact YTD exists under stream, and no later resource replaces the same dictionary. Clear the client cache only after correcting the active resource conflict.
A tractor will not attach to an expected trailer
Confirm the matching vehicles.meta is loaded for that exact tractor, the trailer is one of the intended vanilla types, and another metadata replacement is not overriding the entry.
Textures or metadata change when restart order changes
That indicates duplicate streamed replacements. Keep one authoritative copy of each asset and metadata entry rather than relying on load order to resolve the conflict.
Reference
- Use lsf_company only when the standalone LSFC fleet assets are needed without the full ls_trucking job.
- The repository is public, but no license or texture provenance file is present in the audited snapshot.
- No scripts, commands, events, exports, database migrations, or framework adapters are included.