Documentation
Everything you need to get Quasar Tattoo Creator running: five minutes, no Node.js and nothing to build outside the game.
Quasar Tattoo Creator bakes tattoos into real, streamed GTA ped decorations — and everything runs inside FXServer. No Node.js, no .exe, no CodeWalker, no manual asset builds.
Requirement | Status | Notes |
|---|---|---|
FXServer with OneSync + Mono | Required | Every current artifact has both |
|
Required |
| Required |
MySQL database | Required | — |
Framework | Optional | ESX, QBCore or Qbox — auto-detected |
Works on Windows and Linux. Anything that isn't ESX, QBCore or Qbox runs in standalone mode — edit custom/standalone/*.lua for money and identifiers.
Quasar Tattoo Creator is linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, then open Granted Assets and locate Tattoo Creator in your asset library. Download the latest version and extract the archive.
After extracting the download, you should have the following folder:
[tattoo-creator]/
├── qs-tattoo-creator/ the script (studio UI, server pipeline, texture encoder)
├── qs-tattoo-preview/ static data: the decoration collection — never edit, never restart
└── [sql]/ database.sql (install) · clean.sql (wipe)Folder | Description |
|---|---|
| Main resource (required). |
| Pure data (required). Six decoration presets plus placeholder textures |
| SQL files. |
Never rename the resource folders.
Move the whole [tattoo-creator] folder into your server's resources directory:
resources/
└── [tattoo-creator]/Then add this to your server.cfg, after oxmysql, ox_lib and your framework, if you run one:
ensure qs-tattoo-preview
ensure qs-tattoo-creatorNo
add_acelines are needed. Admins are whoever your framework calls admin (custom/<framework>/server.lua → playerIsAdmin— ESX groups inConfig.AdminGroups, QBgod/admin), and the assets resource is restarted with server natives.
Why qs-tattoo-preview Is Separate
qs-tattoo-preview is pure data and must simply stay running — the script starts it for you if you forget.
It is a separate resource on purpose. Stopping the resource that owns a PED_OVERLAY_FILE unmounts that decoration collection, and a ped still wearing one of its decorations then faults the game client on the next decoration native.
Keeping the collection outside the script means restarting qs-tattoo-creator is always safe.
qs-tattoo-data next to itself and starts it. No ensure line is needed.#It holds your server's data: the worn tattoos, the AI pictures, the uploads and the exported catalog.
:warning: Never delete or replace
qs-tattoo-datawhen you update. It is not part of the download, and it is the only copy of every tattoo your players are wearing. Deleting it cannot be undone.
The database keeps file names only, never paths, so moving the whole server to another folder or machine is safe as long as qs-tattoo-data moves with it. Back it up together with your database.
Open your preferred database manager (such as phpMyAdmin, HeidiSQL, DBeaver, or Navicat), select your server's database, and execute [sql]/database.sql.
Or just start the resource — the tables are created automatically. Importing by hand is simply how you get to look at your data before the server has ever run.
Start your server. A healthy install prints nothing.
The resource only speaks up when a startup check fails, and then the line tells you exactly what to fix. The full check list is in /tattoocreator → Overview.
Log in as admin and run /tattoocreator.
Go to Shops → +.
Click Select to place the NPC in the world — scroll to rotate.
Optionally draw the studio area (polygon, free camera) and set the blip.
Save.
Walk up to the shop — the studio opens.
Done. Run /tattoo_shop at any time and it tells you, one line per studio, what is still missing.
There is almost nothing to edit in files. Open /tattoocreator → Settings: every tunable this resource has is there, grouped and searchable, with a line under each one explaining what it costs you.
Changes apply the moment you save — to the server and to every player online. The handful that genuinely cannot work that way are marked needs a restart in the panel.
Settings are stored in qs_tattoo_settings, one row per value you actually changed, so an update never overwrites your tuning.
Replace qs-tattoo-creator and qs-tattoo-preview with the new versions.
:warning: Never delete or replace
qs-tattoo-data.
Your settings live in the database and are not touched.
[sql]/clean.sql drops all qs_tattoo_* tables. Delete the qs-tattoo-data folder to remove every picture and the exported catalog.