> For the complete documentation index, see [llms.txt](https://openjs.wiki.gd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openjs.wiki.gd/getting-started/configdocs.md).

# Configuration file

{% hint style="info" %}
**A configuration file will only appear in the `plugins/OpenJS/config.yml` path after the plugin has been loaded at least once**
{% endhint %}

### Config.yml

The configuration file allows you to toggle various features to enhance the user experience and tailor OpenJS to your personal preferences. Explanations for the configuration values can be found in the comments:

```
# Prints in the console, whenever a javascript has been loaded
# by default, scripts that failed to load will print in the console
PrintScriptActivations: true

# Logs in the console, whenever a placeholder gets
# registered or unregistered
LogPlaceHolderActivity: true

# Logs in the console, whenever a custom command
# gets enabled/loaded or disabled/removed
LogCustomCommandsActivity: true

# Will send messages regarding errors and warnings to operators or users who have
# the permission to use the commands from OpenJS
BroadcastToOps: true

# Checks for updates and notifies admins and the console for an update
# you can disable this, but it is better to stay up to date
UpdateNotifications: true

# Automatically reloads scripts when they are changed
# Changes include: modifications, creations and deletions
# Scripts that are also newly created will be loaded automatically
AutoReloadScriptsOnChange: true

# If enabled, the Old class importer introduced in 1.3.0 will be used.
# It is recommended to keep this disabled,
# because the old importer does not translate Java classes
UseOldClassImporter: false

# opt-in/out from Bstats https://bstats.org/plugin/bukkit/OpenJavaScript/22268
AllowBstats: true

# enable/disable debug mode, only use if you encounter bugs or issues with OpenJS
# eats up a lot of performance
debugMode: false
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://openjs.wiki.gd/getting-started/configdocs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.