π Switching from another weapons script β
Your players keep every customization they already made. There is one query to run once after you switch, and which one depends on what you were using.
Back up your database before you run it
The order β
- Install Weapon Customization.
- Start the server once, so its table gets created.
- Run the query for the script you were using.
- Restart the server.
If you were using syn_weaponsV2 β
sql
INSERT INTO zoo_weaponcustomization (serial, weapon_id, weapon_name, charid, comps)
SELECT IF(l.serial_number IS NULL OR l.serial_number = '',
CONCAT('row:', l.id), l.serial_number),
l.id, UPPER(l.name), l.charidentifier,
JSON_EXTRACT(l.comps, '$.*')
FROM loadout l
WHERE JSON_VALID(l.comps)
AND JSON_TYPE(l.comps) = 'OBJECT'
AND JSON_LENGTH(l.comps) > 0
ON DUPLICATE KEY UPDATE comps = VALUES(comps);The query only reads your loadout table and writes to ours. Nothing you already have is touched. Knives and bows carry over too.
If you were using vorp_weaponsv2 β
Its customizations cannot be carried over with a query. That script stores each part as a number (a hash of the part's name), not as the name itself, and a query has nothing to turn a number back into a name with. Ask on Discord and we will help you move your players across.
If you want to keep vorp_weaponsv2 running next to Weapon Customization, see vorp_weaponsv2 next to Weapon Customization.
