Installation

The framework is detected automatically (custom/<framework>/).

Download Sizes

Plan for these before you install:

Start order relative to other weapon packs does not matter. The pool patches no weapon metadata, so it has nothing to conflict with.

Downloading Weapon Skin Creator#

Quasar Weapon Skin Creator is linked to your CFX Portal account.

Sign in to the CFX Portal using the same account used during checkout, then open Granted Assets and locate Weapon Skin Creator in your asset library. Download the latest version and extract the archive.

After extracting the download, you should have the following folder:

Never rename the resource folders.

Installing the Resource#

Move the whole [weaponskin-creator] folder into your server's resources directory:

Then add this to your server.cfg:

The loading order matters. The pool and the data resource must start before the creator.

The Data Folder#

qs-weaponskin-data is your data: the addon weapons you add, the AI pictures your players generate and the finished skin textures.

The creator creates it on the first start.

:warning: Never delete or replace qs-weaponskin-data when you update. Replace qs-weaponskin-creator and qs-weaponskin-pool only. It is the only copy of everything your players have made, and deleting it cannot be undone.

Importing the Database#

Start the server once and the tables create themselves.

The qs_weaponskin_* tables are built automatically. [sql]/database.sql is the same schema, included only for servers that prefer to import by hand.

The Pool#

qs-weaponskin-pool ships pre-built and is used as it is. There is nothing to generate and no command to run.

The shipped pool matches the shipped Slots and enabled settings. Changing those does not rebuild it, because Config.Pool.AutoGenerate is false — the studio simply keeps offering what the pool actually holds, and the console says so at boot.

Rebuilding It (Advanced)

Set Config.Pool.AutoGenerate = true only if you want a pool tailored to your own settings. Fewer slots or fewer weapons is a smaller download for every player.

With it on, the pool is written and mounted on the next server start, and weaponskin_pool forces a rebuild.

:warning: Rebuilding while players are online is not safe. A client reads weapon metadata once per session, so players already in game keep the old pool.

When that happens the resource warns in the console every 20 seconds and holds new players at the join screen until somebody restarts — letting them in would give them a session where no skin works at all. Config.Pool.BlockJoinWhenStale = false turns that guard off.

None of this applies while AutoGenerate is false, which is the default.

Before you raise Slots, read the budget docs. Every slot is a file every player downloads.

Adding Add-On Weapons#

No tools needed.

1. Run /weaponskincreator → Addon Weapons.

2. Scan.

3. Add support.

4. One restart on an empty server.

Configuration#

It is all in game. Open /weaponskincreator → Settings: every tunable this resource has is there, grouped and searchable, with a line under each one explaining what it costs you.

Changes apply the moment you save — to the server and to every player online. The handful that genuinely cannot work that way are marked needs a restart in the panel.

Settings live in qs_weaponskin_settings, one row per value you actually changed, so an update never overwrites your tuning.

Verifying the Installation#

Start the server, then in game:

1. Run /weaponskincreator.

2. Create a shop — area, NPC, workbench.

3. Check the Overview tab's self check is green.

Walk up to the shop ped and the skin studio opens. Done.