> For the complete documentation index, see [llms.txt](https://docs.utopiverse.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.utopiverse.net/main/discord.md). # Discord Information Information about our server discord Discord link: When joining the discord either link your account by running the command /dsb in game, or edit you server profile and set you nickname as your minecraft name (Bedrock users make sure to include \_). Why do we ask you do this? Simply put it makes it alot easier on staff when trying to help you if we know your username! Our discord has a variety of channels to offer such as: ┓Announcements ┓Giveaways ┓Changelogs ┓Polls ┓Applications ┓Rules ┓Server information ┓Tutorials ┓Monthly event winners ┓Social and off topic channels to talk in ┓A global channel connected to the server minecraft chat ┓Suggestions ┓Ticket creation ┓Bugs report ┓Voice channels ┓And more! --- # 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.utopiverse.net/main/discord.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.