How to publish

1. Prepare the package

Upload one ZIP (max 100 MB) with one or more resources, each a folder with an fxmanifest.lua, laid out the way they go into resources/:

my_resource/
├─ fxmanifest.lua      ← required: fx_version, game, scripts, dependencies
├─ config.lua
├─ client/main.lua
├─ server/main.lua
├─ html/index.html     ← NUI, if any (ui_page)
└─ stream/             ← models, textures, ymap/ytyp (MLO, vehicles, clothing)

fx_version 'cerulean'
game 'gta5'
lua54 'yes'
name 'my_resource'
version '1.0.0'
shared_script '@ox_lib/init.lua'
client_script 'client/*.lua'
server_script 'server/*.lua'
dependencies { 'es_extended', 'ox_lib' }

• The game line tells the scanner which game the resource is for: this site takes FiveM resources only.
• Every script the manifest names must be in the package. dependencies become the item's dependencies, and frameworks (ESX, QBCore, Qbox, ox) are added as tags.
• No escrow: .fxap files (Tebex Asset Escrow) are tied to the buyer and are refused. Sell paid resources on Tebex and link the store in the description.
• No .exe, .bat, .ps1 or other executables. C# resources (.dll) are allowed but always go to manual review.

2. Images and videos

• 16:9, ideally 1920 × 1080 px, JPG, PNG, WebP, GIF or AVIF, up to 8 MB each, 10 images. We convert to WebP and strip EXIF and location data.
• The first image is the cover: an in-game shot without text near the edges and without third-party logos.
• Paste a YouTube link or a Medal clip (up to 4 videos); the trailer is shown first.

3. Description

Markdown is supported. A good description has: what it does, features, installation (ensure my_resource in server.cfg, SQL to import, items for the inventory), configuration and commands, known issues and a link to support (Discord, GitHub). Say which framework and version you tested with.

Tips

Add a tip / donation link in the item details (Ko-fi, Patreon, PayPal, Buy Me a Coffee, GitHub Sponsors, Liberapay, Open Collective, Stripe). Players see ♥ Support the author next to the download. Tips are always voluntary: the download, features and support must never depend on them.

4. Versions

• Version numbers follow SemVer (1.2.0). The beta channel does not replace the stable version shown to everyone.
• A broken version can be withdrawn in My work; the previous one becomes current.

5. Review

1. Upload the package as a .zip, or link a file of a GitHub release. The scanner checks the archive: the manifest, executables, known Cfx backdoors (code loaded from the internet, add_ace / add_principal, reading sv_licenseKey or rcon_password), Discord webhooks and paste sites, obfuscation and traces of leaks.
2. A moderator reviews new creators and anything risky, with a diff against your previous version. A rejection always comes with reasons.
3. Trust grows with your track record: after 3 approved versions clean updates go live at once, after 10 and 30 days clean new items too. A rejection or a malware report puts you back to full review.
4. Published files are signed (Ed25519). The SHA-256 and signature are on the Versions tab.

Publishing requires two-factor authentication (Settings → 2FA).