> For the complete documentation index, see [llms.txt](https://laot7490.gitbook.io/ltbridge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://laot7490.gitbook.io/ltbridge/getting-started/ide-setup.md).

# IDE Setup

LTBridge generates an `api.lua` stub file so your editor knows every `LT.*` function. A small VS Code setting avoids duplicate warnings.

## Autocomplete

After `ltbridge init`, open any `.lua` file in your resource. You should see autocomplete for calls like:

* `LT.Framework.GetPlayerName()`
* `LT.Inventory.AddItem(...)`
* `LT.Target.AddSphereZone(...)`

If stubs are missing, regenerate them:

```bash
ltbridge api
```

## VS Code — ignore bundled output

The watcher writes compiled modules into `ltbridge/modules/`. Your IDE might read those and show duplicate definitions. Add this to `.vscode/settings.json` (or say yes when `ltbridge init` asks):

```json
{
  "Lua.workspace.ignoreDir": ["**/ltbridge/modules/**"]
}
```

{% hint style="info" %}
Only ignore the **bundled output** folder. Keep `ltbridge/api.lua` — that's your autocomplete source.
{% endhint %}

## Tips

* Use EmmyLua-style comments in your own scripts for better hints
* Run `ltbridge list` to see installed and available modules
* Run `ltbridge why <module>` if you're curious why a module was included

Back to: [Quick Start](/ltbridge/getting-started/quick-start.md)