All versions
v1.1
Release
v1.15 months ago 85
Compatibility
Minecraft: Java Edition
26.1.2
1.21.11
Platforms
Paper
Purpur
Required content
Unavailable version
Unavailable version
Changes
New features
- All 10 variant textures are registered to geyser's custom-skulls.yml so Waystone items render correctly on Bedrock instead of appearing as Steve heads.
- Waystones can now be properly broken. When hitting the Waystone above the base, you'll see the barrel blink into existence and start to take damage. If you continue hitting then it'll break. If you stop before it's broken then it'll have the proper visuals reappear.
- Companion datapack — a small datapack will now be written to the world folder. This allows the plugin to hook into the public hooks available in Kawamood's Waystones datapack. The purpose is to properly provide Waystone destination icons without having to rely on timers. The removal of the timers eliminates a bug where the Waystone's inventory GUI would sometimes auto close.
Bug fixes
- Attack on the slab at ground level, the wall at the base, and the carpet on top now correctly cancels and restores visuals (was previously set to use only).
- The carpet visual on top is now skipped if a real block already occupies that position.
- The ground level slab and the carpet on top are now properly removed when a Waystone is broken.
- /pkcom set visuals true/false now immediately pushes fake blocks or restores real blocks for all online Bedrock players.
- The pk_waystones.json cache file had unnecessary fields removed, running /pkcom sync will update it.
- Teleport destination visuals now pushed for already-loaded chunks. Previously, if you teleported somewhere and then back within 10 seconds or if the Waystones were in the same chunk then the visuals wouldn't get updated.
- The wall at the base of the Waystone no longer disappears when the Waystone's inventory opens.
- Floodgate and Geyser-Spigot moved from softdepend to depend so the plugin won't try to load without them.
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:aYprFjGe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QQebISPv:aYprFjGe"
}
