SmartHomes
Named homes with a menu instead of a command list
SmartHomes gives your players named homes with a menu instead of a command list, on Paper 1.21.x. They set one, pick its icon, browse them all in a GUI and teleport with a click.
WHY SMARTHOMES
- Nobody loses a home to a typo. Setting a home on a name that already exists asks before it overwrites, and deleting asks before it destroys. That single window is most of your home-related tickets gone
- Homes have faces. Each one carries an icon the player chooses, so a browser full of homes is read at a glance instead of being a list of words
- Everything is in the menu. Teleport, rename, change the icon, make it public, set it as default or delete it — all from the home's own panel, with no commands to memorise
- Homes can be visited. A player opts a home in, and others can travel to it — shops, farms and builds worth showing, without you running a warp list by hand
- There is a way back. One command returns the player to where they teleported from, with the same warmup and cost rules as everything else
- Teleporting is not an escape. The warmup cancels on movement and on damage, so a home is not a panic button in a fight
WHAT YOU GET
- Named homes — as many as their rank allows, each with its own name and icon
- GUI browser — paginated, click to travel, right-click for the home's panel
- Home panel — teleport, set as default, rename, change icon, toggle visibility and delete
- Public homes — opt-in per home, visitable by anybody with the permission
- A default home — so the bare command always goes somewhere sensible
- The back command — returns to the last place they teleported from
- Confirmation windows — before an overwrite and before a deletion
- Per-rank limits — a permission node sets how many homes a player gets, highest wins
- Warmup, cooldown and cost — all optional, all configurable, each with its own bypass permission for your ranks
- Rename and re-icon in place — through the GUI, with a chat prompt for the new name
- PlaceholderAPI — home count, home limit and the default home, for scoreboards, TAB or chat
- English and Spanish included, and every string a player reads lives in messages.yml in MiniMessage format
HOW IT WORKS IN PLAYA player sets a home at their base and another at their mine, gives each an icon, and from then on uses the browser instead of remembering names. They make the shop home public so the server can visit it. Months later they try to set a new home on the name "base" by accident — and the window asks whether they really mean to move it, so their base stays where it is.CONFIGURATION
- config.yml — licence-free, default home limit, warmup length, cooldown, optional cost, whether public homes are allowed and the icons offered, every key with a comment beside it
- messages.yml — every string a player reads, so you can reword or re-colour the plugin without touching anything else