Frequently Asked Questions

Last updated: June 14, 2026

What is Obscurau?

Obscurau protects Lua and Luau code from unauthorized reading and modification. The system takes your human-readable source code and translates it into a custom bytecode format. This bytecode executes inside our proprietary virtual machine, replacing the standard Lua execution model. This process prevents attackers from easily extracting your game logic or proprietary algorithms.

Why is Obscurau not free?

Running a secure, fast compiler requires dedicated server resources. Free tools often fund their operations by stealing user code or injecting malicious backdoors into the final output. We charge a fee so we can pay for server infrastructure, write new virtual machine opcodes, and guarantee that your code remains yours. You pay for the compute time, and we delete your source code immediately after processing.

Can someone reverse engineer my script?

Yes. Any software that runs on a user's machine can be reversed if the attacker has enough time and skill. Obscurau significantly increases the time required to analyze the code. Most attackers will abandon the attempt. However, obfuscation is not encryption. Do not hardcode sensitive database credentials or private API keys directly into your client-side scripts.

What environments do you support?

The Obscurau virtual machine targets Lua 5.1 and Roblox's Luau variant. It works in most standard environments. If your specific game engine or host application heavily modifies the C-side Lua API, the virtual machine might fail to initialize. We recommend testing your scripts in your deployment environment before distributing them to users.

Do you store my source code?

No. The compiler reads your uploaded script directly into system memory. It generates the bytecode, packages the virtual machine, and returns the final file over the network. Once the download completes, the server overwrites the memory buffer. We do not write your unencrypted scripts to any persistent storage drive.

How does the billing system work?

We use a pay-as-you-go credit system. You purchase a credit balance upfront. Every time you compile a script, the system deducts credits based on the input file size and the specific security parameters you choose. Heavy obfuscation settings require more processing time and cost more credits.

Why did my script break after obfuscation?

Obfuscation renames local variables, strips debug information, and alters control flow. If your script relies on runtime reflection, specific variable names, or functions like getfenv(), the execution might fail. You must use our provided macro comments to tell the compiler which specific variables to ignore during the renaming phase.

How can I contact support?

If you encounter compiler errors or billing issues, email help@obscurau.net. Include your account email and the error code provided by the compiler. We respond within two business days.