Documentation

Getting started

LuaFlux turns a readable script into one that only the interpreter can follow. It supports standard Lua and Luau, including Roblox scripts. Most builds finish in a few seconds.

1. Paste your script into the editor on the home page.
2. Pick a mode. If you are unsure, start with Ares.
3. Press Obfuscate, then copy or download the result.
4. Test the output in the same environment you plan to ship to.

Modes

The mode is the main choice you make for every build. Stronger modes produce heavier output, lighter modes run faster and stay smaller.

Options

Extra settings you can pass along with a build. Defaults suit most scripts.

Macros

Macros are special calls you place in your script. LuaFlux replaces them while it builds, so they never appear in the output. Use them to protect specific values or to control how a part of your script is handled.

Add shims so your script still runs

Outside of LuaFlux, a macro is just an undefined function. Declare a shim for each macro you use. A shim is a global function that returns its arguments, wrapped in a guard that is removed during the build.

if not FLUX_OBFUSCATED then
    function FLUX_ENCSTR(...) return ... end
    function FLUX_ASSUME(...) return ... end
    function FLUX_OPAQUE(...) return ... end
end

Values

Protection

Older spellings still work: FLUX_STRENC, FLUX_BUFENC and FLUX_NUMENC.

Performance

Example

local token = FLUX_ENCSTR("secret", 0x1234, userId)
local level = FLUX_ENCNUM(42, { [playerLevel] = 5, [gameId] = 9 })

if FLUX_ASSUME(game.PlaceId, 123456789) then
    print("ok")
end

local magic = FLUX_REWRITE(0xDEADBEEF)

Performance

Protection always costs something. The goal is to spend it where it matters and keep everything else fast.

Choose the lightest mode that fits

Heavier modes are for code you cannot afford to lose. Everything else runs better on Heavy, Normal or Weak.

Leave non sensitive code out

Interface code, rendering and physics rarely need protection. Keep them in a separate file and obfuscate only the logic that matters.

Wrap hot functions

FLUX_NO_VIRTUALIZE keeps a function protected while making it much cheaper to run.

local hot = FLUX_NO_VIRTUALIZE(function(a, b)
    return a + b * 2
end)

Tidy your source first

Repeated lookups get expensive once protected. Store them in a local before you build.

a.b.c.d.e.f.g.x = 1
a.b.c.d.e.f.g.y = 2
a.b.c.d.e.f.g.z = 3

local t = a.b.c.d.e.f.g
t.x = 1
t.y = 2
t.z = 3

Watch what runs every frame

Overhead shows up where code runs most. If it is not sensitive, keep it out, or wrap it in FLUX_NO_VIRTUALIZE.

• RenderStepped, Heartbeat and Stepped connections
• UserInputService handlers such as InputBegan and InputChanged
• Metamethod hooks like __index, __namecall and __newindex
• Tight loops with short wait() or task.wait() intervals
• Events that fire many times a second

Roblox

Instance attributes work as usual. SetAttribute, GetAttribute and GetPropertyChangedSignal need no changes in your code.

local part = workspace.Part

part:SetAttribute("Health", 100)
local hp = part:GetAttribute("Health")

part:GetPropertyChangedSignal("Health"):Connect(function()
    print("health changed:", part:GetAttribute("Health"))
end)

Write attribute names as plain string literals so they are protected with the rest of your strings. Names built at runtime are left as they are. When a value must depend on who is running the script, wrap the name in FLUX_ENCSTR.

local key = FLUX_ENCSTR("SessionToken", 0x99, userId)
part:SetAttribute(key, tokenValue)

Changelog

FAQ