Key system

The current source bundles a new key-system window. Configure it inside Library:MakeWindow() or its CreateWindow alias. The main UI opens after a valid key is accepted. Closing the gate cancels startup and unloads the library.

local Library = loadstring(game:HttpGet("https://raw.githubusercontent.com/josediaz765/XLQP-UIS/main/xlqp%20gen1"))()

local Window = Library:MakeWindow({
    Branding = {Name = "My Hub", Icon = "home"},
    KeySystem = {
        Enabled = true,
        Title = "My Hub",
        Description = "Enter your access key",
        Key = {"XLQP-DEMO"},
        CaseSensitive = true,
        SaveKey = true,
        Folder = "MyHub",
        Theme = "Plant-Dark",
    },
})

Validation behavior

The gate trims whitespace around the entered key. Raw keys are case-insensitive by default; set CaseSensitive = true or KeyCaseSensitive = true for exact case matching. Prefer Key; Keys, CustomKey, CustomKeys, CorrectKey, and KeySettingsKey remain compatibility names.

Key accepts a string, number, list, map of accepted keys to true, function, or callable table. A function receives the trimmed key and returns true on success or false, reason on failure. An additional Validate, Validator, or Check callback receives (key, settings).

KeySystem = {
    Enabled = true,
    Key = function(key)
        if key == "XLQP-DEMO" then
            return true
        end
        return false, "This key is not valid"
    end,
    SaveKey = false,
}

Hashes may be configured through Hashes, KeyHashes, HashedKeys, or KeyHash. They are still checked after a failed raw-key match; the old AllowKeyHashesWithRaw rule no longer applies. Hash checks use the original trimmed key, so do not assume raw-key case normalization also applies to hashes. The gate then tries configured API providers.

Always configure a key or a provider. If neither is configured, the bundled gate falls back to the demonstration key key.

Key providers

API accepts one entry or a list. Providers, Services, Auths, and Auth are also collected. Each entry chooses a provider using Type.

Custom-provider context contains the entry's fields and Request, the runtime's HTTP request function when available. Return true for acceptance, or false, reason for rejection. Provider errors are caught and reported; they do not automatically accept a key. Provider credentials and service identifiers must come from your configured service.

Fields

Note, FileName, and Skip appear in older configurations. The new gate does not use Note as expiry enforcement or FileName to choose its key file. Skip is a saving compatibility flag, not permission to bypass validation.

Themes and helpers

Built-in themes: Carmim, Plant, Plant-Dark, Dark, Light, Violet, Midnight, Amber, Indigo, and Amethyst.

Saved keys and troubleshooting

The new window saves the accepted raw key to a deterministic filename derived from Folder and Title. It revalidates that key on the next launch. This differs from the previous signed key-set record and configurable FileName path.

If access fails, check Enabled, the trimmed key, CaseSensitive, custom validator return values, and provider connectivity. A phrase such as “Keys reset every 24 hours” is only a label; configure expiration in your provider or validator. If file APIs are unavailable, saving will not persist across launches.

See Window configuration, Full example, and AI agent.