> For the complete documentation index, see [llms.txt](https://docs-kr.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-kr.zep.us/zep-script-api/zepscriptapi/scriptplayer.md).

# ScriptPlayer

**ScriptApp** 클래스는 아래와 같이 2개의 카테고리로 구성되어있습니다

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

> 플레이어와 관련된 속성 값들 입니다.
>
> 맵 참가자의 이름이나 위치를 조회하거나, 캐릭터의 외형이나 이동 속도 변경 등 다양한 활용한 가능함 함수들이 모여있는 카테고리 입니다.

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

> 맵에 참가한 플레이어에게 UI나 사운드를 출력하거나, 특정 위치로 이동시키는 등 편리한 기능을 제공하는 함수들이 모여있는 카테고리입니다.


---

# 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-kr.zep.us/zep-script-api/zepscriptapi/scriptplayer.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.