DyHomes: Lightweight Homes, Warps and Spawn for Minecraft

DyHomes gives players named homes, public homes, warps, spawn and /back with claim-aware safety checks for Minecraft. One JAR for every server build.

Download DyHomes for Minecraft 1.20.6

Original name: DyHomes

Minecraft: 1.20.6

Loaders: Forge

FileVersionLoaderSize
DyHomes-1.0.0-BETA.jar1.20.6Forge148 КБDownload
DyHomes-1.0.0.jar1.20.6Forge199 КБDownload

DyHomes

Every survival server eventually runs into the same problem: players wander far from spawn, build something great, and then need a reliable way back. DyHomes solves that with a command-based homes plugin that keeps things simple. No GUI to click through, no database server to babysit, and no stack of separate JARs for different server builds. Just one file, a handful of commands, and a workflow your players already understand.

What DyHomes Does

At its core, DyHomes lets players set named homes and return to them, while server owners create warps and a central spawn. Version 1.0.0 is the first stable release, and it rounds out the package with public homes, a /back command, import tools for EssentialsX and HuskHomes, and web-map markers for BlueMap, Dynmap and squaremap.

The feature list is deliberately practical:

  • Named homes with rank-based limits and per-rank cooldowns
  • Public homes that other players can browse and visit
  • Warps and spawn handling managed entirely from commands
  • /back that returns you to your last teleport origin or death point
  • Destination safety checks before every teleport
  • Optional prices for homes, warps, spawn and /back
  • Five languages: English, Turkish, German, Spanish and Russian

Supported Versions and Server Builds

DyHomes ships as a single JAR compiled to Java 17 bytecode, and it runs on Bukkit, Spigot, Paper, Purpur and Folia. The release listing covers Minecraft 1.20.x through 26.x, with live verification performed on Purpur 1.20.4, Folia 1.20.4, Paper 26.2 and Spigot 26.3. On Folia, homes located in other regions are checked and reached on the correct region thread, while Paper and Folia both handle teleports asynchronously. That means you do not need to hunt for a special build when your server software changes.

Homes That Respect Claims

If you run DyClaim 1.1.0 or later alongside DyHomes, homes become claim-aware. Setting a home inside someone else's claim requires that claim's build right, and using the home requires the teleport right. Lose the trust and the home stays stored but cannot be used; earn it back and it works again. Public homes follow the same rule, so a shared home inside a claim closes automatically if the owner loses access.

Safe Arrivals

Builds change after a home is set, and a spot that was safe last week might be a lava pit today. Before each teleport, DyHomes checks the destination for standing room, lava and fire, and ground within a short fall. An unsafe destination is refused with a hint that players can add force if they truly want to go anyway.

How to Install DyHomes

Installation takes about a minute. Drop the DyHomes JAR into your server's plugins folder, start the server, then stand where players should arrive and run /setspawn. Create warps with /setwarp followed by a name. If you are migrating, run /dyhomes import essentials or /dyhomes import huskhomes once; nothing already stored in DyHomes is replaced, and the other plugin's files are only read. After that, adjust limits, warmup, cooldowns and prices in config.yml and run /dyhomes reload.

For server owners who prefer a hands-off setup, the foxygame.net launcher can install DyHomes for Minecraft in a single click and keep it updated automatically, so your plugins folder never drifts out of sync with the latest release.

Ranks Without a GUI

Home limits and cooldowns are handled through permissions rather than menus. The node dyhomes.limit.<n> sets how many homes a group may have, with the highest value winning, and dyhomes.limit.unlimited removes the cap entirely. Cooldowns work the same way through dyhomes.cooldown.<seconds>, where the lowest value wins. It is a familiar permission-based approach that fits neatly into LuckPerms or any other permission manager.

Commands Worth Knowing

Players will spend most of their time with /sethome, /home, /homes and /delhome. Server staff get /setwarp, /delwarp, /setspawn and /dyhomes reload. Public homes use /publichome to open or close a home, /phomes to browse what is available, and /phome <player:home> to visit. The short form /dyh stands in for /dyhomes, and /h works as a shortcut for /home. Home and warp names accept letters from any alphabet, digits, underscores and hyphens up to 32 characters, and they ignore case.

Data, Imports and Peace of Mind

Homes live in one small YAML file per player under plugins/DyHomes/homes/, with warps, spawn and language choices stored separately. Every file is written atomically, and a file that cannot be read is never overwritten; its homes stay read-only and the console tells you exactly which file to fix. Homes remember their world by UID as well as name, so renaming a world does not orphan anyone's base. Missing settings and message keys are added on startup and reload without touching your edits, and an invalid setting rejects the reload while the running configuration stays active.

Developers get an API through dev.dyhomes.api.DyHomesAPI for reading homes, warps, spawn and player limits, along with cancellable events for home changes and teleports. PlaceholderAPI support adds placeholders like %dyhomes_count%, %dyhomes_limit% and %dyhomes_warps% for scoreboards and tab lists.

Final Thoughts

DyHomes is built for administrators who want dependable teleport commands without dragging in a heavy framework. It covers the essentials, respects claims, checks destinations before sending anyone into danger, and stays out of the way until a player needs it. Whether you run a small SMP or a busy economy server, it is a sensible foundation for getting players home safely.