About

Built for cities that get played in.

B3AZTY makes maps, MLOs and assets for FiveM roleplay servers. Everything in the store exists because a live city needed it and nothing on the market did the job properly.

Products
2
Rated
5.0★
  • Instant Tebex delivery
  • Lifetime updates included
  • QBCore · ESX · QBOX · Standalone
  • Optimized for low server load
  • Discord support in under 2h
  • No subscriptions — buy once
Why this store exists

Most FiveM assets are built to look good in a screenshot. That is a different problem from holding up when forty players are inside one interior at once, on a server already streaming a hundred other resources.

So every build here starts from the server side. Collision gets cleaned up, LODs get authored properly, textures get sized for what they are actually used for, and the whole thing runs in a live city before it goes on sale. If it costs frames it does not ship.

The result is a smaller catalog than most stores carry, and that is deliberate. Fewer products, each one finished.

Products in the catalog2
Categories1
Frameworks supported4
Delivery timeInstant
Update policyFree for life
Average first replyUnder 2h
The standard

What every drop has to clear.

Four things are non-negotiable before a product gets a price. Most of the work happens after it already looks finished.

Profiled in a live city

Tested under real player load, not in an empty session. Frame cost is measured before anything is listed.

Clean collision and LODs

Authored by hand rather than auto-generated, so players do not fall through geometry or watch the world pop in around them.

Framework agnostic

Verified against QBCore, ESX, QBOX and Standalone. Nothing assumes a particular resource stack to work.

Documented properly

Every package ships a README covering install, stream folder placement, dependencies and known conflicts.

Process

How a drop gets made.

Roughly five stages, and the last one never really finishes.

  1. 01

    Find the gap

    Something a city needs that either does not exist or only exists badly. Usually it surfaces in a Discord conversation.

  2. 02

    Block it out

    Layout and flow first — where players enter, where they gather, what the space is actually for. Detail comes only after that works.

  3. 03

    Build and optimize

    Model, texture, author collision and LODs, then profile it and cut anything costing more than it is worth.

  4. 04

    Run it live

    Into a real server with real players. Whatever breaks, breaks here rather than on your city.

  5. 05

    Ship, then keep shipping

    Released with documentation, then maintained against new game builds. Updates stay free for everyone who already owns it.

Want the detail on a specific product? Every listing spells out what it replaces, what it depends on and which frameworks it was tested against — browse the catalog.

Ready when you are

Give your city something worth logging in for.

Browse the catalog, grab a free drop to test the build quality, and deploy tonight. Instant delivery, lifetime updates, no subscription.