> For the complete documentation index, see [llms.txt](https://unknown-56-works.gitbook.io/luigiscreen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unknown-56-works.gitbook.io/luigiscreen/getting-started/installation.md).

# Installation

## 1. Stop the server

Do not replace LuigiScreen while Paper is running. Native FFmpeg libraries remain loaded until the Java process exits.

## 2. Install MapEngine

Place the compatible MapEngine JAR in:

```
plugins/
```

Required version for the current LuigiScreen alpha:

```
MapEngine 1.8.12
```

## 3. Install LuigiScreen

Place the LuigiScreen JAR in:

```
plugins/
```

Keep only one LuigiScreen JAR. For example, remove `LuigiScreen-1.1.0-alpha.11.jar` before adding `LuigiScreen-1.1.0-alpha.12.jar`.

## 4. Start the server

The first start creates:

```
plugins/LuigiScreen/config.yml
plugins/LuigiScreen/messages_cs.yml
plugins/LuigiScreen/messages_en.yml
plugins/LuigiScreen/media/
```

## 5. Verify startup

The console should show both plugins enabled without an exception:

```
Enabling MapEngine v1.8.12
Enabling LuigiScreen v1.1.0-alpha.12
```

Run:

```
/plugins
```

MapEngine and LuigiScreen should both appear enabled.

## 6. Choose a source

Continue with [Media sources](/luigiscreen/screens-and-streaming/sources.md). Only RTMP sources need a [network setup](/luigiscreen/screens-and-streaming/overview.md).

## Updating

1. Stop Paper completely.
2. Back up `plugins/LuigiScreen/`.
3. Remove the old LuigiScreen JAR.
4. Add the new JAR.
5. Start the server.
6. Check the console.
7. Run `/screen status`.

Do not use plugin hot-reload tools for native FFmpeg updates.


---

# 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://unknown-56-works.gitbook.io/luigiscreen/getting-started/installation.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.