Set Homes Plugin pre Minecraft 1.21.1, 1.21

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

• Drop the jar into your plugins folder and restart the server.
• Run /sethome base where you are standing.
• 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

Command What it does

/sethome [name] Creates a home where you stand.

/home [name] Teleports you to a home.

/homes Opens the homes menu.

/delhome name Deletes a home.

/uhome name Moves one of your homes to where you are standing.

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

Command Long form What it does

/sethome [name] [icon] [description] /create-home Creates a home where you stand. With no name it is called default.

/home [name] /go-home Teleports you to a home. With no name it goes to default.

/homes - Opens the homes menu.

/delhome name /delete-home Deletes a home.

/uhome name /move-home Moves one of your homes to where you are standing.

/list-homes - Lists your homes in chat. Click a name to teleport.

/give-homes-item - Gives you the item that opens the menu.

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

Command What it does

/set-max-homes [group] number (alias /setmax) Sets the home limit, per LuckPerms group or server-wide.

/get-player-homes player Lists another player's homes.

/home-of player home (long form /go-player-home) Teleports you to another player's home.

/delhome-of player home (long form /delete-player-home) Deletes another player's home.

/uhome-of player home (long form /move-player-home) Moves another player's home to where you are standing.

/blacklist add world... (alias /add-to-blacklist) Stops homes being set in a world.

/blacklist remove world... (alias /remove-from-blacklist) Lifts the restriction again.

/blacklist list (alias /get-blacklisted-dimensions) Shows which worlds are blacklisted.

/import-homes source [confirm] Imports homes from another plugin. source is sethomes or essentialsx. Dry-run unless confirm is given.

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:

Action What happens

Left-click a home Teleports you there

Right-click a home Opens the management menu below

Rename Opens an anvil prompt for the new name

Move home here Repoints the home at where you are standing

Set icon to held item The home's icon becomes whatever you are holding

Delete Asks for confirmation first

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:

Bundle Default Contains

sh2.player everyone sh2.create-home, sh2.go-home, sh2.list-homes, sh2.delete-home, sh2.teleport, sh2.give-homes-item, sh2.manage-homes, sh2.move-home

sh2.admin OP sh2.player, plus every admin and bypass node

Full permission list

Permission Default Allows

sh2.create-home everyone Creating homes

sh2.go-home everyone Using the go-home command

sh2.teleport everyone Actually teleporting to a home

sh2.list-homes everyone Listing homes in chat, and /homes

sh2.delete-home everyone Deleting your own homes

sh2.give-homes-item everyone Getting the menu item

sh2.manage-homes everyone Renaming, moving, re-iconing and deleting from the GUI

sh2.move-home everyone Moving your own home with /uhome

sh2.set-max-homes OP Setting home limits

sh2.get-player-homes OP Viewing another player's homes

sh2.go-player-home OP Teleporting to another player's home

sh2.delete-player-home OP Deleting another player's home

sh2.move-player-home OP Moving another player's home

sh2.add-to-blacklist OP Blacklisting a world

sh2.remove-from-blacklist OP Un-blacklisting a world

sh2.get-blacklisted-dimensions OP Listing blacklisted worlds

sh2.import-homes OP Importing from another plugin

sh2.update-notify OP Being told on join that a newer release exists

sh2.bypass-max-homes OP Creating homes past the configured maximum, whether the limit is server-wide or per group

sh2.bypass-blacklist OP Creating a home in a blacklisted world, moving a home into one, and teleporting to a home already in one

sh2.bypass-teleport-delay OP Teleporting with no countdown, and not being canceled by moving

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:

Setting Default What it does

delay 3 Seconds you must stand still before teleporting. 0 is instant.

cancelOnMove true Cancel the teleport if the player moves during the countdown.

teleportSafety true Relocate to the nearest safe spot instead of teleporting into danger.

maxHomeEnabled false Turn home limits on.