Activities Pack Documentation
This guide explains how to install and configure Activities Pack for your FiveM server.
Compatibility
- ESX Legacy
- QBCore
- Framework inventory
- ox_inventory
- qs-inventory
Requirements
- ESX Legacy or QBCore
- Framework resource
- ox_lib recommended
- ox_target or qb-target optional
- qb-menu optional for QBCore menu support
- ox_inventory or qs-inventory optional for inventory support
- OneSync recommended for server-side entity spawning
Installation
- Download the resource from your Tebex purchases.
- Extract the folder.
- Place the tdev_activities folder inside your server resources folder.
- Start your framework before the resource.
- Start optional dependencies before the resource if you use them.
- Open the config.lua file.
- Select your framework or leave it on auto detection.
- Configure your target system.
- Configure your menu system.
- Configure your inventory system.
- Configure activity peds, blips, and enabled activities.
- Configure boat cruise destinations and routes.
- Configure skydiving destinations and parachute settings.
- Configure jet ski, dirt bike, Formula1, and horse riding courses.
- Configure prices, payment accounts, lobby limits, and rewards.
- Add the resource to your server.cfg.
- Restart your server or run refresh followed by ensure tdev_activities.
- Test solo activities, group lobbies, payments, checkpoints, and rewards.
Server CFG Example
ESX Example:
ensure oxmysql
ensure es_extended
ensure ox_lib
ensure ox_target
ensure tdev_activities
QBCore Example:
ensure qb-core
ensure ox_lib
ensure qb-target
ensure tdev_activities
Configuration
- Set Config.Framework to auto, esx, or qb.
- Set Config.Target to auto, ox_target, qb-target, or none.
- Set Config.Inventory to auto, framework, ox_inventory, or qs-inventory.
- Set Config.Menu to nui, ox_lib, qb-menu, or ESX menu support.
- Replace html/nobackground.png if you want to use your own menu logo.
- Configure Config.ActivityPeds for each activity location.
- Use enabledActivities to control which activities are available at each ped.
- Configure Config.BoatCruise.destinations for boat routes.
- Configure Config.Skydiving.destinations for plane spawn, jump, and landing locations.
- Configure Config.JetSki.destinations for jet ski courses.
- Configure Config.DirtBike.destinations for dirt bike sessions.
- Configure Config.Formula1.destinations for Formula1 sessions.
- Configure Config.HorseRiding.destinations for horse riding sessions.
- Set Config.DirtBike.model, Config.Formula1.model, and Config.HorseRiding.model.
- Use Fullhorse or Rangehorse for the included horse models.
- Configure Config.Payment for prices, accounts, and charge timing.
- Use money for ESX cash, cash for QBCore cash, and bank for bank payments.
- Configure Config.LobbyLimits for each activity.
- Use 0 for unlimited lobbies.
- Configure Config.BoatCruise.rewards for server-side boat rewards.
- Keep payment and reward logic server-side.
- Do not edit encrypted files.
Activities Included
- Boat Cruise
- Skydiving
- Jet Ski Courses
- Dirt Bike Sessions
- Formula1 Sessions
- Horse Riding
Group System
- Players can start activities alone.
- Players can create group lobbies.
- Lobby members must press Ready before the activity starts.
- The activity starts automatically when every lobby member is ready.
- Every member must be able to pay if payment is enabled.
- Sessions, payments, ready states, and rewards are handled server-side.
Security
- Do not move payment logic client-side.
- Do not move item reward logic client-side.
- Do not trust client-sent prices, items, accounts, coordinates, lobbies, ready states, or payment states.
- Keep destination coordinates, route points, prices, and rewards inside config.lua.
- Keep server-side destination validation enabled on production servers.
- Keep server-side ped validation enabled on production servers.
- Use Config.Webhook for activity logs and exploit logs.
Anticheat Whitelist
If your anticheat blocks custom resource events, whitelist the TDev Activities events from the README.
Important server events include createLobby, joinLobby, leaveLobby, setReady, requestStart, startAlone, cancelActivity, finishActivity, and the activity entity ready events.
Important client events include openMenu, updateLobby, startBoatCruise, startSkydiving, startJetSki, startRideActivity, endActivity, notify, and the activity entity ready events.
Common Issues
No third-eye option appears: Check Config.Target, target resource ensure order, and confirm the activity ped spawned.
Menu does not open: Check Config.Menu, optional menu dependencies, or use the built-in NUI menu.
Group activity does not start: Make sure every lobby member pressed Ready and every member can pay.
Payments do not work: Check Config.Payment, account names, and framework money settings.
Boat rewards do not appear: Check that the reward item names exist in your inventory system.
Skydiving does not put everyone in the plane: Lower Config.Skydiving.maxPlayersPerPlane or adjust the skydiving lobby limit.
Custom parachute does not show: Check the streamed .ydr name, enabled setting, replaceNativeParachute setting, parachute model, and pack model.
Jet ski checkpoints do not appear: Check that the course has checkpoints and that the player is inside an active jet ski session.
Dirt bike, Formula1, or horse checkpoints do not appear: Check that the destination has checkpoints and that the player is inside an active ride session.
Horse does not spawn: Check that peds.meta is loaded in fxmanifest.lua and that Config.HorseRiding.model is set to Fullhorse or Rangehorse.
Server-side spawning fails: Check that OneSync is enabled and that the configured vehicle or ped models are valid.
Support
If you need help, open a support ticket in the Tdev Scripts Discord.
Provide your order ID, script name, framework, inventory, full F8 error, server console error, and a screenshot or video.
Support is only available for verified customers.
Support is not provided for leaked, resold, or heavily modified versions.
Discord: https://discord.gg/5MYzXemM4q
Back to home
