> 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/openjs-components/fflags.md).

# Feature Flags

**What is a feature flag?**

With a feature flag, you can add special flags **at the beginning of your script** to enable features that may bypass certain safety restrictions provided by the plugin.

{% code title="Example usage of a feature flag:" %}

```javascript
//!featureflagnamehere
```

{% endcode %}

**Available feature flags:**

<details>

<summary>//!loadmanually</summary>

With this feature flag placed at the top of your script, the script will not load automatically when the plugin starts or reloads. It will only be loaded if another script explicitly loads it, or if you load it manually using the `load` command.

</details>

<details>

<summary>//!waitForInit</summary>

With this feature flag placed at the top of your script, the script will yield (pause execution) until the plugin has been fully initialized. This should be used if you're calling the `LoadScript(scriptName)` function during plugin startup. In general, you should avoid manually loading scripts while the plugin is still starting or loading.

</details>

<details>

<summary>//!PlaceholderAPI</summary>

This feature flag indicates that the script will use PlaceholderAPI components, such as `PlaceholderAPI.registerPlaceholder()` `PlaceholderAPI.unregisterPlaceholder()` `PlaceholderAPI.parseString()`. In general, this allows the script loader to enable PlaceholderAPI support specifically for scripts that include this feature flag.

</details>

<details>

<summary>//!ProtocolLib</summary>

This feature flag indicates that the script will use ProtocolLib components, such as `ProtocolLib.registerListener` and `ProtocolLib.unregisterListener()`. In general, this allows the script loader to enable ProtocolLib support specifically for scripts that include this feature flag.

</details>

{% hint style="info" %}
Feature flags will be ignored if they have been disabled in the [configuration file](/getting-started/configdocs.md)
{% endhint %}


---

# 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/openjs-components/fflags.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.