Documentation

Macros are inline directives you drop into your Luau to control obfuscation function by function. They come in two forms: call-style like MV_VM(function() ... end) and --! comment directives placed above a function:

--!mv:vm
local function verify(pw)
  return pw == "s3cret"
end

Using comment directives offers a seamless alternative to inline directives that aims to fit better with modern Luau language servers. This allows you to obfuscate the exact same script you use to debug against without annoying Luau type check warnings or a SDK header.

Some macros are tailored specifically for you to optimize performance, such as MV_OMIT:

--!mv:omit
local function handlePreRender(deltaTime)
    local fps = math.round(1 / deltaTime)
    label.Text = "FPS: " .. fps
end
game:getService("RunService").PreRender:Connect(handlePreRender)

-- or --

game:getService("RunService").PreRender:Connect(MV_OMIT(function(deltaTime)
    local fps = math.round(1 / deltaTime)
    label.Text = "FPS: " .. fps
end))

Code which is expected to run often (e.g. per game tick, render frame, or otherwise multiple times per second) may cause application freezes, drop FPS, reduce throughput, and increase latency even if optimized properly. Most of the time obfuscation is not necessary on these functions. If you do find yourself needing to still obfuscate a function which is too slow to virtualize, MV_CFF may be a better candidate:

--!mv:cff
local function GetTransparentRecursive(instance, partsTable)
	local partsTable = partsTable or {}
	for _, child in pairs(instance:GetChildren()) do
		if child:IsA('BasePart') or child:IsA('Decal') then
			table.insert(partsTable, child)
		end
		GetTransparentRecursive(child, partsTable)
	end
	return partsTable
end

GetTransparentRecursive(game.Workspace)

MV_CFF functions are completely lifted from virtualized functions and are emitted as a separate opaque state machine. This can give much better performance but comes at a cost of quality obfuscation.