1. Add the resource
Place the resource folder in your server resources and ensure it after any required framework or dependency resources.
Install
Resource setup.
Add this page's exact install steps as the packaged release changes. Keep framework notes and required dependencies visible.
2. Configure API access
Add your YouTube API key and any proxy or server-side lookup settings required by your release.
3. Set permissions
Choose who can use vehicle music, boombox playback, playlists, admin tools, and any restricted features.
4. Test in game
Open the NUI, search for a song, play it nearby, enter and leave a vehicle, and confirm audio follows the expected zone.
Features
What customers should know.
These notes explain the gameplay behavior customers usually ask about first.
Tunes can connect playback when a player enters a vehicle and disconnect when they leave, keeping music behavior natural.
Players can use localized audio so nearby people hear the same track without server-wide music spam.
Document your framework checks here, including standalone, ESX, QBCore, vRP, and custom permission wiring.
Add notes for connecting your own permanent ID script, including where to return or fetch the player identifier.