All versions
26.1
Release
HomeKeeper 26.13 months ago 80
Compatibility
Minecraft: Java Edition
26.2
1.21–1.21.1
1.20
1.19
1.18
1.17
Platform
Paper
Changes
HomeKeeper 26.1
A polish and UX pass. New menu, cleaner colors, safer deletes, more homes.
New
- Homes menu (
/hk homes) — paginated GUI, each home is a bed.- Left-click a bed to teleport.
- Right-click a bed to rename via chat.
- Automatic pagination, 21 homes per page.
- Delete confirmation —
/hk delhome <name>sends a chat message with clickable [Confirm] and [Cancel], so you can't wipe a home by accident. - Rename via chat — click rename, type the new name, press enter. Type
cancelor click rename again to abort. - Duplicate-location guard — you can't save two homes on the exact same block.
- Consistent theme — new color palette applied to menus and chat messages.
- Info panel in the homes menu with a quick reference to all commands.
Improvements
- Default max-homes raised from 3 to 10 (still configurable in
config.yml). - Help menu redesigned with a banner and categorized tips (Set, Teleport, Menu, Rename, Delete, Good to know) and a clickable Discord link.
- Friendlier command errors — typing
/hk sethomewithout a name now shows a helpful hint instead of the raw "Unknown or incomplete command" error. - Clearer feedback messages for saved, updated, deleted and teleported actions.
- Hidden
homekeeper:namespace, only clean/hkshows up in tab-complete.
Fixes
- Fixed the "Could not save rank.yml because rank.yml already exists" warning on startup.
Removed
/hk renamecommand — renaming is now done through the menu./hk cancelrenamecommand — cancel by clicking rename again or typingcancel.
Commands
| Command | What it does |
|---|---|
/hk homes |
Open the homes menu |
/hk sethome <name> |
Save your current spot |
/hk home <name> |
Teleport to a home |
/hk delhome <name> |
Delete a home (with chat confirm) |
/hk help |
Open the help menu |
/hk reload |
Reload configs (admin only) |
Community
Join our Discord: https://discord.com/invite/U5Qb7QGDTU
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:hjBb7PhG:V1Agg1lQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hjBb7PhG:V1Agg1lQ"
}

