Installation#
Requirements
| Resource | Required | Notes |
|---|---|---|
| ox_lib | Yes | Shared dependency, must start first |
| oxmysql | Yes | Stores every placement, must start first |
| Framework | Yes | qb-core, qbx_core or es_extended, detected automatically |
| Inventory | Yes | Detected automatically, see the list below |
Supported inventories are qb-inventory, new-qb-inventory, ps-inventory, lj-inventory, ox_inventory, qs-inventory, qs_inventory, codem-inventory, core_inventory and inventory.
Step 1 - Add the resource
Drag the frkn-weaponsling folder into your resources directory, for example:
resources/frkn-weaponsling
Step 2 - Start the resource
Add this to your server.cfg, after ox_lib, oxmysql, your framework and your inventory:
ensure frkn-weaponsling
If your resources are grouped with ensure [qb] or a similar folder start, make sure frkn-weaponsling is inside that group or started after it.
Step 3 - Set up the database
The resource creates its own tables on first start, so there is nothing to import. Three tables are created:
| Table | What it holds |
|---|---|
frkn_weaponsling_presets | Server wide placement for each weapon or item |
frkn_weaponsling_players | Personal placement saved per character |
frkn_weaponsling_vehicle_presets | Trunk and glovebox points per vehicle model |
A frkn-weaponsling.sql file ships with the resource if your database user cannot create tables. Import it once and start the resource normally.
Missing columns are added automatically when you update the resource, so never drop the tables to fix an update. Dropping them deletes every saved placement.
Step 4 - Give yourself admin access
The editor is admin only. Any of the following grants access:
| Method | How |
|---|---|
| Ace permission | add_ace group.admin frkn.weaponsling.admin allow in your server.cfg |
| Framework group | Be in a group listed in AdminPermissions, god and admin by default |
| Command ace | Any player with the general command ace, while AcceptCommandAceAdmins is true |
Open shared/config.lua to change which groups count as admin:
AdminPermissions = { 'god', 'admin' },
AdminAce = 'frkn.weaponsling.admin',
AcceptCommandAceAdmins = true,
Leave AcceptCommandAceAdmins on true only if you trust everyone holding the command ace. Set it to false on a public server and rely on the dedicated ace instead.
Step 5 - Set your language
Open shared/config.lua:
Language = 'en',
Available locale codes are en, tr, de, fr and ru. Every key lives in the matching file inside locales, and any key you leave out falls back to English.
Installation is done. Press F7 in game to open the editor and read the Features page to learn what it can do.
Commands
| Command | Who can use it | What it does |
|---|---|---|
/weaponsling | Admin | Opens and closes the editor, also bound to F7 |
/weaponslingreset confirm | Admin | Deletes every saved placement on the server |
Both commands are validated on the server, so a player without permission gets a notification and nothing else happens. Change the command names and the key in shared/config.lua:
Command = 'weaponsling',
Keybind = 'F7',
ResetCommand = 'weaponslingreset',
Keybind only sets the default. Each player can rebind it from the FiveM keybind settings.
Troubleshooting
| Problem | Fix |
|---|---|
Nothing happens on F7 | You are not admin, check Step 4 |
| The editor opens but the item list is empty | Your inventory is not detected, set Inventory manually in shared/config.lua |
| Item images are missing in the list | Set InventoryImagePath manually, for example nui://ox_inventory/web/images/ |
| Placements are not saved | oxmysql started after the resource, fix the ensure order |
| A custom weapon shows nothing | Add it to ModelOverrides with a valid GTA model |
| An item shows nothing | It has no prop model yet, register one from the editor |
| Weapons do not show in trunks | VehicleWeapons.Enabled is false, or no point exists for that vehicle model |