Blacklist Import (illenium)

So moving across is a one-shot import of their table into ours, not a config option you point at their file. Paste the block, look at what it would do, then write it.

This page is about their blacklist config. Player skins and saved outfits are a separate tool, see Migration.

🖥️ The Import Page (the normal way)Copy Anchor Link

1. Open /shopmanager as an administrator.
2. Pick Blacklist Import in the left sidebar.
3. Paste their Config.Blacklist = { … } block into the box.
4. Press Check it.
5. Read the table it shows you, then press Import.

Nothing is written until the second press. Check it parses the paste and reports what it found; Import is the same read, committed.

What the preview tells youCopy Anchor Link

Above the table: how many garments in total, how many are blacklisted, how many are job-restricted, and every job name the config mentions. Any category name this resource has no slot for is listed as skipped rather than guessed at.

Long configs are summarised, the table shows the first 40 rows, and a line underneath says how many more will be imported.

Undoing an importCopy Anchor Link

The page counts how many of your locks came from an import and offers Remove imported locks. That deletes exactly those rows and the job rules under them. Locks you authored yourself in the LOCK EDITOR are untouched.

Fix the config, then import again.

💬 The Same Thing By CommandCopy Anchor Link

For a server that still has their resource on disk:

/migrateilleniumblacklist              -- find their config and import it
/migrateilleniumblacklist dry          -- print what it would do, write nothing
/migrateilleniumblacklist path/to.lua  -- read a specific file

With no path it looks at kartik-clothing/data/illenium_blacklist.lua first, then illenium-appearance/config.lua and the usual places under it.

-- Or from any server script
local result = exports['kartik-clothing']:migrateIlleniumBlacklist({ dry = true })
print(result.total, result.blacklisted, result.restricted)

🔁 What Their Entries BecomeCopy Anchor Link

[!IMPORTANT] jobs in their config is a whitelist, not a list of who is banned, it names the people who may wear an otherwise-blacklisted garment. It is carried over that way. An entry whose jobs key names nobody is treated as a plain blacklist.

Their category names map onto GTA component and prop ids, upperBody is component 3, jackets is 11, hats is prop 0, and so on. hair is component 2 whether it sits inside components or beside it.

Both shapes are accepted, including mixed in one category:

Config.Blacklist = {
    male = {
        hair = {12, 13},              -- a plain list
        components = {
            masks = {
                {
                    drawables = {298, 297, 296},
                    jobs = {"hadesautos", "wagner"}   -- only these two jobs
                },
            },
            upperBody = {5, 6, 7},    -- nobody
        },
        props = {
            hats = { { drawables = {1, 2} } },
        },
    },
}

You can paste the whole Config.Blacklist = { … } assignment, or just the table inside it. Anything else in the file is ignored.

🛈 Worth KnowingCopy Anchor Link

• Importing the same config twice changes nothing. Garments are keyed on kind + id + drawable + texture + body, so the second run lands on the same rows, no duplicate locks, and the job rules under each one are replaced rather than appended. Import as often as you like.
• Re-importing an edited config overwrites in place. Raise police from grade 0 to grade 3, flip a blacklisted garment to a job, or the other way round, and the existing lock is updated. Garments you removed from their config are not removed here, though, a shrinking config leaves the old locks behind. Use Remove imported locks and import again for a clean slate.
• Every row it writes is stamped created_by = 'illenium-migration'. That is what Remove imported locks matches on.
• No hint text is written. The hint is the line a player is shown when a garment is refused, so it belongs to whoever authored the lock, an imported lock falls back to the default "You are not entitled to wear this." A hint you write by hand in the LOCK EDITOR survives a re-import.
• Locks apply immediately. A player already wearing a garment they are no longer entitled to loses it at their next save or spawn.
• An import wins over a lock you authored by hand for the same garment: its blacklist flag and rules are replaced by the config's. That row keeps your created_by stamp, so Remove imported locks will not take it away afterwards, it stays, carrying the imported rules. If you have hand-tuned locks, import first and tune second.
• Their config is parsed, not executed. The Blacklist table is cut out by matching braces and compiled on its own in an empty environment, so nothing else in their file runs.

🩺 If Something Goes WrongCopy Anchor Link

➡️ After ImportingCopy Anchor Link

Everything is now an ordinary garment lock. Edit, extend or remove any of them in the LOCK EDITOR, see Item Locks & Restricted Clothing, or from the console with Item Lock Commands.