Changelog

1. Back up and check the game build

Download and extract Sky Activities 1.1.3. These instructions update 1.1.2 to 1.1.3.

Back up the installed sky_activities resource, your customized configuration and translations, edited textures and map exclusions. Back up the game database, including sky_activities_definitions, sky_activities_settings, sky_activities_kart_profiles and sky_activities_kart_payments. Keep saved locations, operator settings, kart profiles and payment/refund records. Finish active games and stop the whole server before replacing files.

Open server.cfg and find sv_enforceGameBuild. Keep an existing value of 2189 or higher. If the line is missing or its value is lower, add or replace that line before the resource start entries:

sv_enforceGameBuild 2189

Keep a higher build if you already use one. A full server restart and reconnecting players are required; restarting only Activities does not change the content build.

2. Replace the matching files

The ZIP contains sky_activities/ directly. Work inside the installed resource folder containing fxmanifest.lua.

1. Delete the installed source/ folder and insert the complete new source/ folder, including its built interface and matching assets.
2. Replace fxmanifest.lua and INSTALL.md from the same download.
3. Replace shared/sports/definitions.lua with the new file. Keep the other shared/ files and their existing custom rules.
4. Copy both complete new folders, stream/kart_props/ and stream/venues/, into the installed stream/ folder and replace matching files. This installs the matching kart props, track models, collision and placements. Keep the other stream folders, edited signage and existing bowling-map exclusions.
5. Replace all supplied Lua files in config/locales/. Transfer only your custom wording into matching new entries and keep every new translation key.
6. Keep your existing config/config.lua, config/bowling.lua and config/karting_server.lua. Review the two optional setting choices below and change only what applies to your setup; retain your other values and server-only webhook configuration.

3. Keep settings and choose optional features

Keep Config.UseActivitiesConfig unchanged in config/config.lua. With true, saved global settings in SQL remain authoritative; use /activitiesconfig → Operation. With false, global operator values come from the Lua file and saved SQL overrides remain intact. The activity editor and its saved definitions remain available in both modes. Activities has no /jobconfig section.

Optional: retain the old overhead table-tennis camera. The new default is the angled thirdperson view. In editor mode, open /activitiesconfig → Operation → Sports → Table tennis camera, select Top-down and save. Choose Third-person for the new angled view. Existing saved operator choices are retained.

For Lua mode only (Config.UseActivitiesConfig = false), open config/config.lua, find the existing Config.PoolAimAssist line and leave its value unchanged. Immediately after it, add:

Config.PingPongCamera = "thirdperson"

Use "topdown" instead of "thirdperson" if you want the earlier overhead view. Keep only one Config.PingPongCamera assignment. Restart after editing the Lua file.

Optional: enable spectator discovery between networks. Config.VenueScreens.iceServers always comes from config/config.lua, including in editor mode. Find its existing block near the session-bucket settings. Keep a working custom STUN/TURN configuration and its client-safe credentials. If that block is empty or contains only the old commented examples and you use spectator television feeds, replace that empty/example block with:

Config.VenueScreens.iceServers = {
    { urls = "stun:stun.l.google.com:19302" },
}

An intentional empty {} may be kept for local-network-only discovery. STUN does not replace a TURN relay where your network needs one. Keep existing VenueScreens.enabled and VenueScreens.spectatorFeeds choices. Restart after changing connection settings.

4. Preserve data and assets

No manual SQL import, schema migration, new inventory item, inventory image or provider change is required for this patch. Startup initializes missing SQL structures automatically. Do not import defaults over saved records or delete any Activities table.

The changed native kart content is installed by copying the matching stream/kart_props/ and stream/venues/ folders. Keep your other bundled maps, third-party bowling maps, custom textures and documented map exclusions. No separate weapon or Jobs Base resource is introduced.

5. Start and check the result

Keep OneSync enabled. Start your framework and provider dependencies, then oxmysql, your configured sky_base and sky_activities 1.1.3. This patch adds no new Sky Base version minimum. Jobs Base is not required. Keep the existing Activities anticheat permissions and reserved routing-bucket range.

Restart the whole server. Fully exit and relaunch FiveM, then reconnect so the new content build and streamed assets are loaded together. Open /activitiesconfig with an authorized account and confirm that your saved locations and settings remain available.

Start a short kart race and check that the driver and another player see the kart at the same correct ground height. Finish or leave and confirm the player returns with normal controls. Take a billiards shot and confirm the player stands beside the latest shot. Check a table-tennis game with your chosen camera. If you use automatic sports discovery, visit a supported existing air-hockey table and check its interaction and score display.

If you use spectator television feeds, check them with a second connected player on your normal network setup. A selected local test recording takes display priority; it is separate from another player's live feed. Optional recording commands remain in the Commands reference. Keep the backup until your checks pass.