Developer guides
Start with the runtime you ship.
A protected file passing a syntax check is only the beginning. These guides show what to compare, which failures to watch for, and what to record before distributing a Lua build.
Build and release
How to obfuscate a Lua script walks through source backup, a Lite build, a same-runtime comparison and a release record. It is the starting point if you have not tested an obfuscated build before.
Roblox Lua obfuscation focuses on Luau syntax, event callbacks, host APIs and the gap between a command-line test and the place where your users actually run the script. It includes a release checklist and a warning about distribution rules for public assets.
MoonLoader and SA:MP covers LuaJIT, FFI, memory access, native hooks and versioned game environments. Use it to plan a compatibility test before sending a protected script to a community.
Language and debugging
Lua 5.1 vs Luau identifies syntax that will not travel between the two languages and explains why host APIs need a separate test even when syntax parses.
Fix an attempt to index nil gives a concrete lookup trace and distinguishes a missing value in the original source from a difference introduced by a protected build.
Use the tools with the guides
Script Doctor analyzes source without an account. It reports syntax and known runtime-sensitive patterns, but does not execute your script. The obfuscation workbench makes a free Lite build for a verified account. Save the original, output and build report together, then run the output in your own target runtime.
For details on the compiler's checks and source handling, read how hide.lat works. If you find a reproducible mismatch, a small example and the exact runtime version are more useful than a full private project.
Some guides may show ads to visitors who are not signed in. Signed-in readers see no ads. The source workbench has no ad script for anyone.
Guide index reviewed on . Individual guides are revised when a tested workflow or compatibility fact changes.