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

# Introduction

{% hint style="danger" %}

## WARNING

1.0 cinematics are not compatible with the 2.0 version.
{% endhint %}

{% hint style="warning" %}
This wiki is still under construction.
{% endhint %}

Cinematic Studio is a powerful tool that allows you to create intricate cinematic cutscenes. \
An advanced cutscene tool by LoneDev (originally by CraterHater)

It allows you to create **smooth camera paths** which allows you to create sweeping shots of scenery or of NPC scenes. \
This plugin allows you to have an unlimited amount of characters in your cutscene. \
These can be any type and can be animated via a **motion capture** **system**. \
This means you can act out the behavior of the NPCs in order to give them the exact motion you want them to have.

For a quick showcase please take a look at the example cutscene visible on the plugin page description.

**This plugin is actually quite self-explanatory so the best way to learn is by simply messing around with the editor in game and editing the files.**


---

# 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://lonedev.gitbook.io/cinematicstudio/cinematicstudio-v2/introduction.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.