> For the complete documentation index, see [llms.txt](https://legacydmc.gitbook.io/chaser/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacydmc.gitbook.io/chaser/fundamentals/the-chaserfirststartup-command.md).

# The "chaserfirststartup" command

As soon as you download and install chaser on your server from TEBEX go into your server.cfg, and add to ace perms the following:

```
add_ace group.admin command.chaserfirststartup allow
```

or to whatever group you utilize, this step isn’t mandatory, but highly recommended in order to prevent players from utilizing this command.

Once that is done, run the script.

When in game, go into a clean area, without traffic or peds, and run the command:

```
“chaserfirststartup update”
```

This command will process and calculate all necessary chaser pre-calc info for all compatible models in your server.

You’ll need to run this everytime new vehicles are added in order to keep compatibility, else new vehicles might break features.

Once the command has been processed you’ll see a new file named 

“globalvehdata.lua” in your config folder, was created or updated.

and now, you’re ready to use chaser!

## Arguments:

The "chaserfirststartup" command has 3 possible arguments:

### update:

When calling with the argument "update", the command will only process vehicles that require an update, when calling with this argument, the settings stored in "globalvehdata.lua" will not be overwritten.

### overwrite:

When calling with the argument "overwrite", the command will process all vehicles, and overwrite the "globalvehdata.lua" entirely, losing all saved settings.

### none:

When calling without an argument, the command will process all vehicles, and overwrite the "globalvehdata.lua" entirely, losing all saved settings.


---

# 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://legacydmc.gitbook.io/chaser/fundamentals/the-chaserfirststartup-command.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.