If you’re using FiveM’s FXServer you should add the following path to the libraries list: C:/server/citizen/scripting/lua where server is the folder which contains FXServer.exe
Really good work, glad to see something like this, I thought about this idea a while back but completely forgot about it, heh. Nice to see its presence though.
… but these are 90%+ the same as the codegen output from the repo itself.
for comparison:
might be these IDE tools don’t like Global. prefix aliasing or such but really it’s nearly the same as core codegen, and @return is what LDoc specifies, not @returns
Yeah… I hadn’t noticed the codegen output from the repo would spit out something I could use with my editor. I’d just been using the natives site (which is great btw) and decided I wanted something in my editor, noticed the JSON files and wrote the shitty generator.
I’m not sure if the Lua language server I’m using supports the Global prefix, but I do know it has issues with library files more then a 1000 lines, it makes it super slow unfortunately (hence why I am splitting them)
Please don’t take any offence to my tool, thank you for your work on FiveM and the tooling you’ve written around GTA.
For some reason I can’t for the life of me get this to work. All the FiveM functions aren’t declared and I don’t get any FiveM function Code Completion/Snippets when typing
I’ve installed the Lua extension by sumneko.
I go under the Extension Settings, find Lua > Workspace: Library and edit the settings.json
My entire settings.json is as follows:
I’ve reloaded VSCode many times (I even completely reinstalled VS Code, including deleting any configuration and settings files from AppData, etc, thinking maybe its an issue with VS Code itself)
I just can’t figure out whats wrong (and I reckon its something small that I’ve just completely missed). Anyone else run into this?
That’s really weird, Does auto complete work? If not - maybe try enabling the debug options in the extension or VSCode to see what’s going on under the hood. I don’t see anything obvious wrong, sorry