Docs/ORB WeaponSkins/Installation

Installation

Requirements

Both are already present on almost every server.

Steps

1. Drop the orb-weaponskins folder into your resources/.

2. Add it to server.cfg, after its dependencies:

cfg
ensure ox_lib
ensure oxmysql
ensure orb-weaponskins

3. Give yourself admin access:

cfg
add_ace group.admin orb.weaponskins allow

4. Start the server.

On first boot the resource detects your framework and creates its own database table. There is no SQL file to import.

Admin access

Admin unlocks the library panel: creating, hiding and deleting skins. Players without it can still use every published skin.

Three things grant admin, and any one of them is enough:

MethodNotes
The ace aboveWorks on every framework, including standalone
Framework groupadmin, superadmin or god on QBox, QBCore or ESX
Server consoleAlways allowed

Existing admins usually work with no extra setup, because the framework groups are honoured automatically.

If the admin menu does not appear, run /wskindiag in game. It prints, in the F8 console, exactly which permission checks pass and which fail.