Weapon Installation Guide

This guide explains how to install, test, and configure Raynex weapon assets for FiveM servers.

Raynex weapon packs are installed as standalone FiveM resources. A shared weapon core resource is not required for the current weapon packs.

Requirements

Before installing a Raynex weapon asset, make sure you have:

• A working FiveM server

• Access to your server resources folder

• Access to your server.cfg

• Admin or developer access for testing weapons in-game

• Basic knowledge of starting FiveM resources

Important Notes

• Raynex weapon resources are standalone resources.

• There is currently no shared raynex_weapon_core resource.

• Do not merge weapon resources into a core folder.

• Each purchased weapon resource should be installed and started separately.

• Official ready-made inventory configs are not included yet.

• Framework inventory support for ox_inventory, QBCore, Qbox, ESX, and other inventory systems is not included at this time.

• Server owners may still integrate weapons manually into their own inventory system, but this requires custom configuration on their side.

Installation

Step 1 — Upload the Weapon Resource

Upload the purchased Raynex weapon resource folder to your server resources directory.

Example:

resources/[raynex]/raynex_weapon_resource_name

The exact folder name may be different depending on the purchased weapon pack.

Do not rename internal weapon files unless the product-specific instructions say it is safe to do so.

Step 2 — Start the Resource

Add the weapon resource to your server.cfg.

Example:

ensure raynex_weapon_resource_name

Replace raynex_weapon_resource_name with the actual folder name of the purchased weapon resource.

If you purchased multiple weapon resources, add each one separately.

Example:

ensure raynex_weapon_cf552
ensure raynex_weapon_mx9
ensure raynex_weapon_p32

The example names above are only examples. Always use the real folder names from your purchased package.

Step 3 — Restart the Server

After installing or updating weapon files, restart your server.

A full server restart is recommended because weapon metadata may not always reload correctly with only a resource restart.

Testing Weapons

After installation, weapons can be tested through:

• An admin menu

• A weapon showroom system

• A custom spawn command

• A development/testing script

Use the spawn names listed in the weapon reference table below.

Important: weapon spawn names are case-sensitive in many scripts. Use them exactly as listed.

FiveM Weapon Spawn Names (Raynex Pack)

Weapon Components

Some Raynex weapons support optional components such as suppressors, scopes, flashlights, grips, magazines, muzzle devices, or compensators.

Use only the components listed for each weapon.

Do not mix components between unrelated weapons unless you have tested them and confirmed they work correctly.

CF-550 Assault Rifle

Spawn name:

WEAPON_CF552

Available components:

MX-9 Tactical SMG

Spawn name:

WEAPON_MX9

Available components:

P32 Compact Pistol

Spawn name:

WEAPON_P32

Available components:

RH-12G Shotgun

Spawn name:

WEAPON_RH12G

Available components:

TPR-21 Battle Rifle

Spawn name:

WEAPON_TPR21

Available components:

Field Assault Rifle

Spawn name:

WEAPON_ARIFLELD

Available components:

None

This weapon does not have configured attachment components.

AR-2 Tactical Rifle

Spawn name:

WEAPON_ARIFLE2

Available components:

Blackline Assault Rifle

Spawn name:

WEAPON_ARU_BL

Available components:

Brownline Assault Rifle

Spawn name:

WEAPON_ARU_DF

Available components:

Silent Pistol

Spawn name:

WEAPON_PISTOLSL

Available components:

Heavy Tactical Shotgun

Spawn name:

WEAPON_SHOTGUNH

Available components:

SZ Compact SMG

Spawn name:

WEAPON_SMGSZ

Available components:

Urban SMG

Spawn name:

WEAPON_SMGU

Available components:

Showroom Configuration

If you use a weapon showroom script, add the weapon spawn name and its supported components to your showroom configuration.

A basic example:

{
    title = 'MX-9 Tactical SMG',
    image = 'img/weapon_mx9.jpg',
    url = 'https://raynex.dev/products/mx-9-tactical-smg',
    weapon = 'WEAPON_MX9',
    ammo = 250,
    defaultTint = 0,
    maxTint = 5,
    components = {
        { label = 'Extended Magazine', name = 'w_mag10_v2_df', group = 'magazine', default = false },
        { label = 'Flashlight', name = 'COMPONENT_AT_AR_FLSH', group = 'flashlight', default = false },
        { label = 'Medium Scope', name = 'COMPONENT_AT_SCOPE_MEDIUM_MK2', group = 'scope', default = false },
        { label = 'Suppressor', name = 'COMPONENT_AT_AR_SUPP', group = 'barrel', default = false },
        { label = 'Muzzle', name = 'COMPONENT_AT_MUZZLE_05', group = 'barrel', default = false },
        { label = 'Grip', name = 'COMPONENT_AT_AR_AFGRIP_02', group = 'grip', default = false }
    }
}

Your showroom script may use a different format. If so, keep the same weapon spawn names and component names, but adapt the structure to your script.

Framework and Inventory Support

Raynex weapon resources can be installed and tested as standalone weapon resources.

At this time, official ready-made inventory configurations are not included.

This means we currently do not provide ready-made item configs for:

• ox_inventory

• qb-inventory

• QBCore

• Qbox

• ESX

• Other framework-based inventory systems

Weapons may still be integrated manually by a server owner or developer, but this requires custom configuration for the specific inventory system.

Official inventory support may be added in future updates.

Updating Weapon Resources

When updating a weapon resource:

1. Stop your server.

2. Back up the current resource folder.

3. Replace the old resource files with the updated files.

4. Make sure the resource is still ensured in server.cfg.

5. Start the server and test the weapon in-game.

A full server restart is recommended after updating weapon files.

Troubleshooting

FiveM weapon not spawning? Fix checklist

Check that:

• The weapon resource is installed in the correct folder.

• The resource is added to server.cfg.

• The resource folder name matches the ensure line.

• The spawn name is written correctly.

• The server was fully restarted after installation.

• There are no console errors related to the weapon resource.

FiveM custom weapon invisible in-game?

Check that:

• The full weapon package was uploaded.

• The stream files are inside the weapon resource.

• The resource is started before testing.

• The server was restarted after installation.

• There are no missing files in the resource folder.

FiveM weapon has no sound or behaves wrong?

Check that:

• The full resource package was installed.

• Weapon metadata files were not removed or renamed.

• The resource was fully restarted with the server.

• No other resource is overriding the same weapon name.

• There are no errors in the server or client console.

FiveM weapon attachments / components not showing?

Check that:

• The component name is written exactly as listed in this guide.

• The component is supported by that specific weapon.

• The component files are included in the resource.

• Your showroom or script supports weapon components.

• You are not using components from another weapon.

Weapon works in admin menu but not in inventory?

This usually means the weapon resource itself is installed correctly, but your inventory system does not have a custom item configuration for it.

Raynex does not currently provide official ready-made framework inventory configs.

A server developer may need to configure the weapon manually inside your inventory system.

Support

Raynex provides post-purchase support for weapon assets.

If you need help, open a support ticket in our Discord server and include:

• Product name

• Order ID or proof of purchase

• Weapon spawn name

• Resource folder name

• Screenshot or video of the issue

• Server console errors, if available

• Client console errors, if available

• Short explanation of what you already tried

Discord Support:

https://discord.gg/raynex

Please do not share private server keys, license keys, or sensitive information in public channels.