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

# Configuration

## Editor GUI Configuration

{% hint style="info" %}
You can open the in-game editor with the command: **/shrine editor.**
{% endhint %}

### Create Shrine

To create a new Shrine, you can use the command **/shrine editor.** Once you have opened the editor, click on "**Create Shrine.**" After clicking, you will need to **enter the desired ID name** for the shrine, such as shrine-1.

<figure><img src="/files/JWX33zwS7nlTDaWlkd3X" alt="" width="324"><figcaption></figcaption></figure>

### Modify your Shrine

Congratulations! You have created your shrine! Now let's see what we need to do to modify it.

Open the /shrine editor. Once you have opened the editor, **click on "Modify Shrine."**

<figure><img src="/files/6GorUUyf2NjEGAmBIkg9" alt="" width="375"><figcaption></figcaption></figure>

After clicking, **select the shrine you want edit**

<figure><img src="/files/N520hxpX4rl2XbhF2L4T" alt="" width="287"><figcaption></figcaption></figure>

After clicking, you will have access to the selected Shrine editor, where you can edit all parameters of your shrine.

<figure><img src="/files/WaQWZGvTYZuY50qHAPQT" alt=""><figcaption></figcaption></figure>

## File configuration&#x20;

{% hint style="info" %}
Configuration files can be found in the plugins folder → Shrines → shrines.yml
{% endhint %}

Default configuration file with explainations:

```yaml
shrines:
  shrines-1: #SHRINES ID
    permission: 'shrines.shrines-1' #If player have the permission he can use the shrine
    item:
      completed:
        icon: STONE_BRICKS #Icon of the shrine teleport GUI
        displayname: '<yellow>Shrine 1 item' #Display name of the shrine
        lore:
          - '<rainbow>This is a custom lore!' #Lore of the shrine teleport GUI
        custom-model-data: 1000 #Custom model data of the shrine teleport GUI
        slots: # you can set the item for one or more slots
          - 0
          - 1
          - 2
          - 3
      incomplete:
        icon: STONE_BRICKS #Icon of the shrine teleport GUI
        displayname: '<yellow>Shrine 1 item' #Display name of the shrine
        lore:
          - '<rainbow>This is a custom lore!' #Lore of the shrine teleport GUI
        custom-model-data: 1000 #Custom model data of the shrine teleport GUI
        slots: # you can set the item for one or more slots
          - 0
          - 1
          - 2
          - 3
    displayname: '<yellow>Shrine 1' #Display name of the shrine
    region: 'shrines-1' #Region name of the shrine
    teleport-location:
      x: 0 #X coordinate
      y: 0 #Y coordinate
      z: 0 #Z coordinate
      world: 'world' #World where the shrine is
    completed: # message you get if you have completed the shrine
      welcome-message-chat: '<gray>Shrine shrines-1!'
      welcome-message-title: '<gray>Shrine shrines-1!'
      welcome-message-subtitle: '<gray>You have completed Shrine shrines-1!'
    unlocked:
      welcome-message-chat: '<gray>Congratulations! You have unlocked the Shrine shrines-1!'
      welcome-message-title: '<gray>Congratulations!'
      welcome-message-subtitle: '<gray>You have unlocked the Shrine!'
    incomplete: # message you get if you have not completed the shrine
      welcome-message-chat: '<gray>Welcome to the Shrine shrines-1!'
      welcome-message-title: '<gray>Welcome to the Shrine shrines-1!'
      welcome-message-subtitle: '<gray>Incompleted Shrine shrines-1!'
```


---

# 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.anotherlevel.it/documentation/shrine/configuration.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.