sh-weaponspawner follows the same ACE permission model as sh-vehiclespawner. If you have already configured ACE groups for sh-vehiclespawner, you can reuse those groups here with only the node names changed.
Requirements
sh-weaponspawner depends on warmenu. Ensurewarmenu is started before sh-weaponspawner in your server.cfg. No SQL import is required.
Installation
Download and place the resource
Copy the
sh-weaponspawner folder into your server’s resources directory alongside warmenu.Configure config.lua
Open
sh-weaponspawner/config.lua and define your categories, weapon entries, and ammo amounts as described below.Add ACE permission nodes
Grant the appropriate ACE nodes to your staff and player groups as shown in the Permissions section.
Core Configuration
The table below covers the top-level options inconfig.lua. All values shown are the shipped defaults.
config.lua
Permissions
sh-weaponspawner uses the same three-tier ACE pattern as sh-vehiclespawner: an open node to access the menu at all, an all node to bypass category restrictions, and individual category nodes for granular control.- server.cfg
- config.lua (permission nodes)
server.cfg
weaponspawner.all bypasses every category-level check. Reserve this node for server owners and senior staff only.Defining Weapon Categories
Weapons are defined inConfig.Weapons as a list of category objects. Each category has a name that maps to the permission key in Config.CategoryPermissions, and a list of weapon entries. The category name must match its key in Config.CategoryPermissions exactly.
config.lua
Weapon Entry Fields
| Field | Type | Description |
|---|---|---|
label | string | Display name shown in the spawner menu |
value | string | GTA V weapon hash name (all caps, e.g. WEAPON_PISTOL) |
ammo | integer | Ammo amount added alongside the weapon; use 0 for melee |
Pairing with sh-vehiclespawner
Consistent ACE group setup for admin tooling
Consistent ACE group setup for admin tooling
If you run both sh-weaponspawner and sh-vehiclespawner on the same server, use identical group names for both resources so a single This pattern scales cleanly: define your groups once, then add ACE nodes as you install new SH Development resources.
add_principal or add_ace line covers a player’s access across both scripts.server.cfg