PlotsX is a lightweight land-protection plugin built for survival servers and shared player worlds. Players can claim an area, invite friends, configure protection rules, protect private containers, expand their land and teleport back to it without learning a large command set.

The plugin supports both traditional square plots and free-form chunk claims. Most player-facing management is available through /plot, while administrators keep control over worlds, limits, prices, permissions and integrations.

This README describes the current main branch and is intended to serve as the project overview for GitHub and plugin marketplaces.

✨ Features

Designed for player-owned worlds

PlotsX does not require a separate generated plot world. Administrators decide which normal worlds allow claims, and each plot covers the full vertical height of the world.

The plugin is suitable for survival bases, towns, farms, shared projects and other servers where players should claim land where they already play.

🧭 Classic plots or chunk plots

The claiming mode is selected by the administrator:

Changing the default mode does not delete existing plots. Classic and chunk plots remain protected and continue using their own expansion rules.

🛡️ Protection and ownership

PlotsX protects more than block breaking. Built-in flags cover common survival interactions including containers, redstone, pistons, PvP, animals, hostile mobs and utility blocks.

Members can be assigned roles with separate grants. Owners and administrators can control who may invite or remove players, rename the plot, change individual flags or transfer ownership.

Private containers add a second layer of access control. A chest, barrel or other supported container can be locked for one player and shared only with selected users even when other members have access to the plot.

💰 Expansion and economy

Plot expansion can be free or paid. When an economy is configured, PlotsX uses VaultUnlocked first and falls back to Vault.

Prices, multipliers and upper limits are configurable by the server. Expansion operations use a persistent operation journal so confirmed land changes, debits and refunds can be reconciled instead of relying on blind retries after a failure or disconnect.

Chunk plots are managed interactively: players can purchase neighboring chunks without leaving the expansion workflow and can remove eligible individual chunks from a dedicated GUI. The original anchor chunk cannot be removed, and removals that would split a plot into disconnected pieces are rejected.

🔌 Integrations

PlotsX works without these integrations for normal free claiming and protection.

📦 Compatibility

The current release line is 1.0.0. Compatibility recognition does not mean every possible server/plugin combination has been certified, so test upgrades on a staging server before deploying them to production.

Public marketplace links will be added here when their PlotsX project pages are published. Current development artifacts are available from successful Build Explorer workflow runs.

🚀 Quick start

1. Build or obtain PlotsX-Paper-<version>.jar and place it in the server's plugins/ directory.
2. Start the server once to generate the configuration and language files.
3. Configure allowed worlds and choose classic or chunks as the claiming mode.
4. Grant players the required plotsx.* permissions.
5. Restart the server after changing the claiming mode or installing integrations that participate during plugin startup.
6. Join with a normal player account and verify claiming and guest protection before opening the feature to everyone.

For players, the basic flow is intentionally short:

1. Stand in a free area and run /claim.
2. Confirm the claim in the GUI.
3. Run /plot to manage the new plot.
4. Invite a friend with /plot add <player> or use the member interface.
5. Expand the plot later when more space is needed.

💬 Commands and permissions

The administrator interface also supports listing and managing plots belonging to offline players. See the full command reference and permission reference for exact syntax and limit nodes.

🧩 Player interface

/plot is the central entry point. Depending on context, it opens the plot you are standing on or a list of your own plots.

From the panel, players can:

• inspect plot information and display its border;
• manage flags and members;
• rename the plot;
• teleport to it;
• set its teleport point from a safe position inside the plot;
• expand classic or chunk plots;
• remove eligible chunks from chunk plots.

On Paper 1.21.7+, renaming uses a native Minecraft dialog. Older versions retain the chat-input fallback, so one PlotsX codebase can support both modern and legacy interaction paths.

🗄️ Storage and reliability

PlotsX keeps protection data cache-backed for normal gameplay and supports SQLite, H2, MySQL, MariaDB and PostgreSQL for persistent storage.

Expansion purchases use a durable operation journal and transactional land commits. This makes failures easier to recover from and avoids treating an uncertain economy response as permission to repeat a debit blindly.

Administrators can export and import PlotsX data with /ptx export and /ptx import. Keep a database and plugin-data backup before upgrades or migrations.

📚 Documentation

The PlotsX wiki is maintained in both English and Polish. Language versions are kept side by side and cover the same user and administrator topics.

Developer documentation: API v2.

🛠️ Build from source

PlotsX uses Gradle and a Java 21 toolchain.

./gradlew clean buildAll

The installable server artifact is written to:

build/libs/PlotsX-Paper-1.0.0.jar

The compile-only API artifact is written alongside it as:

build/libs/PlotsX-1.0.0-api.jar

The API JAR is for integration developers and is not a server plugin.

🤝 Support and contributions

For support, join the SyntaxDevTeam Discord. Reproducible bugs can be reported through GitHub Issues with the PlotsX version, server platform/version, relevant logs and steps to reproduce.

Contributions and feedback are welcome. PlotsX is released under the MIT License.