> 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/using-java-in-scripts.md).

# Using Java in scripts

This section contains guides on how to use **Java libraries and classes** directly within OpenJS scripts.

From importing internal Bukkit or Minecraft server packages to using external Java libraries (external `.jar` files), these guides walk you through all supported features and best practices.

***

#### What you'll learn here:

* How to import internal server packages and classes
* How to safely use Java reflection and static fields/methods
* How to import and use external Java libraries
* Limitations and workarounds of Java integration in OpenJS
* Tips for safe cross-version compatibility

Each subpage provides focused help on a specific aspect of Java usage.

{% hint style="info" %}
This section assumes you already know the basics of writing scripts in OpenJS. If not, check out the [Getting Started](/getting-started/installation.md) section first.
{% 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/using-java-in-scripts.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.