Getting your files

Everything is sold and delivered through Tebex. When checkout completes, the download unlocks on your Tebex account immediately and stays there — you can re-download it later, and any updates to something you already own are free from the same place.

Each product arrives as a single .zip. Extract it somewhere sensible before you start; several of the packs are over 150 MB and working directly inside a zip will only cause you grief.

Licence

Every pack ships with a LICENCE.txt. In short:

• Use the files on as many of your own servers or projects as you run, commercial or private.
• Modify, retexture, rig and convert them freely.
• Use them in a server you operate or are paid to build for a client.

What you may not do:

• Resell, redistribute or share the raw model files.
• Claim authorship of the models.
• Upload them to any asset site, leak site or public repository.

Model packs at a glance

These figures are measured from the shipped meshes, not estimated. Triangle counts assume fan-triangulated n-gons, which is what your importer will do.

Things that are true of every pack

• Not rigged. No skeleton and no vertex weights on any mesh.
• Scale varies between models. Check and normalise before you rig anything.
• These are detail meshes, not game props. A 50,000-triangle necklace is far heavier than anything you should attach to a player. Decimating is expected work, not an optional polish step.

What's in a pack

Every pack has the same shape. Taking Simple Rings as the example:

Previews are named to match their mesh, so ring_13_Diamond_ring.obj has ring_13_Diamond_ring.png beside it in previews/. Every model in every pack has one — that is checked before release.

The README.txt inside each pack is generated from the geometry itself rather than written by hand, so if it disagrees with anything on this page, trust the README.

The .mtl files

Each mesh ships with a matching .mtl defining a neutral polished-gold material, plus a gem material where the mesh named one. That exists so the model imports looking like jewellery instead of flat default grey. It is a starting point — retexture freely. No texture image files are referenced, so nothing will come up missing on import.

Importing

.obj imports into Blender, 3ds Max, Maya, Cinema 4D, ZBrush and most other packages without a plugin. In Blender use File → Import → Wavefront (.obj) and keep the .mtl beside the .obj so the material comes with it.

Fix these first, in this order

1. Scale. Models were authored at different scales. Bring your piece to real-world size against a reference before anything else — everything downstream depends on it.
2. Orientation. Rotate so the piece hangs the way it should on a body.
3. Origin. Set the origin where the piece attaches, not wherever the exporter left it. An origin left at the world centre is the usual reason an asset ends up floating off the model in-game.
4. Decimate. Only once the above are right. Trying to fix scale and orientation after decimating means redoing it.

UVs & texturing

This is the part most likely to surprise you, so it is spelled out per pack rather than glossed over.

Both ring packs have no UVs at all

All 65 ring meshes ship with zero UV coordinates. Flat materials and vertex colour work as-is, but you must unwrap them before applying any image texture. Budget for that.

Chain packs are mostly mapped, with named exceptions

Chain meshes carry UVs, but some are collapsed remnants or projected far outside the 0–1 range and are not usable as delivered. Those are listed here and in each pack's README so you know before you start:

For jewellery, Smart UV Project is usually enough — these are metal surfaces with a repeating material rather than painted artwork, so a perfect unwrap is rarely worth the time.

Converting for FiveM

Turning one of these meshes into something a player can wear is a real piece of work. This is the shape of it, and the traps that cost the most time.

1. Reduce the mesh

Decimate hard. For scale: an entire GTA V player model is in the region of 10,000–15,000 triangles, and the median mesh in these packs is three to five times that on its own. A chain or ring that a player wears should be a small fraction of the ped, not a multiple of it.

2. Rig it

Nothing in these packs is rigged. A component has to be skinned to the ped skeleton or it will not move with the body — an unrigged mesh exported as clothing sticks out at a fixed point in space and does not follow animation. Chains are weighted to the upper spine so they hang and swing with the torso.

3. Export

• Components export to .ydd, textures to .ytd.
• A prop and a component are not interchangeable. Props take a p_ stream name; components do not, and shipping one as the other is a common cause of an asset appearing in the wrong place or not at all.
• Strip any embedded skeleton from a component before export. An embedded skeleton is a classic cause of clothing that imports cleanly and then renders invisible in game.

Advanced Organization Panel

A gang and organisation management system driven from one in-game panel — ranks, members, permissions, shared treasury, territories, businesses, reputation and heat.

Requirements

• FiveM server build 5848 or newer — declared in the manifest.
• A framework, or none. QBCore, Qbox and ESX are all supported and detected automatically. It also runs standalone.
• A database driver — oxmysql or mysql-async.

Installation

1. Drop the folder into your resources directory. It must stay named advanced_organizations — every export call is written against that name, so renaming the folder breaks integrations.
2. Import all four SQL files from sql/: organizations.sql, applications.sql, messages.sql and outfits.sql. Every statement is CREATE TABLE IF NOT EXISTS, so they are safe to re-run.
3. Add ensure advanced_organizations to server.cfg after your framework and your database resource.
4. Grant admin access: add_ace group.admin organization.admin allow
5. Restart and read the console.

Optional: seed the stock gangs

sql/seed_gangs.sql inserts six ready-made organisations (Lost MC, Ballas, Vagos, Cartel, Families, Triads) with four ranks each. It creates no tables. Import it before first start — organisations are cached at start-up, so rows inserted underneath a running resource will not appear until you restart it.

Commands

Ranks and permissions

Twenty permission keys cover members, structure, economy, assets and oversight. Two rules matter more than the rest:

• The highest rank is the leader and implicitly holds every permission, whatever is stored against it — so a server can never lock itself out of its own organisation. The leader cannot be removed by members and cannot leave; leadership has to be transferred first.
• You cannot act on someone at or above your own rank. You cannot hand out a rank at or above your own level, and when you create or edit a rank, any permission you do not personally hold is stripped from it. Admins bypass all of this.

New organisations get a seven-rank ladder by default, from Recruit up to Boss. Note the stock-gang seed file uses a different four-rank ladder instead, because stock QBCore gangs define exactly four grades.

Gang applications — the playtime trap

Gang outfits

Outfits are stored as raw ped component and prop slots captured with base natives, so the feature works with any clothing menu — or none at all. Eight clothing resources are recognised for hand-off, including illenium-appearance, fivem-appearance, qs-appearance and qb-clothing. If yours lives in a renamed folder, pair the adapter with the folder name rather than editing it: { adapter = 'illenium-appearance', resource = 'clothing' }.

Outfits are stored per body type — the same drawable index is a different garment on the male and female freemode skeletons, so members only see the variant matching their character. To cover everyone, save the same look once on each body.

Framework gang sync

Mirroring organisations into your framework's own gang system is off by default. When enabled it only fires for organisations whose ID matches a gang your framework already defines; anything else is skipped and named once in the console. Rank-to-grade mapping is deliberately not a naive level - 1 — the leader takes the top grade and the rest spread below it, because stock gangs define four grades with the top one flagged as boss, and a naive mapping would promote your mid-ranks to gang bosses.

For developers

The resource exposes 34 server exports and 7 client exports so other resources can read and drive organisation state — membership and rank lookups, treasury add/remove, reputation and heat, businesses, drugs, territories and activity logging. A few of the most useful:

Every request from the panel routes through a single server event and is re-validated server-side — rate limit, identity, organisation, permission, handler. Non-admins are always scoped to their own organisation regardless of what the client asks for.

Support

Questions before or after buying go to the Discord — that is the fastest route to an answer, and where update notes get posted.

If something does not work as described on its store page, say so and it gets sorted. If you are unsure whether a pack suits your use case, ask before you buy rather than after.

Join the Discord