Turn all your jewelry clothing into usable items in minutes. Auto-generate mappings, ox/qb item configs, and store lists. Players wear/remove with animations, chains vanish on loss/robbery, and your mappings stay stable across updates.
Auto Jewelry removes 95% of the setup work for server owners. Point it at your clothing pack and run the setup command—we’ll scan, map, and generate everything:
Auto-generate jewelry map (male & female), ox items, qb items, and store configs
Create usable items that equip the correct drawable/texture with clean wear/remove animations
Chain-snatching ready: if a chain leaves inventory (drop/stash/trade/robbery), it auto-unequips instantly
Stable mapping: mappings persist even when you add new clothing or change builds—no remapping headaches
Inventory support: drop-in configs for ox_inventory and qb-inventory
Framework friendly: QBCore & ESX compatible
Minutes, not days — bulk generation replaces manual item creation, slot math, and store hand-entry
Future-proof — stable tech keeps your mappings intact when your wardrobe grows
Immersive gameplay — chains are real assets: wearable, stealable, tradable
setup command → builds male/female entries and all docs/configs
Wear/Remove animations (standard chain on/off)
Auto-unequip on loss/robbery (true ownership binding)
Performance-safe (event-driven)
Optional desktop capture helper to screenshot every item for store images
Client & server scripts
Example configs for ox & qb
Mapping schema with sex-aware entries
Generated code (tablet/ox/qb)
ox_inventory or qb-inventory
ox lib
Will my mappings break when I add new clothes?
No—Stable tech mapping preserves references across updates.
Does it support both male and female?
Yes— writes sex-specific entries automatically.
What happens in a robbery?
If a chain leaves the inventory, it instantly unequips—no ghost visuals.
