> For the complete documentation index, see [llms.txt](https://docs.lifev.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lifev.eu/einstieg.md).

# Einstieg

Loslegen mit einem LifeVisuals-Script: Escrow-Grenzen, Editierbares und Update-Ablauf.

Ein Produkt, vier Seiten: Übersicht, Installation, Konfiguration und API. Hier steht nur, was vor dem ersten Start deines Scripts passiert.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Escrow &#x26; Download</strong></td><td>Was verschlüsselt ist, was du editieren darfst und wie Updates laufen.</td><td><a href="/einstieg/escrow-und-download.md">Escrow &amp; Download</a></td></tr></tbody></table>

### In vier Schritten zum ersten laufenden Script

{% stepper %}
{% step %}

#### 1. Voraussetzungen prüfen

Auf der Installationsseite deines Scripts steht, was du brauchst — Framework, Datenbank-Bridge und optional HUD oder Menü.
{% endstep %}

{% step %}

#### 2. SQL einspielen

Die `.sql`-Dateien des Scripts in deiner FiveM-Datenbank ausführen — einmalig, vor dem ersten Start.
{% endstep %}

{% step %}

#### 3. `server.cfg` ergänzen

`ensure`-Zeile für dein Script eintragen — direkt nach den Systemen, die es erwartet.
{% endstep %}

{% step %}

#### 4. Config anpassen und testen

Config-Werte setzen, Server komplett neu starten, Console auf Fehler prüfen.
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lifev.eu/einstieg.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.