Skip to main content
This quickstart walks you through the core features of GLua Language Server in about five minutes. You will see how completions follow your values, how realms protect you from runtime errors, how net messages are validated end to end, and how to silence a diagnostic inline.

1) Completion follows your values

When you assign a known type, the extension suggests the right members. Type a player reference, a panel, or a loop variable, and the completion list updates automatically.

2) Your own functions

You can add type annotations so the extension understands your code, or let it infer types from usage.
With annotations, callers get completions and diagnostics for every parameter. Without them, the extension still infers types from how the function is used in your codebase.

3) Realms are not a suggestion

GLua runs on the server, the client, or both. The extension reads the file path and flags API calls that do not belong in the current realm.
The diagnostic appears immediately, so you know to move that code to a server file or use a net message instead.

4) Net messages checked end to end

When you define a net message sender and receiver, the extension compares the write and read signatures. If the payload types or order do not match, it reports a diagnostic.
The mismatch between WriteEntity and ReadUInt is flagged before you run the game.

5) Silencing a finding

If a diagnostic is a false positive for your project, you can suppress it inline with a comment:
Place the suppression comment on the line before the statement you want to ignore. The extension stops reporting the finding without affecting other diagnostics.

6) Commands worth knowing

Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and type GLua: to find these commands: Try running GLua: Show Net Message Graph on your project to see the net message analysis in action.