Settings
Every setting in config.lua.
Every setting in config.lua, taken from the file itself. The comments in the
file and this page always say the same thing.
Config.Framework
Your framework: "esx", "qb-core", "qbox", "ox" or "custom". With "custom" the resource loads public/framework.lua instead.
| Setting | Default | What it does |
|---|---|---|
name | "esx" | |
esxMode | "legacy" | Only when name is "esx": "legacy" uses the export, "old" waits for the shared object event that older forks still use. |
esxSharedObjectEvent | "esx:getSharedObject" |
Config.UI
Notifications: "ox_lib" or "custom" (loads public/ui.lua).
| Setting | Default | What it does |
|---|---|---|
name | "ox_lib" |
Config.Language
Any file in languages/, without the extension.
Config.Language = "english"Config.Debug
Prints what the resource is doing to the console.
Config.Debug = falseConfig.OpenCaseCommand
The chat command that opens the case menu.
| Setting | Default | What it does |
|---|---|---|
enabled | true | |
name | "cases" |
Config.RewardTypes
Two reward types need something your framework does not have. Coins are a currency of your own. A vehicle is put away under no garage, and which garage it belongs in is yours to say.
Both take the same three ways, tried in this order:
1 the event, if you name one
2 the export, if you name one
3 public/rewards.luaenabled = false takes the type out of every pool. The rewards left keep their ratios to each other.
| Setting | Default | What it does |
|---|---|---|
coins | a table | |
vehicle | a table |
Config.Database
The table is created on first start, and only while logOpenings is on. The name is yours, but everything in it that is not a letter, a digit or an underscore is stripped out, and a name left empty by that falls back to ktx_case_openings.
| Setting | Default | What it does |
|---|---|---|
logOpenings | true | |
table | "ktx_case_openings" |
Config.Rarities
The colour and the name on the card. Rarity does not touch the odds, those stand on the reward itself.
| Setting | Default | What it does |
|---|---|---|
common | a table | |
rare | a table | |
epic | a table | |
legendary | a table | |
mythical | a table |
Config.Cases
Every case and its reward pool.
The draw runs over whatever the chances add up to, so a case that misses 100 still works and keeps its ratios. They are written down as percentages though, so the server prints a warning on start for every case that does not total 100.
Reward types: money (amount), item (item, amount), weapon (weapon, ammo), vehicle (model), coins (amount).