Database Reference
kartik-clothing creates and upgrades its own schema. There is no .sql file to import, on first start the resource runs its versioned migrations through oxmysql and records what it has applied in kartik_clothing_migration, so upgrading the script upgrades the database with it.
Every table is InnoDB / utf8mb4.
👤 Appearance & Outfits
kc_player_skins
The saved character. One active row per citizen.
| Column | Description |
|---|---|
citizenid | Owner. |
model | The ped model name on record, this is what the server validates a ped change against. |
skin | The full appearance snapshot as JSON. |
active | 1 for the live skin. |
updated_at | Last save. |
kc_player_outfits
Wardrobe presets.
| Column | Description |
|---|---|
citizenid | Owner. |
name | The outfit's display name. |
components / props | JSON arrays of the saved slots. |
🏬 Shops
kc_shops
Every shop location. Managed live through /shopmanager, there is no shop list in the config files.
| Column | Description |
|---|---|
label | Shop name, shown on the blip and in the UI. |
type | clothing, barber, tattoos, wardrobe, ped (Ped Changer) or job (Job / Faction store). |
coords / heading | JSON position and the ped's facing. |
blip | JSON { sprite, colour, scale, enabled }. |
zone | Optional JSON zone shape for the interaction area. |
categories | Reserved. Stored, but not read by the shop UI yet: every store shows the categories for its type. |
priceMultiplier | Multiplies every price in this shop, 1.5 for a luxury boutique, 0.8 for a discount store. |
job / gang | Optional access restriction. job is checked on purchase; gang is stored but not currently set by the UI or enforced. |
Eight shops are seeded on first start (Suburban, Ponsonbys, Binco, Discount Store, Herr Kutz, Bob Mulét, Ink Inc., The Pit). Delete or edit them freely in /shopmanager.
🎨 Design Studio
kartik_clothing_designs
One player-submitted garment.
| Column | Description |
|---|---|
citizenid | Author. |
base_id | Which Designer.Bases entry it was designed on. |
name | The design's name. |
layers | The layer stack as JSON. Uploaded images are stored on disk and referenced as asset:<ref>. |
preview_ref / preview_bytes | The artwork in the asset store. A design with no preview_ref can never bake. |
status | pending → approved / rejected → baked → live. |
reject_note | Why it was rejected. |
drawable / texture | The slot it baked into. |
remix_of | The design this one was remixed from, if any. |
reviewed_by | Who moderated it. |
kartik_clothing_design_owners
Who owns the right to wear a design. Cascades when the design is deleted.
💳 Credits & Tebex
kc_design_credits
One row per citizen: balance, plus a starter_granted flag. The flag is deliberately a flag rather than a comparison against Designer.Credits.StarterAmount, so raising the starter amount later does not silently re-gift existing players.
kc_credit_ledger
Every credit movement, delta, reason, package_id, transaction_id. transaction_id is unique, which is what makes a Tebex grant idempotent: a webhook Tebex retries cannot pay out twice. Manual admin adjustments carry a NULL transaction and are exempt.
kc_tebex_packages
The Tebex package → credit amount map, edited in /shopmanager. See Tebex Monetization & Design Credits.
🧑 Peds
| Table | Contents |
|---|---|
kc_ped_packages | Ped model → Tebex package. A row here is what locks a ped; the model is the primary key, so one package may bundle many peds. |
kc_ped_unlocks | Who owns what, citizen id, model, source (tebex / admin), consumable, consumed_at, revoked_at. |
kc_ped_changes | An audit row per ped change, written whether or not console logging is on. Surgery changes use context surgery. |
kc_ped_surgeries | One row per paid surgery, patient, surgeon, old/new model, price, and where the money went (paid_to). |
🔒 Item Locks
See Item Locks & Restricted Clothing.
| Table | Contents |
|---|---|
kc_item_locks | One locked garment scope, kind, item_id, drawable, texture, gender, blacklisted, hint. |
kc_item_lock_rules | Rules under a lock, job + min_grade, or citizenid. Rules OR together; cascades on delete. |
texture = -1 and gender = 'any' are sentinels rather than NULL, because MySQL treats NULLs as distinct in a UNIQUE key, a nullable column here would let the same garment be locked twice.
🧩 Compatibility
| Table | Contents |
|---|---|
kc_item_compat | An authored garment scope, arms_drawable / arms_texture, replaces_game, note. arms_drawable = NULL means "no opinion about arms". |
kc_item_compat_entries | One accessory paired with the row above, its own kind, slot, drawable, texture, required. Cascades on delete. |
🧾 Migration Bookkeeping
kartik_clothing_migration
Records which schema versions have been applied. Do not edit it by hand, deleting a row makes the resource re-run that migration on next start.
For importing data from another appearance script, see Migration.