# Coding Scripts

## Tutorial

### IDE&#x20;

An IDE is a very important part of coding. It keeps your workspace clean and has syntax highlighting, which colors parts of your code to make it easy to identify them.&#x20;

Some IDE's good for coding scripts are&#x20;

* [VsCode](https://code.visualstudio.com/)
* [Atom](https://atom.io/)

I personally use VsCode because of its simplicity and customizability.

### Coding scripts

To start coding scripts you need to think about what you want your script to achieve. The majority of lua scripts made in fatality will need these things

* Render instance
* Config instance
* Menu instance
* Callback instance

Next, use this site's documentation to learn about how fatality's lua API works.

### Code snippets

Code snippets are used to auto-fill in code patterns

[Download snippets.](https://github.com/Jewlsxxx/Fatality-Luas/blob/main/fatal.code-snippets)\
Place that file in "C:\Users\YOURNAME\AppData\Roaming\Code\User\snippets"\
[Watch tutorial.](https://www.youtube.com/watch?v=uRdNvga3YyE)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://lua.legacy.fatality.win/getting-started/coding-scripts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
