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

# ScriptApp

**ScriptApp** class consists of the five categories below. You can see detailed information if you click the title of each category.

### [<mark style="color:purple;">Lifecycle</mark>](/zep-script/zep-script-api/scriptapp/lifecycle.md)

> An app’s lifecycle is a cycle where an app starts, runs, and until it ends. This category contains the functions that can create the app’s entire lifecycle by executing necessary actions in situations when the app starts, runs, and ends.

### [<mark style="color:purple;">Field</mark>](/zep-script/zep-script-api/scriptapp/field.md)

> This category contains the properties of an app where you can view the Space, maps, or user information or you can use the storage space.

### [<mark style="color:purple;">Event Listeners</mark>](/zep-script/zep-script-api/scriptapp/event-listeners.md)

> This category contains the functions that can detect and execute various events based on what happens in a map, such as players typing specified words or attacking a specific object.

### [<mark style="color:purple;">Callbacks</mark>](/zep-script/zep-script-api/scriptapp/callbacks.md)

> &#x20;This category has the functions that set conditions, such as when players press a key designated by the script developer or arrive at a specific point, and operate when the condition is satisfied.

### [<mark style="color:purple;">Methods</mark>](/zep-script/zep-script-api/scriptapp/methods.md)

> &#x20;This category has functions that provide convenient techniques such as UI display, moving or kicking users, and playing sound.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.zep.us/zep-script/zep-script-api/scriptapp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.