> 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/events.md). # Events This section covers how scripts can interact with **Minecraft events** and **Script events.** Scripts can **listen to events**, **cancel or modify them**. This allows you to react to player actions, server behavior, or even your own plugin logic, all from within scripts. #### Topics you'll find here: * Listening to events (like `PlayerJoinEvent`, `BlockBreakEvent`, etc.) * Listening to script events * Cancelling or modifying default event behavior * Managing listeners and cleanup to avoid memory leaks or duplicate triggers Whether you're trying to react to a block being placed, cancel an entity from spawning, this section gives you the tools to do that cleanly. {% hint style="info" %} Events are central to building reactive and dynamic behavior. If you're writing any kind of automation or gameplay logic, chances are you'll be using events. {% 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/events.md?ask=&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.