All versions
2.0.1.b
Release
Create Waystones Recipes 2.0.1.b2 months ago 1,721
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
[2.0.1.b] - 2026-08-29
Added
- New Waystone Variants in Mechanical Crafting:
- Deepslate Waystone (
waystones:deepslate_waystone): Crafted using Andesite Casings, Deepslate Bricks, Ender Pearls, and a Warp Stone. - Blackstone Waystone (
waystones:blackstone_waystone): Crafted using Railway Casings, Polished Blackstone Bricks, Ender Pearls, and a Warp Stone. - End Stone Waystone (
waystones:end_stone_waystone): Crafted using Brass Casings, End Stone Bricks, Ender Pearls, and a Warp Stone.
- Deepslate Waystone (
- Mechanical Crafting Support for Waystones Items:
- Warp Stone (
waystones:warp_stone): Migrated to a custom 5×4 Mechanical Crafting grid (Amethyst Shards, Emeralds, Ender Pearls). - Warp Plate (
waystones:warp_plate): Migrated to a custom 5×4 Mechanical Crafting grid (Andesite Casings, Stone Bricks, Warp Dust, Flint). - Warp Scroll (
waystones:warp_scroll): Migrated to a custom 5×4 Mechanical Crafting grid (Gold Nuggets, Purple Dyes, Paper, Ender Pearl). - Return Scroll (
waystones:return_scroll): Migrated to a custom 5×4 Mechanical Crafting grid (Gold Nuggets, Purple Dyes, Paper). - Bound Scroll (
waystones:bound_scroll): Migrated to a custom 5×4 Mechanical Crafting grid (Purple Dyes, Gold Nuggets, Paper, Ender Pearl). - Warp Dust (
waystones:warp_dust): Converted to Mechanical Crafting recipe.
- Warp Stone (
Fixed
- Recipe Overwrite Priority:
- Updated
mods.tomldependency ordering forwaystonesandcreatetoordering = "AFTER". - Fixed an issue where default Waystones recipes overrode the custom Create mechanical crafting recipes due to mod/datapack load order.
- Updated
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:wQpKGqNJ:65NW162m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wQpKGqNJ:65NW162m"
}

