MX Weapon Aura

Bring custom and addon weapons to life with configurable particle aura effects designed for FiveM multiplayer servers.

MX Weapon Aura allows server owners to assign visual particle effects to selected weapons through a simple configuration file. Each configured weapon can use its own aura style and color, making it suitable for fantasy weapons, exclusive items, special rewards, themed collections, and other custom weapon projects.

Features

• Configurable particle aura effects for custom and addon weapons.
• Supports multiple aura styles and colors.
• Assign different effects to individual weapons.
• Simple configuration without modifying framework files.
• Distance-based rendering prevents unnecessary effects from running outside the configured range.
• Automatic particle cleanup when a player or weapon leaves the rendering area.
• Effects are handled correctly when players equip, switch, or remove configured weapons.
• Designed for OneSync multiplayer environments.
• Standalone resource with no ESX, QBCore, or Qbox dependency.
• Suitable for existing custom weapon collections and newly created addon weapons.

How It Works

Weapon names and their corresponding particle effects are defined inside the configuration file.

When a player equips a configured weapon, the assigned aura becomes visible in game. The resource monitors nearby players and only renders effects within the configured distance. Effects are automatically removed when they are no longer required, including when the weapon is changed or the player leaves the rendering range.

Weapons that are not included in the configuration remain unaffected.

Configuration

The editable configuration allows server owners to control:

• Supported weapon names.
• Particle effect assignments.
• Aura styles.
• Aura colors.
• Rendering distance.
• Additional available effect settings.

No framework-specific item or player data configuration is required.

Compatibility

MX Weapon Aura is intended for:

• Custom weapons.
• Addon weapons.
• OneSync multiplayer servers.
• Standalone, ESX, QBCore, and Qbox servers.

Framework compatibility is possible because the resource does not depend on framework-specific functions.

Requirements

• A working FiveM server.
• OneSync enabled.
• Custom or addon weapons that will use the configured effects.

Installation

1. Add the resource to your server resources directory.
2. Configure the desired weapon names and particle effects.
3. Add the resource to your server startup configuration.
4. Restart the server.
5. Equip a configured weapon and verify the effect in game.

Detailed installation and configuration instructions are included with the package.

Important Information

• This product adds particle aura effects to configured weapons.
• Weapon models are not included unless explicitly stated in the package contents.
• The appearance of an effect may vary depending on the weapon model and its dimensions.
• Review the included documentation before changing the configuration.
• Please verify that your weapon names match their FiveM spawn names.

Support

If you experience an installation or configuration issue, please provide relevant server and client console errors when requesting support. This helps identify configuration mistakes and compatibility issues more quickly.

MX Character Aura adds synchronized fire aura effects to player characters on FiveM servers. The resource includes five selectable aura colors and supports both ACE permissions and inventory-based access.

Each inventory item is connected to a specific aura color. Using the item activates its assigned aura immediately without opening a menu. Using the same item again disables the active aura, while using a different aura item switches directly to the selected color.

Features

• Five fire aura colors: Purple, Blue, Green, Red, and White.
• Synchronized character effects for multiplayer servers.
• Direct item-based aura activation.
• Use the same item again to disable the aura.
• Switch colors by using a different aura item.
• Optional F6 menu for authorized ACE users.
• Supports ACE-only, item-only, ACE-or-item, and ACE-and-item access modes.
• Individual ox_inventory item for every aura color.
• Configurable particle intensity and rendering distance.
• Automatic effect cleanup when players disconnect or leave rendering range.
• Standalone design with no ESX, QBCore, or Qbox dependency.
• Designed for OneSync multiplayer servers.

Inventory Integration

Five predefined items are included:

• Character Aura – Purple
• Character Aura – Blue
• Character Aura – Green
• Character Aura – Red
• Character Aura – White

The included installation files provide the required ox_inventory item definitions and inventory image.

Items are not consumed when used.

ACE Access

Authorized players can open the aura menu using the configured F6 keybind. ACE users can select any available color directly from the menu without requiring inventory items.

The ACE permission and access behavior can be changed through the editable configuration file.

Configuration Options

Server owners can configure:

• Access mode.
• ACE permission names.
• Inventory item names.
• Aura color assignments.
• Required item quantity.
• Menu keybind.
• Rendering distance.
• Particle intensity.
• Aura positioning and scale.
• Notification behavior.

Requirements

• FiveM server.
• OneSync enabled.
• ox_lib.
• ox_inventory when inventory-based access is enabled.

ESX, QBCore, and Qbox are not required.

Package Contents

• MX Character Aura resource.
• Five aura particle assets.
• Editable configuration file.
• ox_inventory item definitions.
• Inventory image.
• ACE permission example.
• Installation guide.
• Configuration documentation.
• Troubleshooting documentation.

Installation

Detailed installation instructions are included with the package. Add the resource to the server, install the provided inventory items when required, configure the preferred access mode, and start the resource after its dependencies.

Important Information

• Client-side and server-side scripts are protected using FiveM Asset Escrow.
• The configuration file remains editable.
• Aura items are not consumed by default.
• The inventory integration is only required when an item-based access mode is selected.