Config

The Ks_Core/config.lua file serves as the central hub for configuring Killstore Core. It contains all the key settings you need to tailor the core to fit your server's specific needs. From framework selection to notifications, progress bars, and other system integrations, this file ensures seamless interaction between Killstore Core and your server.

Below, you'll find the configuration code along with recommendations for making the most of its customizable options.

If you want to use custom functionality, it’s fully supported and can be implemented through the Ks_Core/custom/*.lua directory.

Server = {}

--      [[  Main  ]]
Server.Framework = 'esx' -- 'esx', 'qb-core', 'auto', 'standalone'

Server.Language = 'es'   -- 'es', 'en'

Server.Debug = true      -- true, false

--  [[  Scripts Selection ]]
Server.ProgressBar = 'Killstore'     -- 'Killstore', 'other'   << 'Killstore' Recommended for better experience of our scripts
Server.NotifySystem = 'Killstore'    -- 'Killstore', 'other'   << 'Killstore' Killstore will use the system you configure in custom/client.lua
Server.ClothingSystem = 'esx'        -- 'illenium-appearance', 'qb-clothing', 'esx', 'custom'
Server.SQL = 'oxmysql'               -- 'oxmysql', 'custom'
Server.AmbulanceSystem = 'auto'      -- 'auto', 'custom'

Customization Options

The configuration is fully customizable, allowing you to define your preferences for various systems:

• Framework: Supports esx, qb-core, auto, or standalone to adapt to your server setup.

• Language: Set to es (Spanish), en (English), to match your audience.

• Progress Bar: You can use Killstore’s Progress Bar (Killstore) or integrate another system. However, we highly recommend using Killstore's Progress Bar for the best experience with our scripts.

• Notification System: Killstore's Notification System (Killstore) is optimized for seamless integration, but other systems can also be configured.

• Clothing System: Supports a variety of options such as illenium-appearance, qb-clothing, esx, or custom integrations.

• SQL: Use oxmysql for optimal performance, or define a custom solution.

• Ambulance System: Automatically detect or configure a custom system as needed.