Enter at least two characters

Console-only private locations

Docs version: v1.2.1

All /katpa location commands (also available as /katap location) are console-only, including list. Even OP players cannot use them. Locations belong to a single player UUID and are grouped by group/name; they are separate from /home and public /warp.

/katpa location save <player> <group> <name>
/katpa location list <player> [group]
/katpa location tp <player> <group> <name>
/katpa location delete <player> <group> <name>
  • save records the current location, world, precise coordinates, orientation, and real backend of a player online on this console's backend. Saving the same player's group/name again replaces it.
  • list shows locations grouped by group, optionally filtered; list and delete also work for offline players previously seen on any backend using this KaTpa database. Offline names are resolved from the database, not this backend's player cache.
  • tp moves an online player on this backend to their own saved location. Both local and cross-server teleports warm up first, showing the group/name and remaining seconds in the player's ActionBar with countdown sounds and particles. Movement, damage, or disconnect cancels the warmup; successful arrival plays the teleport sound and shows an ActionBar message. Cross-server teleports use KaProxy arrival acknowledgements and wait for authentication on the destination. Console teleports have no fee or warp permission check. “Requested” does not mean a cross-server arrival has already completed.

Configure the independent warmup with modules.location.warmup, warmup-seconds (default: 3), sounds, and particles in config.yml. The effects use the global sounds.countdown, sounds.teleport, and particles.warmup definitions. Customize ActionBar messages using location-warmup ({group}, {name}, {seconds}), location-success, and location-arrived in the language file; cancellation messages are shared with other teleports. Configuration version 10 backs up the old config.yml and preserves existing settings, including custom world overrides under modules.rtp.worlds. Existing custom language files without these keys use the bundled defaults.

  • delete removes only that player's named location within the group. Group/name are 1–64 characters without spaces, looked up case-insensitively.

Data lives in the private_location table of the configured SQLite or MySQL storage backend. Use a shared MySQL database to access the same saved points across backends. Cross-server travel also requires KaProxy's modules.back.enabled: true and compatible KaTpa versions on both backends. Run save and tp from the backend where the player is currently online; the Lobby console cannot directly target someone online on another backend. No custom plugins/KaTpa/gui/ files are overwritten.