Bukkit

Set Homes gives every player a menu of their homes. Left-click one to teleport. Right-click it to rename it, move it, change its icon, or delete it.

Full documentation | Report a bug | Donate | Discord

Why Set Homes

• A menu, or a list of commands. Homes live in a chest-style GUI. Players open it with /homes or by right-clicking the configured "Home Item".
• Every home gets its own icon. Pick any Minecraft item when you create a home, or change it later to whatever you are holding. A base, a mine and a farm stop looking identical.
• Rename, move and delete in-game. Right-click any home to manage it. Deleting always asks first, so nobody loses a base to a misclick.
• Teleports that do not kill you. Set Homes checks the destination and relocates you to the nearest safe spot rather than dropping you into blocks, lava, or a fall.
• Switch without losing anything. One command imports every home from EssentialsX or Set Homes v1, and shows you exactly what it will do before it does it.
• Per-rank home limits. Give donors more homes than default players with LuckPerms groups, or set one server-wide limit.
• Permissions you can change from the config. Every sh2.* node has a sensible default, and any of them can be moved in config.yml. No permissions plugin required.

Quick start

1. Drop the jar into your plugins folder and restart the server.
2. Run /sethome base where you are standing.
3. Run /homes and click it.

That is genuinely the whole setup. Player permissions default to granted, so your players can create and use homes the moment the plugin loads. See Permissions below if you want to change that.

Commands

In these tables, square brackets mark an optional argument. Anything else is required.

Names are optional on /sethome and /home. Leave the name off and both use a home called default. Home names are unique per player and ignore case, so base and Base are the same home.

All player commands, with their long forms

On /sethome, a second word that names a real item becomes the icon, and everything after it is the description. So /sethome base stone house creates base with a stone icon and the description "house". If you wanted the whole phrase as the description, put d in the icon position: /sethome base d stone house. The reply names the icon it chose, so there is never any guessing.

Admin commands

The three blacklist commands are one command with three aliases. Nothing you already type changes: /add-to-blacklist world_nether still adds that world, and /get-blacklisted-dimensions still lists them. Give worlds by the name the server knows them by, in lower case, which on a default setup means world, world_nether and world_the_end.

The three commands that take a player accept anyone who has saved homes, whether or not they are online. Tab completion only offers online players, because there is no lookup for every stored name.

Managing homes

Open your homes with /homes, or right-click the homes item. Then:

The management menu is controlled by sh2.manage-homes, which defaults to granted.

Changing a home's icon works the same way. Hold the item you want and click Set icon to held item:

Teleporting

By default players wait three seconds before a teleport fires, and moving cancels it, so a home is not a free escape from a fight. Set delay: 0 for instant teleports, or cancelOnMove: false to let players walk during the countdown.

Before it drops anyone anywhere, Set Homes checks the destination is safe to stand in. If a home has been built over, flooded with lava, or left hanging above a drop, the player is moved to the nearest safe spot instead, or the teleport is canceled and they are told why. Turn it off with teleportSafety: false.

Permissions

Nothing here needs a permissions plugin. Out of the box, every player can create, list, teleport to and manage their own homes, and operators get everything else.

Two bundles group the nodes, so you can move a whole role in one line:

Full permission list

These nodes are granted by the bundles, which is why denying a bundle takes its whole set away at once. Granting or denying an individual node works exactly as the table describes.

Note that sh2.move-home sits in sh2.player, not behind sh2.manage-homes. If you took sh2.manage-homes away to stop players relocating their homes, deny sh2.move-home as well or /uhome gives the ability back.

Changing permissions

Uncomment the permissions: block in config.yml and list the nodes you want to move:

permissions:
  sh2.manage-homes: false
  sh2.get-player-homes: true
  sh2.import-homes: op

Accepted values are true (everyone), false (nobody), op (operators only) and not-op (everyone except operators). A deny applies to operators too, so use op if you want a node gone for everyone except them.

You can name a bundle here as well as a single node, so sh2.player: false moves all eight player nodes in one line. There is no wildcard, so list whatever you want changed. If a line does not seem to take effect, check the server log at startup: anything the plugin could not read is named there.

This only changes a default. If you run LuckPerms or similar, an explicit grant or deny there still wins. The config block decides what happens to a player the permissions plugin says nothing about.

Take care with sh2.import-homes. Anyone who can run /import-homes source confirm can write homes for every player on the server, so granting it to everyone is a real risk.

With LuckPerms, the equivalent one-liner is /lp group default permission set sh2.player true. The server's own permissions.yml works too, and the README has an example of wrapping these nodes in a rank of your own.

Configuration

Settings live in plugins/SetHomesTwo/config.yml on your server, written the first time the plugin starts. Edit it in any text editor, save, then restart the server. There is no in-game reload command, so changes do not apply until the server comes back up.

The file is commented throughout, and every message the plugin sends can be rewritten in it. These are the settings most servers actually change:

Per-rank limits need LuckPerms and maxHomesType: groups.

That table is only the common settings. For the complete list, see default-config.yml, the file your config.yml is first written from. Every setting the plugin has is in there, commented in place.

Your config.yml is written once and never touched again. Installing the plugin, updating the jar and restarting the server all leave the file exactly as you last saved it, so a setting added in a later release will not appear in a file written by an earlier one. Anything missing falls back to its default, so nothing breaks, but you cannot change a setting you cannot see.

To pick a new setting up, copy the key out of default-config.yml into your file and restart. To start clean, rename your config.yml and restart. A fresh one is written with everything in it, and you can copy your old values across.

Coming from EssentialsX or Set Homes v1

Your players keep their homes. The old plugin does not even need to be running, because the importer reads its data files directly.

1. Stop the server.
2. Move the old plugin's jar out of plugins/ and keep it somewhere safe rather than deleting it. That jar is your way back. Leave its data folder exactly where it is: the importer reads plugins/SetHomes/ or plugins/Essentials/userdata/ and never writes to either.
3. Start the server. Set Homes creates its own folder and an empty database. No homes are visible yet, and the console tells you how many are waiting.
4. Run /import-homes sethomes (or /import-homes essentialsx). This is a preview only. It reports how many homes it would import and warns about any it would skip, and changes nothing.
5. Happy with the numbers? Run it again with confirm on the end.
6. Paste any settings the config report listed into plugins/SetHomesTwo/config.yml, then restart the server. Nothing is written there automatically, and there is no in-game reload, so a pasted setting does nothing until the server comes back up.

The jar has to move before the import, not after. Set Homes v2 will not start while a Set Homes v1 jar is still in plugins/. Both plugins provide /sethome, /home and /delhome, and v1 usually takes priority and wins those names regardless the load order.

You are reminded until you import. While plugins/SetHomes/homes.yml still holds homes and none have been imported here, every startup says so in the console, and anyone holding sh2.import-homes gets the same reminder in chat on join. Both stop for good once any home exists here.

Existing homes are never overwritten, so re-running the import is always safe. Homes in worlds that no longer exist are skipped with a warning naming the world.

Set Homes v1 told base and Base apart, while home names here ignore case. A player holding both keeps both: the second is imported under the next free name, so Base arrives as Base2, named in the report and the server log.

You can go back at any time. The old plugin's data folder is never written to, so rolling back is mostly putting its jar back and taking the Set Homes jar out.

Coming from Set Homes v1, the world blacklist comes across too. The migration guide on GitHub has the full rollback steps and maps every v1 command, permission and config setting to its v2 equivalent.

Requirements

• Paper or Spigot 1.21+
• Java 21, which Minecraft 1.21 servers already require
• Optional: LuckPerms, only for per-rank home limits

Changelog

Every release is listed on the Files tab of this page, and in the changelog on GitHub.

Support

The README on GitHub has the migration tables and an FAQ covering the questions that come up most.

Found a bug or want a feature? Open an issue on GitHub. It gets seen faster than a comment on this page.

Source | Report a bug | Donate | Discord