> 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/interacting-with-external-plugins.md).

# Interacting with external plugins

This documentation header contains guide's on how to integrate external plugins ( for e.x [ProtocolLib](https://www.spigotmc.org/resources/1997/) ) into any script. Following this guide is crucial especially if you are trying to integrate a plugin that has no official support.

While you can integrate non-supported plugins into scripts, it is very complex. So here is a list:

{% hint style="info" %}
If **"Support Integrated"** is **"❌No"** but both **"Support Tested"** and **"Support Available"** are **"✅Yes"**, it means the plugin is fully compatible with OpenJS and can be used in scripts, but there is no built-in wrapper or pre-made API layer provided. In that case usage requires manual integration.
{% endhint %}

| Plugin         | Support Integrated | Support Tested | Support Available |
| -------------- | ------------------ | -------------- | ----------------- |
| PlaceholderAPI | ✅ Yes              | ✅ Yes          | ✅ Yes             |
| ProtocolLib    | ✅ Yes              | ✅ Yes          | ✅ Yes             |
| CoreProtect    | ❌ No               | ✅ Yes          | ✅ Yes             |


---

# 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/interacting-with-external-plugins.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.