AWSAWS DOCUMENTATION38 source-matched resource guides
Documentation/Vehicles/AWS CarSound V2
Vehicles3 min readUpdated 2026-10-15
AWS CarSound V2 cover

AWS CarSound V2

A vehicle sound workshop with configurable sound lists, favorites, rev previews and persistent plate-based installations.

Installation

Requirements

  • oxmysql
  • OneSync
  • One supported core: QBCore, Qbox or ESX

Startup order

This example selects one framework and target. Use the resources matching your configuration and start dependencies first.

ensure oxmysql
ensure qb-core
ensure aws-carsounds-v2

Setup steps

  1. Install V2 instead of running it alongside CarSound V1; their public commands and event names overlap.
  2. Back up the vehicle database. Config.Database.SoundTable defaults to aws_vehicle_sounds and is initialized by the server.
  3. Review Config.Database.UseLegacyVehicleColumn and AutoCreateSoundColumn before startup. They can read or alter the framework vehicle table.

Gameplay and usage

  1. Open the workshop menu in a vehicle or use /carsound as authorized staff.
  2. Preview a sound, install it, then test favorites and the configured reset-to-stock action. W/Shift rev preview is controlled by Config.Features.

Configuration

  • config.lua: Config.Framework selects auto, qb, qbox or esx.
  • Config.Database defines vehicle tables, plate and owner columns, and sound storage.
  • Config.Features controls favorites, sorting, installed badges, reset, rev preview and staff free installations.
  • Config.Security controls vehicle requirements, ownership enforcement, price limits and event cooldowns.
  • Config.Locations, Config.Sounds and Config.Admin define the workshops, library, prices and /carsound access.

Exports and integrations

No public callable export is declared with exports() in these source files. Use the documented commands or configuration; internal network events are not a trusted integration API.

Troubleshooting

  • If saved sounds do not return, inspect the configured plate column and dedicated sound table.

  • If a purchase is rejected, check ownership rules, active vehicle, sound key and configured price cap.

  • Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.

Package reference

Manifest Version
fxmanifest.lua 3.1.5

Database files

No standalone SQL file is included. Check the installation steps above for tables created by server code.

Configuration reference

  • aws-carsounds-v2/config.lua: HeaderTitle, Currency, DefaultPrice, MoneyType, RequireJob, Framework, Admin, Database, Security, Debug, SoundApplication, Features, Blips, Logs, Blacklist, Interaction, Marker, Locations

Frequently asked questions

Does this need Keymaster or an escrow key?

The Lua sources in this delivery package were readable in the static audit. No /assetpacks requirement is added by this package. Required framework, inventory and map resources still need to be installed separately.

Can I change the folder or database table names?

Keep the supplied folder names. Historical event, SQL and KVP identifiers are retained to protect existing integrations and saved data. Renaming a table or event requires a separate migration.

Why is an interface or item missing?

Check the startup order, selected framework/target adapter, inventory item definitions and the server/F8 console. The package does not install an entire framework or inventory for you.

Has this been tested on my server?

ZIP integrity, source readability, script syntax and manifest references were checked locally. Multiplayer gameplay, your framework version and integrations require a FiveM server acceptance test before a public release.