Tags
Creators
Details
21.0.7+fabric-1.21
Compatibility
Required content
Changes
-
Fixed Waystones sometimes restricting structure parts containing the word "waystone" from spawning (which caused the top of Towers of the Wild to sometimes be missing)
-
Fixed modifier screen accepting more than one dormant shard, resulting in all others being consumed
-
Fixed crash when DynMap integration is used
-
Fixed waystones from pre-1.21 worlds not migrating correctly to 1.21
-
Re-added JourneyMap support
-
Fixed missing particle texture in mossy waystones
-
Fixed sharestones not being right-clickable
-
Fixed crash with JEI on Fabric
-
Updated to Minecraft 1.21
-
Updated Mossy Waystone Texture
-
Changed scroll recipes to use ink instead of purple dye
-
Added colored portstone that allow teleporting to colored sharestones
-
Removed white and colorless sharestones
-
Removed Landing Plate (use a Warp Plate with Deepslate Shard instead)
-
Made warp plates rename-able like regular waystones
-
Added Dormant Shard, which can be plugged into a Warp Plate to attune it
-
Added Deepslate Shard, which can be plugged into a Warp Plate to fill in the hole
-
Changed shard placement to happen in-world for warp plates
-
Changed auxiliary warp items (warp modifiers) to be applied on arrival rather than departure
-
Made auxiliary warp items (warp modifiers) apply on regular waystones as well
-
Removed the slot UI for waystones and warp plates
-
Added new modifiers UI for waystones and warp plates for placing auxiliary warp items
-
Changed the waystone edit screen to be more intuitive
-
Removed Crumbling Attuned Shard for now because it doesn't have a crafting recipe yet
-
Removed Bound Scrolls for now because there is no way of obtaining them yet
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:LOpKHB2A:jqkMwqdk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LOpKHB2A:jqkMwqdk"
}

