Choose the target tattoo system before exporting
Write down the appearance or tattoo script already installed on your server and the character models you intend to support. The artwork, streamed tattoo asset, menu entry and saved selection are different pieces. Choose the supported integration route before assuming an exported file can be pasted into any appearance menu.
rcore’s Add-on tattoos documentation links its Addon Generator and Durty Cloth Tool as creation routes. Use those original tools and their current documentation. This guide reviews the public workflow and proposes checks; Magnate has not uploaded artwork, generated a pack or tested a tattoo in gameplay.
| Deliverable | Purpose | Check independently |
|---|---|---|
| Source artwork | The design to be placed | Ownership, image quality and intended body area |
| Exported resource | Game asset packaging | Tool output and installation instructions |
| Target-script configuration | Makes the asset available to the interface | Correct generated integration and menu registration |
| Placement | Fits the intended character | Each supported model and selected area |
| Saved selection | Restores the chosen appearance | Reconnect and normal appearance changes |
Prepare the artwork and placement brief
Use an original design or material you have permission to adapt and deploy. Keep the editable source alongside a named export so future corrections do not depend on an unknown screenshot or a compressed chat attachment. Define the intended body area and the models to support before adjusting placement.
Inspect fine lines, lettering and the edge of the image at the scale players will actually see. A design that is readable in a full-screen editor can become unclear on a small area of a moving character. Treat those as design checks, not measured engine limits.
rcore Addon Generator: image, model placement and export
The Addon Tattoos site currently advertises PNG, JPG and WebP input, a 3D placement preview, male and female model configuration, and export of a structured FiveM tattoo resource. Those are the tool’s published capabilities, not results Magnate has validated. Follow the current creator instructions for your account and export.
Keep position, scale and rotation with the design record. rcore’s add-on FAQ describes predefined or community positions and editable male/female position fields. It identifies X as horizontal and Y as vertical. Check each intended model rather than assuming one placement transfers unchanged.
For a missing shop entry, the same FAQ routes readers to its tattoo configuration troubleshooting. An asset existing in an exported resource and the shop knowing how to list it are separate conditions. Keep the generated configuration with the matching package version.
Durty Cloth Tool: generate configuration for the intended script
Durty Cloth Tool’s Dynamic Config Builders page lists target configurations for rcore_tattoos, xnTattoos, qb-tattooshop, ESX-TattooShop and illenium-appearance. It describes selecting the relevant builder in Build Options before building the project.
The maintainer explicitly distinguishes generating configuration from guaranteeing structural correctness or optimization. It also notes that generated data may need merging or references in the existing target configuration. Preserve the installed configuration and follow the script creator’s integration instructions rather than replacing it blindly.
Install and register one small test design first
Use an isolated staging copy and the smallest useful test pack. Retain the creator’s resource structure and record which file belongs in which resource. If the generated configuration references identifiers, preserve those exact identifiers rather than renaming files without updating their consumers.
Add the target-script configuration through its documented route, then inspect the first relevant error. Verify that the design appears in the intended list, that selecting it produces the expected preview and that the normal completion action saves it. A successful preview alone should not close the acceptance task.
Run a placement and persistence acceptance check
The table below is an original proposed test plan. Define the expected result before each attempt and record the actual model, package version and target script. Keep failures as well as passes so a maintainer can reproduce the issue.
Check placement with a neutral view and the clothing combinations your project actually uses. When a garment covers the design, distinguish intended occlusion from a missing tattoo. Do not alter several appearance resources at once merely to make a single screenshot look right.
| Check | Expected result to define | Evidence to retain |
|---|---|---|
| Menu registration | Design appears in intended category | Entry name and generated configuration |
| Supported character model | Correct body area and readable scale | Model and placement values |
| Other supported model | Deliberately configured placement | Separate comparison screenshot |
| Normal save action | Selection is retained as intended | Before/after saved state |
| Reconnect | Expected tattoo is restored | Loaded appearance and first error |
| Clothing or appearance change | Intended design remains or is covered normally | Exact outfit/action and result |
| Removal workflow | Selection is removed through supported UI | Saved and displayed state |
Diagnose the failing layer
If no entry appears, inspect registration and category configuration before changing the artwork. If the entry exists but the preview is wrong, retain the identifier and placement evidence. If preview works but reconnect loses it, investigate the target appearance system’s save and restore route.
Use the Illenium appearance guide for that system’s configuration boundaries and the clothing packs guide for asset-versus-menu distinctions. Include the tool version, generated package, target script and smallest reproduction when asking the appropriate maintainer for help.
Scope and handoff
Deliver the editable artwork, permitted-use information, exported resource, integration notes and acceptance record together. Describe the exact supported setup rather than marketing the result as compatible with every FiveM framework.
Magnate reviewed the linked creator documentation on November 7, 2026. No tool account was created, artwork uploaded, software installed or runtime test performed. These are GTA V/FiveM workflows and do not establish GTA VI tattoo or mod support.
Questions, answered.
Does a PNG automatically become a working FiveM shop tattoo?
No. Use a supported export route and integrate its resource and configuration with the intended tattoo or appearance script.
Can I reuse the same placement for male and female models?
Do not assume it fits unchanged. Configure and check every intended model separately.
Does a generated config guarantee optimized assets?
No. Durty Cloth Tool distinguishes configuration generation from structural and optimization correctness.
Sources & editorial notes
Source review: November 7, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.
- rcore — Add-on tattoos Reviewed November 7, 2026. Creator-described workflow; no upload, export or game-runtime test performed.
- rcore — Addon Tattoos generator Reviewed November 7, 2026. Creator-described workflow; no upload, export or game-runtime test performed.
- Durty Cloth Tool — Dynamic Config Builders Reviewed November 7, 2026. Creator-described workflow; no upload, export or game-runtime test performed.
Published by an independent editorial brand. Read our editorial standards.