Changelog

Version 0.0.1 is the first prepared numbered package baseline. No previous public numeric release or migration is assumed. Back up any development installation, custom config/translations, music and sky_dj_state; preserve settings, clubs, devices, playlists and boombox claims. Stop the server for replacement. Install ESX with RunStaticPlayerMethod, OneSync, ox_lib, Sky Base and its configured SQL provider. No Jobs Base or separate sound resource is required. Follow Installation for prerequisites.

Install the complete central ZIP's sky_dj/ at resources/[sky]/sky_dj, with the manifest directly inside it. A standalone drag-and-drop wrapper locates the resource under resources/[sky]/sky_dj. Use all files from the same 0.0.1 package. For a development copy, delete and reinsert source/ completely, replace the matching manifest and public stream/, and refresh all 19 JSON locales while merging custom wording. Merge backed-up values into config/config.lua, config/audio.lua and config/soundboard.lua. Keep generated NUI, Lua and the profiler manifest/helper together.

Customer music, saved data and owner-local stream/tent / stream/speakers models are excluded. The public festival does not include those private models or a nightclub MLO. Preserve music separately and avoid mixing unrelated assets. Standalone documentation and the optional conversion tool stay outside the runtime.

With Config.IngameSettings = true, use /djadmin and the existing SQL settings. Access requires an allowed ESX group or sky.dj.admin ACE permission. Generated defaults seed only missing settings. With false, edit the existing config/config.lua; the saved SQL settings remain intact. Clubs, devices and playlists remain in SQL in either mode. Sky DJ has no /jobconfig section. Follow Configuration, without resetting or importing defaults over saved settings.

Optional diagnostics are disabled by default. Put setr sky_profiler 1 before Sky ensures, restart and start a normal FiveM recording manually. No automatic recording or upload occurs. Disable with setr sky_profiler 0 and another restart. Keep the generated helper and matching manifest installed.

Sky Base creates sky_dj_state and missing rows automatically. Use the SQL permissions documented in Installation. No manual SQL import or data reset is required. Preserve all existing rows and boombox claims.

Supply MP3s under config/music/ or configure a separate music resource as documented. Standard playback needs no Python or FFmpeg runtime. Optional HTTPS/Opus streaming is disabled by default and requires the complete Installation setup. Default /boombox placement requires no item. Before enabling item mode, install the configured sky_boombox catalog entry using the Boombox guide; retain existing claims. The supplied public stream/ is required; private tents/speakers and customer music are not included. Shared YouTube and personal Spotify playback are different workflows.

Start the SQL provider and ESX before ox_lib, sky_base, an optional separate music resource and finally sky_dj. Restart the server and fully reconnect clients after native map replacements. Check startup logs, authorized /djadmin access, MP3 mixing, playlists, saved settings, club controls, optional boombox item handling and public assets actually delivered. Confirm existing SQL data remains. Do not start the previous club system alongside Sky DJ.

These checks require a connected FiveM client and the actual ESX/inventory setup. Source tests, ZIP hashes and disk copies do not prove gameplay, a performance result, customer delivery or encrypted Escrow acceptance.