Luau

Alignment, not a course

1.3.6.0 tracks a Luau bump. Official language docs stay on Roblox properties.

Script errors

Execute can succeed while the script is wrong. Execute.

Luau is the language shape this documentation uses for the buffer: Lua-like syntax used by the Roblox platform. Alignment in 1.3.6.0 means the executor tracks a Luau version bump, not that we teach the language here.

This is not a Luau course. We will not reproduce Roblox API reference. Official language docs live on Roblox’s properties, not on xenokeyless.com.

Scripts you paste may be Lua 5.x mentally and still fail if they assume APIs this client does not give a third-party executor. That failure is not a missing key.

We do not host a standard library of “Xeno Luau snippets” for games. External files you keep are yours. Editor.

Changelog language about Luau alignment is the version pin. Do not mix a 1.3.55 note with a 1.3.6.0 ZIP. Release notes.

If execute succeeds and the script errors inside the experience, read the script. The executor did the only job this page describes.

Luau-shaped buffer, not a language school

1.3.6.0 tracks a Luau-shaped environment. That sentence is alignment, not a course. Official syntax, types, and API notes live on Roblox properties and the Luau site. Copying a 2019 Lua tutorial into the editor and calling it a Xeno bug is a category error.

Execute can return success while the script errors inside the experience, or while the script is written for a different place. The executor is not a compiler CI. Read the output your build actually shows. This documentation will not paste a sample exploit.

Language bumps in changelog can explain why an old script stopped parsing. They do not explain attach failure after a client update. Split those tickets. Changelog, offsets.

Do not expect this host to mirror every Roblox API, every instance method, or a typed definition file. Editor highlighting, if any, is convenience. Trust files you keep on disk. Editor.

Lua versus Luau in search queries still lands here because people type both. The product line is Luau. An Android “Lua executor APK” comparison is still a category error. Comparison, execute.

Print-first is still the right experiment: a short line you wrote, not a 2018 paste. If that fails, you do not have a Luau language problem. You have attach, offsets, or a closed client. If it succeeds, your large file’s errors are that file.

Loadstring-style patterns you saw on other executors are not a promise on this page. Believe the 1.3.6.0 workspace in front of you. Changelog notes language alignment; it does not paste samples.