> For the complete documentation index, see [llms.txt](https://docs.cheddah-development.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheddah-development.net/plugin-documentaion/cozy-claims.md). # Cozy Claims CozyClaims is a native land-claiming plugin for Paper servers. Players protect land, organize multiple areas under one claim, invite members with clear roles, and control common protection rules from polished inventory menus. ### Highlights * Native claims with no required claim plugin * Visual two-corner Claim Mode with boss-bar guidance * Multiple land areas per claim * Claim resizing, merging, removal, and deletion * Accrued and administrator-granted claim blocks * Access, Containers, Build, and Manager member roles * Configurable PvP, explosions, fire, mobs, containers, entry, portals, and more * Claim teleportation and client-side border previews * Claim names, icons, pinning, search, and sorting * Native claim bans and safe player ejection * Administrator inspection, teleportation, borders, bypass, and balance tools * Optional import path from GriefPrevention, GPFlags, and BanFromClaim * Optional Oraxen display-item support {% hint style="info" %} CozyClaims requires **Paper 26.2** and **Java 25**. {% endhint %} Start with Installation, then follow the Quick Start. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cheddah-development.net/plugin-documentaion/cozy-claims.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.