Lua MTA VScode is an extension for Visual Studio Code editor to add code completion support, snippets, commands and more for the Multi Theft Auto San Andreas modification.
Please note, this is not a full LSP, which means, it doesn't have detection for variables, custom functions, and other general features of a LSP.
Lua MTA VScode brings autocomplete, hover and signature providers for various symbols that belong to MTA San Andreas.
The extension distinguishes between client, server and sharedside symbols, allowing you to see the only the ones that are available for the scriptside you are dealing with. This setting can be customized, allowing special keywords to be used to differentiate both scriptsides, by default, it uses the c_ and s_ syntaxes, as well as looking for "server" and "client" words in the file.
Every autocomplete and hover item describes what does the method do, its parameters, as well as a link to the MTA Wiki for full reference!
This extension provides useful snippets for coding your resource, for example, create a command handler, add a custom event and more!
The extension also provides snippets for the meta.xml file.
This extension adds the ability to scaffold a resource from the get go, simply call the respective command (Lua MTAVScode: Scaffold a new resource) and you will be able to generate a simple project from the get go. If you also have git configured, you can also create a new repository from the same command.
The extension has the following settings:
lua-mtavscode.serverSideFileKeywords: This setting allows the extension to scan the filename to determine if it belongs to a serverside script. It's an array of strings, and by default, it has the following:_s, server.lua-mtavscode.clientSideFileKeywords: This setting allows the extension to scan the filename to determine if it belongs to a clientside script. It's an array of strings, and by default, it has the following:_c, client.
The wiki is crawled and scraped with a script that allows to get the information out of the pages. This script is still in development and this is perhaps the most difficult part because the pages in the wiki are not totally coherent with each other (e.g: the title of the section where the syntax of the function is can be called "Syntax" or "Parameters", the note headers in the code can be either in one line or multiple, some pages have TODOs in it and/or other issues). The script is not yet fully perfect, so the output can vary from perfect to bad.
To add symbols manually, or to debug the script, please see here.