All versions
v1.2
Release
v1.23 months ago 411
Compatibility
Minecraft: Java Edition
26.2
26.1.2
1.21.11
Platforms
Paper
Purpur
Required content
Unavailable version
Unavailable version
Changes
New feature
- Bedrock recipe book support — added proxy recipes for Bedrock players, replacing the Java-side recipes with equivalents Bedrock can actually display. Includes a small resource pack the plugin generates and installs into Geyser's folder automatically, since Bedrock needs real icon textures to show these in the recipe book.
Bug fixes
- Torches and other attachable blocks/items can now be placed on any side of the Waystone by Bedrock players — this was previously unreliable, and even when it appeared to work, it was never actually confirmed server-side (the item would vanish if the player relogged).
- Sneaking now lets Bedrock players place a block/item on top of the Waystone, same as Java players.
- The carpet visual now properly restores when a block/item placed on top of the Waystone is removed.
- Waystone visuals now properly refresh for bystanders whenever any player (Java or Bedrock) interacts with the Waystone — previously only the interacting player's own client stayed in sync.
- The top of the Waystone can now be clicked through to open its inventory, matching how the sides already worked.
- Major bug fix (Linux) — fixed a bug where the plugin failed to write its datapack hooks to the world folder on certain server setups, which silently broke the plugin's integration with Kawamood's Waystones entirely.
- Major bug fix (performance) — fixed a bug where interacting with Waystones could force-load distant, unrelated chunks, causing severe lag (high MSPT) on servers with many Waystones spread across the map.
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:QQebISPv:ITtcPGPE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QQebISPv:ITtcPGPE"
}
