Engines & options

Every option the service exposes, and the combinations it accepts. The panel enforces these rules as you change them, so an invalid selection never reaches a build.

Lua v2

The current-generation Lua protector. It supports standard Lua, FiveM, and Roblox targets, with platform-specific version rules.

PlatformAccepted versions
lua5.1, 5.2, 5.3, 5.4, 5.5, luajit
fivem5.4 only
robloxluau only

Presets trade runtime speed and output size for progressively stronger transformations. Figures are indicative and vary with the input.

PresetApproachRuntime costOutput size
FastAOT-focused. Lightest runtime cost, smallest output.~1.2×~2×
BalancedHybrid of AOT and VM. The default trade-off.~1.8×~4×
SecureProtected execution with practical size and runtime costs.~3×~7×
ExtremeAdditional verification and smaller encrypted pages, with higher runtime costs.~5×+~10×+

local delivery embeds the protected program in the output. online delivery uses a revocable runtime key and always forces portable binding. Precheck binding is available only for local delivery.

Profile references are limited to 128 characters. The panel also corrects a version automatically when you change to a platform with a fixed runtime.

Lua

The legacy Lua engine supports Lua 5.1 through 5.5. Its options cover minification, anti-debug behavior, and FiveM compatibility. New accounts use Lua v2 for plain .lua files unless the default engine is changed in Settings.

JavaScript

JavaScript accepts .js, .mjs, and .cjs. Local mode produces a self-contained output; cloud mode produces a loader backed by an encrypted runtime bundle.

OptionPurpose
CompactRemove unnecessary whitespace and syntax.
Control-flow flatteningRestructure branch flow.
Dead-code injectionInsert non-executing branches.
Debug protectionAdd debugger resistance.
Disable console outputRemove console calls from the result.
Self-defendingDetect some forms of output modification.
String-array encodingMove and encode string literals.

JVM

JVM protection accepts .jar files. Minecraft mode keeps private-member renaming disabled for compatibility. Class renaming, exclusions, string encryption, and number encoding can be configured independently where the selected mode permits it.

Rename exclusions accept up to 256 entries, each no longer than 512 characters.