# Settings

```yaml
# Wards Main configuration. Version 1.0.3
# Created by Divios
# =========================================================
# Fields Explanation:
#   <chunk_display_seconds>:
#       - Amount of seconds the ward structure is displayed.
# ============================
#   <chunk_display_cooldown>:
#       - Amount of seconds until a player can request a ward display again.
# ============================
#     Although all the operations are done async and have great performance,
#     if exploited, it can cause some lag. Tweak this value depending on your player
#     base and server but 30 seconds should be fine
# ============================
#   <ward_check_cycle_seconds>:
#       - How often in ticks a ward checks in his given radius for players.
# ============================
#     This task is really optimized and done async. 20 ticks (1 sec) is a conservative value
#     that should work perfectly in most of the cases but don't be afraid to lower it.
# ============================
#   <ward_teleport_delay>:
#       - Ticks to wait until a player is teleported. If the player moves in the given time, the teleport is cancelled.
# ============================
# You must restart for changes to take affect when editing this file!
# =========================================================
chunk_display_seconds: 10
chunk_display_cooldown: 30
ward_check_cycle_seconds: 20
ward_teleport_delay: 0
```


---

# Agent Instructions: 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:

```
GET https://diviosx.gitbook.io/wards/configuration/default-files/config.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.