> For the complete documentation index, see [llms.txt](https://sl-scritps.gitbook.io/sl-scripts-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-fight-club.md). # SL Fight Club ## SL Fight Club **Code:** FGT-36\ **Resource:** `sl_fight_club`\ **Version:** v0.1.35.92\ **Category:** Activity RP / Fight Club / Event System\ **Status:** Stable Candidate / Testing **Structured tools for serious roleplay servers.** *** ### Overview SL Fight Club is a fight club activity system for FiveM roleplay servers. It allows servers to create controlled fight club zones where players can participate in fights, organize events, sponsor active fights, watch NPC matches and build underground or legal combat roleplay depending on server configuration. The resource supports multiple fight formats, including player vs NPC, player vs player and NPC vs NPC fights. *** ### What is this script for? SL Fight Club is designed to create structured combat roleplay without relying on random street fights. It is useful for: * Fight club events * Underground arenas * Legal boxing gyms * Street tournament RP * Staff-hosted events * Player entertainment businesses * NPC exhibition fights * PvP roleplay with rules * Social activity zones The goal is to make fight scenes feel organized, readable and controlled. *** ### Roleplay Experience SL Fight Club is built around a simple IC idea: ```txt There is a fight organizer. Players approach the organizer. A fight is created. Fighters enter the arena. Spectators can watch and support the fight. The result is recorded. ``` The system is meant to support roleplay around the fight, not only the combat itself. A fight club scene can include: * Fighters * Organizers * Spectators * Sponsors * Staff * Business owners * NPC fighters * Ranking progression * Event storytelling *** ### Player IC Usage Players can interact with SL Fight Club in different roles. Common player roles: ```txt Fighter Spectator Sponsor Event participant NPC fight viewer ``` The player does not need to manage the technical setup. The normal roleplay flow is: ```txt Approach organizer → create/join fight → fight or watch → result is shown ``` Example IC lines: ```txt “I want to sign up for a fight.” “Who is fighting next?” “I’ll support this fighter.” “Let them finish the round.” “That was a clean win.” ``` *** ### Fighter IC Flow #### 1. The fighter approaches the organizer The player goes to the fight club zone and interacts with the organizer. Expected prompt may appear near the organizer. Example: ```txt [E] Organizer ``` *** #### 2. The fighter creates or joins a fight Depending on configuration and available modes, the player may choose: ```txt Player vs NPC Player vs Player NPC vs NPC ``` For solo testing or simple servers, Player vs NPC can allow the player to fight against an NPC opponent. *** #### 3. The fight is prepared The system prepares the fighters, positions and fight state. The goal is to make the fight start clearly instead of becoming a chaotic street brawl. *** #### 4. The fight starts The fighter enters combat. Depending on mode, the player may fight: * Against an NPC * Against another player * As part of an event-controlled fight *** #### 5. The result is shown After the fight ends, the result is displayed in a clean way. Possible results: ```txt Win Loss Draw Cancelled by admin ``` The result may update ranking or stats depending on configuration. *** ### Spectator / Sponsor IC Usage Players do not always need to fight. They can also participate as spectators or sponsors. Common IC actions: * Watch an active fight * Support a fighter * Sponsor an active fight * React to the winner * Create crowd atmosphere * Participate in event roleplay Example IC lines: ```txt “I’m supporting the blue corner.” “This match is getting intense.” “Good fight.” “I’ll sponsor this one.” ``` The system uses sponsorship/support language to keep the activity focused on roleplay and event support. *** ### Organizer IC Usage The organizer is the main in-world point for the fight club. The organizer can represent: * A fight club manager * A boxing gym coordinator * An underground event host * A staff event NPC * A business representative Players interact with the organizer to access the fight system. Example IC flow: ```txt Talk to organizer → choose fight mode → prepare match → fight begins ``` This keeps the activity grounded in the world. *** ### Admin / Owner IC Usage For admins, owners and event staff, SL Fight Club can be used to create structured combat events. Common admin/owner IC uses: * Create a fight club zone * Prepare a boxing gym * Organize an underground tournament * Host NPC exhibition fights * Create a public event with spectators * Test PvN, PvP and NvN flows * Manage fight areas and organizer NPCs * Reset or cancel problematic fights * Use rankings to support recurring events Example admin/event flow: ```txt Choose location → create zone → place organizer → test fight → open event ``` Example event scenario: ```txt Staff prepares a small fight club night. The organizer NPC is placed near the ring. Players arrive, sign up, sponsor fights and watch matches. The event ends with winners recorded in the ranking. ``` *** ### Admin / Owner Technical Flow Admins and owners should configure the system before opening it to players. Common admin actions may include: * Create or configure fight zones * Place or configure the organizer * Enable allowed fight modes * Configure PvN difficulty * Configure PvP rules * Configure NPC vs NPC behavior * Configure ranking points * Configure permissions * Test sponsor flow * Test cleanup after fights * Cancel or reset fights if needed Recommended admin checks: ```txt 1. Confirm the fight zone exists. 2. Confirm the organizer prompt appears. 3. Test Player vs NPC. 4. Test Player vs Player if available. 5. Test NPC vs NPC. 6. Test sponsor/support flow. 7. Test fight result. 8. Check ranking update. 9. Restart the resource. 10. Confirm organizer and zones still work. ``` *** ### Fight Modes #### Player vs NPC A player fights against an NPC opponent. Useful for: * Solo servers * Training * Testing * Public fight club activity * Players who want a quick fight without another player online *** #### Player vs Player Two players fight each other in a controlled fight club flow. Useful for: * Competitive RP * Tournaments * Gym events * Underground fights * Staff-hosted events *** #### NPC vs NPC Two NPC fighters fight while players watch or sponsor the fight. Useful for: * Passive events * Spectator roleplay * Testing arenas * Social gatherings * Servers with low player count *** ### Ranking SL Fight Club may include ranking or fight stats depending on configuration. Ranking can help track: ```txt wins losses draws points fight history ``` Example scoring logic may include: ```txt Player vs NPC win = 1 point Player vs Player win = 2 points NPC vs NPC result = 2 points depending on mode/configuration ``` Check your installed version and configuration for exact ranking behavior. *** ### Example IC Scenarios #### Underground fight night Players gather in a hidden location and sign up for fights. ```txt “Tonight’s main event starts in five minutes.” ``` #### Boxing gym training A player fights NPC opponents for training RP. ```txt “I’m doing a few rounds before the tournament.” ``` #### NPC exhibition fight Admins start an NPC vs NPC fight while players watch. ```txt “Red corner versus blue corner. Place your support now.” ``` #### Player tournament Staff runs several PvP fights and tracks winners. ```txt “Winner advances to the next round.” ``` #### Social event Players gather around the ring even if they are not fighting. ```txt “This place is packed tonight.” ``` *** ### What this resource is not SL Fight Club is not intended to replace full combat systems, police systems or medical systems. It is focused on: ```txt fight club activity controlled fight flow PvN / PvP / NvN modes organizer interaction spectator support ranking event roleplay ``` For best results, servers should use it as a structured activity area, not as a replacement for every combat situation in the server. *** ### Main Features * Fight club activity system * Organizer NPC / interaction point * Player vs NPC fights * Player vs Player fights * NPC vs NPC fights * Spectator and sponsorship flow * Ranking and fight stats when enabled * Admin zone management * Fight cleanup logic * Result display * Configurable difficulty * Configurable permissions * Configurable fight zones * Target / interaction support * Command fallback support * ES/EN locale support * Clean SL Scripts style *** ### Dependencies #### Required ```txt FiveM server ``` #### Recommended / Optional ```txt ox_lib ox_target qb-target oxmysql QBCore Qbox ESX Standalone mode ``` If ranking or persistence is enabled, database support may be required. If target interaction is enabled, make sure your target resource starts before `sl_fight_club`. *** ### Installation Notes 1. Place the resource folder inside your server resources folder. Example: ```txt resources/[sl_scripts]/sl_fight_club ``` 2. Make sure the folder name is: ```txt sl_fight_club ``` 3. Configure: ```txt config.lua custom.lua locales/ ``` 4. If SQL is included and database mode is enabled, import: ```txt sql/install.sql ``` or use automatic migrations if supported by your build. 5. Add the resource to your `server.cfg`. Example: ```cfg ensure oxmysql ensure ox_lib ensure ox_target ensure sl_fight_club ``` If you are not using target interaction, configure fallback interaction mode in `config.lua`. *** ### How to Use #### Basic Fighter Flow 1. The player goes to the fight club zone. 2. The player interacts with the organizer. 3. The player chooses an available fight mode. 4. The fight is prepared. 5. The fight starts. 6. The result is shown. 7. Ranking or stats update if enabled. #### Basic Spectator Flow 1. The player goes to the fight club zone. 2. The player watches an active fight. 3. The player may sponsor/support an active fight if enabled. 4. The player reacts to the result. #### IC Summary ```txt Approach organizer → create/join fight → fight/watch/support → result recorded ``` #### OOC / Technical Summary ```txt Interaction → server validates zone/permissions → fight session starts → result processed → cleanup/ranking update ``` *** ### Commands Command names may depend on configuration. Common command examples: ```txt /fightclub /sl_fightclub /sl_fightclub_admin ``` Check `config.lua` for the exact command names used by your installed version. Commands are useful as fallback access, testing tools or admin shortcuts. *** ### Permissions Permission setup depends on server configuration. Common permission levels may include: ```txt view use manage admin owner ``` Recommended access logic: ```txt Players = use organizer and join allowed fights Spectators = view/support active fights Admins = manage zones, cancel/reset fights, test modes Owners = full access ``` Permissions may use: * Ace permissions * Framework groups * Jobs * Job grades * Config admin list * Custom permission bridge Check `config.lua` and `custom.lua` for your server setup. *** ### Configuration Open: ```txt config.lua ``` Common settings may include: ```txt Product information Locale Debug mode Startup logs Fight zones Organizer settings Allowed fight modes PvN difficulty PvP settings NPC fighter settings Sponsorship/support settings Ranking settings Permissions Interaction mode Target settings Command settings Database settings Cleanup settings Webhook/log settings ``` Recommended for production: ```lua Config.Debug = false ``` Use debug mode only while testing or troubleshooting. *** ### Custom Integrations Open: ```txt custom.lua ``` Use this file for server-specific functions such as: * Custom notifications * Custom permission checks * Custom framework integration * Custom logging * Custom job restrictions * Custom admin checks * Custom reward or economy bridges if enabled If your server uses standard systems, you may not need many changes here. *** ### Startup Logs When the resource starts correctly, you may see logs similar to: ```txt [sl_fight_club][INFO] Server ready: SL Fight Club v0.1.35.92 [sl_fight_club][INFO] Client ready: SL Fight Club v0.1.35.92 | Use /fightclub ``` If startup logs are disabled, check `config.lua`. *** ### Troubleshooting #### Organizer prompt does not appear Check: ```txt - Organizer is enabled in config.lua. - Fight zone is configured. - You are close enough to the organizer. - Target/fallback interaction is enabled. - The organizer ped spawned correctly. - F8 console has no errors. ``` *** #### Player cannot create a fight Check: ```txt - Player is near the fight zone. - Fight mode is enabled. - Player has required permission if configured. - No active fight is blocking the zone. - Server console has no validation errors. ``` *** #### Player vs NPC does not start Check: ```txt - PvN mode is enabled. - NPC model is configured correctly. - Fight zone has valid positions. - Player is not already in another fight. - Server console and F8 console are clean. ``` *** #### Player vs Player does not work Check: ```txt - PvP mode is enabled. - Both players are available and nearby. - Permissions allow PvP fight creation. - Fight zone has enough spawn positions. - No active fight is already using the arena. ``` *** #### NPC vs NPC does not work Check: ```txt - NvN mode is enabled. - NPC models are configured. - Arena positions are valid. - Organizer/admin flow is being used correctly. - F8 console has no ped/task errors. ``` *** #### Sponsor/support button does not work Check: ```txt - Sponsorship/support flow is enabled. - There is an active fight. - Player is allowed to support the fight. - Amount limits are configured correctly if used. - Server console has no validation errors. ``` *** #### Ranking does not update Check: ```txt - Ranking is enabled. - Database is configured if required. - oxmysql starts before sl_fight_club. - Fight result completed normally. - SQL tables exist. - Server console has no database errors. ``` *** #### Fight does not clean up correctly Check: ```txt - Cleanup settings are enabled. - Fight ended normally. - No player disconnected during the fight. - NPC entities were not removed by another resource. - Server console has no cleanup errors. ``` *** #### UI does not open or gets stuck Check: ```txt - web/ folder exists if NUI is used. - ui_page is correctly declared in fxmanifest.lua. - F8 console has no JavaScript errors. - Another NUI is not blocking focus. - Resource folder name is still sl_fight_club. ``` *** #### Normal players see admin options Check: ```txt - Admin permissions are configured correctly. - Framework group detection is working. - Ace permissions are not too broad. - custom.lua permission bridge is not returning true for everyone. ``` *** ### Version Notes #### v0.1.35.92 * Improved public wording and UX for fight creation and sponsorship. * “Create fight” language is used for clearer action flow. * Sponsorship/support wording keeps the system focused on RP support. * Public cancel options are restricted to prevent abuse. * Organizer prompt visibility improved. * Admin controls remain available for management and cleanup. #### v0.1.35.x * Character selection guard improvements. * NPC vs NPC flow polished. * Ranking UI improvements. * PvN, PvP and NvN modes stabilized through testing. * Fight cleanup and result behavior improved. *** ### Support When asking for support, include: ```txt Product: SL Fight Club Resource name: sl_fight_club Version: Framework: Target system: Database: Issue: Steps to reproduce: Fight mode: Server console error: Client F8 error: Screenshot/video: ``` Example: ```txt Product: SL Fight Club Resource name: sl_fight_club Version: v0.1.35.92 Framework: Qbox Target system: ox_target Database: oxmysql Issue: Organizer prompt appears but PvN does not start Steps to reproduce: Go to fight zone, interact with organizer, choose Player vs NPC Fight mode: PvN Server console error: none Client F8 error: attached Screenshot/video: attached ``` *** ### Final Notes SL Fight Club works best when used as a structured event or activity zone. For best results, configure the organizer, arena positions, permissions, fight modes and ranking behavior before opening the system to players. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-fight-club.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.