# Create player-owned public warps with Player Warps

Olzie's Player Warps lets players publish destinations that other players can visit. Several unrelated plugins use similar names, so check the author before downloading or following commands. This guide refers to the Olzie Development project.

## Plan public destinations and preserve existing warps

Check the release's Minecraft compatibility, dependencies and edition before installation. If replacing an existing warp plugin, do not copy its database over this plugin's data. Use a documented importer or plan a migration with support while retaining the original records.

Stop the server and back up the plugin's data, affected worlds and external database if used. Warps depend on world names, server identifiers and locations. Renaming a world after creating warps can make valid records point somewhere unavailable.

Install using [the plugin guide](https://help.cloudexa-hosting.com/books/game-hosting/page/install-plugins-on-a-paper-or-purpur-minecraft-server). Start once, read Console for dependency errors, then stop before editing configuration. Review creation costs, visitor charges, teleport delay and available categories before players can create public destinations.

## Give a test player a small warp allowance

The documented allowance permission is `pw.limit.<number>`. For example, a temporary group can receive `pw.limit.1` for a one-warp trial. Do not give the unlimited wildcard just to solve an ordinary player's missing allowance. Use [LuckPerms groups](https://help.cloudexa-hosting.com/books/game-hosting/page/create-minecraft-ranks-and-inheritance-with-luckperms) to apply and inspect the intended membership.

1. Stand as the test owner in a safe, permitted area with enough standing room and no immediate fall or suffocation hazard.
2. Use `/pw help` to confirm the active command belongs to this plugin.
3. Create a clearly named trial destination with `/pw set MarketTest`, using the installed build's accepted naming rules.
4. Read any cost confirmation and inspect the published destination in the menu.
5. Join as a second non-operator account and use `/pw MarketTest` to test access and arrival.

Keep operator status out of the access test. It can mask permission, claim or protection restrictions that ordinary visitors experience.

## Check categories and charges

Category visibility and permission to assign a category are different controls. The official FAQ identifies `pw.category` plus the particular category permission for assignment. Review any category-specific viewing permission before assuming a missing menu item is a corrupted warp.

Record both players' money before and after a charged visit. Check whether the owner receives that charge and whether creation costs are separate. Publish clear prices to players; a free warp name does not mean every teleport is free under your configuration.

## Fix command and destination problems

If a subcommand such as lock is interpreted as a destination name, the command may be disabled in configuration. Check that before renaming warps or replacing the JAR. A missing category may instead be a menu configuration or permission issue.

For failed teleports, verify the destination world exists, its chunk can load and your claims plugin permits the intended visit. Do not disable protections globally to make one market accessible. Test at the destination with an ordinary account, and move a dangerous trial warp using the documented edit tools.

Keep the original data and send support the warp name, owner, version and exact message. Further reading: [commands and permissions](https://docs.olziedev.com/projects/playerwarps/commands) and [common configuration problems](https://docs.olziedev.com/projects/playerwarps/faq).

Looking for another plugin? [Browse the Minecraft plugin guide directory](https://help.cloudexa-hosting.com/books/minecraft-plugins/page/find-a-minecraft-plugin-setup-or-troubleshooting-guide).