> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/in-world/finding-events.md).

# Finding Events

Finding Events in Decentraland

The best way to meet new people in Decentraland is to attend events! Anyone in the community can submit an event to Decentraland's Event page, so you can discover a wide variety of events, from annual music festivals to weekly hang outs, if you stay updated.

**How to check current and upcoming events in Decentraland:**

* **Event Page:** Browse Decentraland's Event page at [decentraland.org/events](http://decentraland.org/events). You can jump directly to live events or RSVP to upcoming events to get an in-world notification when they start.
* **Genesis Plaza:** Check the Event board when you land in Genesis Plaza. It will display events happening soon.
* **World Map:** To see where live events are happening, open the map in-world and look for a red and white icon. Clicking on it will bring up event info and a jump in button.
* Follow Decentraland [**socials**](https://twitter.com/decentraland) or [**subscribe**](https://decentraland.beehiiv.com/subscribe) to the weekly newsletter to stay updated

Want to submit your own event? Learn more [**here**](/faqs/posting-events.md).


---

# 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://docs.decentraland.org/in-world/finding-events.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.
