Browse docs

Installation

Install Sky Activities, configure its dependencies and permissions, and verify the included venues.

Requirements

RequirementPurpose
sky_baseFramework, inventory, account and database integration
sky_jobs_baseShared initialization, player information and placement tools
oxmysqlPersistent settings, activity definitions and kart records
OneSyncServer-side entities and separate match sessions

Use compatible versions of both Sky dependencies and configure Sky Base to use oxmysql as its SQL provider. Keep your framework, inventory and any required map dependencies running before the resources that use them.

Install

Place the resource

Copy the folder containing fxmanifest.lua to your server's resources directory and keep its name sky_activities. Include source/html, stream, data, config, shared and the other shipped files.

The release includes the UI, sport weapons and Sky maps. If you build from the source repository, build its frontend first and deploy the inner resource folder with the resulting source/html. The former separate sky_activity_weapons resource is obsolete; remove its start entry when upgrading from that arrangement.

Prepare the database

Connect oxmysql to your database. Startup migrations create the Activities tables; import.sql is the manual schema reference. The database account needs the permissions required by those migrations and normal reads/writes.

Back up sky_activities_definitions, sky_activities_settings, sky_activities_kart_profiles and sky_activities_kart_payments before updates. They hold saved locations, operator settings, kart choices and payment records.

Start the resources

Enable OneSync and use this order after your framework and inventory:

server.cfg
ensure oxmysql
ensure sky_base
ensure sky_jobs_base
# Start optional map resources and their dependencies here.
ensure sky_activities

The Sky maps are already part of sky_activities; they need no separate map resource. Third-party bowling maps must be installed separately. See Bowling MLOs for exact resource names and conflicting-map instructions.

Set startup options and permissions

Check config/config.lua. The default language is de; choose en for English. The default administrator groups are admin and superadmin. The editor also accepts the ACE permission:

server.cfg
add_ace group.admin sky.activities.admin allow

This grants the permission to the named group; use your server's existing administrator assignments. Reserve routing buckets 62000–62255 for Activities, or change Config.BucketStart and Config.BucketCount to an unused range.

Configure anticheat permissions

Apply the Anticheat & resource protection instructions before testing. Activities creates equipment, temporary sport weapons, local player clones and race karts, and uses scripted cameras and movement.

First verification

With standard activity installation enabled, visit the Activity Center at 1024.1989, -2399.1038, 30.1206. Open a sport at its television or interaction marker. Open /activitiesconfig as an administrator and check the supplied activities, rules and activation state.

Join a game, leave with /leaveactivity, and confirm the player's controls and previous location are restored. Try a private solo test, then a game with another player. Check both the server console and client F8 log if models, menus or interactions fail.

InstallVenuePresets installs missing standard activities on resource startup. Turning it off prevents that installation step; manage already saved activities in the editor. See Configuration before changing this setting.