0.3.0-beta+26.1.2
Compatibility
Required content
Changes
Wither Compass teleportation
Build matching 7 by 7 platforms from 49 blocks of a single beacon material, with a Lodestone on top of the centre block. Bind a compass to the destination, then charge it with one Nether Star at an anvil for one experience level.
- Start a journey by using the Wither Compass on the departure Lodestone. Other players join with an empty main hand. One charge covers the entire group.
- Iron carries players within 4,000 horizontal blocks. Gold adds animals and monsters and shortens preparation. Emerald also carries villagers and wandering traders. Diamond removes the distance limit within a dimension. Netherite connects dimensions. Additional Additions' rose gold also keeps players on their living mounts.
- Travellers keep their exact horizontal position and looking direction. Arrival height follows the destination covering, so bare, slab and carpeted platforms can connect.
- Platforms can be concealed beneath a decorative floor. Particles show the boarding area and selected travellers above the covering, with familiar Minecraft sounds throughout the journey.
- Blocked or interrupted journeys preserve the charge. Successful travel returns an ordinary compass that keeps its destination and name. Players receive three seconds of Blindness.
- Villagers preserve trades and inventory. Living mounts preserve their rider, saddle and equipment. Cross-dimensional creatures retain their identity and data.
The previous covered-campfire flight stations and subtle smoke remain included.
Built for Minecraft 26.1.2 and Fabric. Update both client and server. Additional Additions is optional and enables rose-gold platforms.
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:w51aXf75:ZVOYzpGA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:w51aXf75:ZVOYzpGA"
}

