> For the complete documentation index, see [llms.txt](https://intellectualsites.gitbook.io/plotsquared/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intellectualsites.gitbook.io/plotsquared/features/vanilla-tags.md). # Vanilla tags ## What are "Tags"? Tags are part of Vanilla Minecraft itself. For example, vanilla block tags are used for various block properties, vanilla item tags are used for various item properties, vanilla advancement files are used for various advancements, vanilla recipe files are used for various recipes, and vanilla entity type tags are used for various mob properties. We decided to use these tags in our new flag system, this way you can easily set scopes of flags without having to add multiple values yourself. Tags are used in flags that accept block types, but are prefixed with `#`. As an example, the command `/plot flag set use #signs` will add the sign category to the `use` flag. This is equivalent to adding every sign type to the flag. A complete list of tags and the items contained in them, can be found in the [official wiki](https://minecraft.wiki/w/Tag#List_of_tags). --- # 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://intellectualsites.gitbook.io/plotsquared/features/vanilla-tags.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.