All versions
1.0.0
Beta
Set Home for NeoForge 1.0.02 months ago 18
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Dedicated servers only
Changes
Set Home for NeoForge 1.0.0
- Added player homes for NeoForge servers.
- Players can set a default home with
/sethome. - Players can set named homes with
/sethome <name>. - Players can teleport home with
/homeor/home <name>. - Players can delete homes with
/delhomeor/delhome <name>. - Players can list their homes with
/homes. - Added a server config file to control the maximum number of homes per player.
- Added a readable homes tracking file so admins can inspect stored homes outside the game.
- Added OP-only admin commands to list, inspect, remove, clear, reload, and save homes.
- Server-side only; players do not need to install the mod client-side.
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:jrHN6wKA:9oZkDRho"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jrHN6wKA:9oZkDRho"
}

