All versions
2.0.8+neoforge+26.3
Release
TP HOME 2.0.8+neoforge+26.3last week 65
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
TP Home - Version 2.0.8
Release Date
2026-09-25
Inventory Improvements
- Opening the player inventory with E now closes the crafting recipe book by default, so it does not cover the TP Home button. Players can reopen the recipe book normally.
- The first time the inventory is opened with this mod installed, a client-side guide shows a real in-game inventory screenshot and points out the TP Home button. The guide can open TP Home directly.
- Dismissing the guide records its state in the client's
config/tphome-inventory-guide.seenfile. This is per installation, not per server or world; it does not repeat on later inventory opens. - Fixed blurred guide text and imagery in the 1.21.1 ports by preventing the screen background from being rendered over the guide. The screenshot is also prepared at its display resolution and drawn without unnecessary rescaling in all maintained ports.
Maintained Ports
| Loader | Minecraft | Version |
|---|---|---|
| Fabric | 1.21.1 | 2.0.8+fabric+1.21.1 |
| Fabric | 26.2 | 2.0.8+fabric+26.2 |
| NeoForge | 1.21.1 | 2.0.8+neoforge+1.21.1 |
| NeoForge | 26.2 | 2.0.8+neoforge+26.2 |
| NeoForge | 26.3 | 2.0.8+neoforge+26.3 |
Legacy ports and the Bukkit plugin are not part of this release.
Verification
- All five maintained projects pass
gradlew build. - The Fabric 1.21.1 guide was visually checked in a running client after the blur fix; the NeoForge 26.3 guide and its once-only behavior were previously checked in a running client. The other ports were build-verified, not individually visual-tested.
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:wDbytaJP:163VfMx5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wDbytaJP:163VfMx5"
}

