Homes

## Installation

1. Put homes-plugin.jar into plugins/ on Paper/Spigot/Folia 1.20+ (tested on Paper 1.21.11/26.2, Spigot 26.1/1.8, Folia 26.2)

2. Restart the server.

3. Home data is stored in plugins/HomesPlugin/homes.yml.

4. To reload the config, run /home reload as an admin or from the console.

## homes.yml Structure

<player UUID>:

<home name>:

world: world

x: 123.0

y: 64.0

z: -456.0

yaw: 90.0

pitch: 0.0

Commands

Command	Description
/sethome <name>	sets a home at the current position
/delhome <name>	deletes a home
/home <name>	teleports to a home
/homes	opens the GUI (compasses, click = teleport)

## Permissions

Command	Description
/sethome <name>	sets a home at the current position
/delhome <name>	deletes a home
/home <name>	teleports to a home
/homes	opens the GUI (compasses, click = teleport)

Home Limit

plugins/HomesPlugin/config.yml:

home-limit: 10

A single global limit for everyone, with no permission groups — the only exception:

players with the homes.bypass node (op by default) do not have the limit checked at all.

Overwriting an existing home (/sethome with an already existing name) does not count towards the limit — only creating a new home beyond the limit is blocked.

The value is not cached in a separate field — it is read from plugin.getConfig() on every /sethome call. However, the config itself is loaded into memory only once on startup, so changes to config.yml still need to be applied via /reload confirm or a server restart.

## Known Limitations

• The home limit per player is global for everyone through config.yml (see above).

Group/permission-based limits are not implemented.

• Home names containing . cannot be safely used inside YAML keys in all cases — the Bukkit ConfigurationSection API handles this, but it is still recommended to disallow spaces/special characters in names at the command level if this is important.

• The home's world must be loaded on the server at the time of teleportation,

otherwise an error is displayed instead of causing a crash.