All versions
Release-7.5-26.2.x
Release
Waystones Release-7.5-26.2.x3 months ago 14
Compatibility
Minecraft: Java Edition
26.2
Platforms
Paper
Purpur
Spigot
Changes
๐บ๏ธ Version 7.5 โ Dynmap support
A long-standing gap among Waystones-style plugins closes: your teleportation points can now show up right on your web map.
Optional Dynmap integration
- If Dynmap is installed and enabled on your server, every waystone now gets a marker on a dedicated "Waystones" layer on the web map โ toggleable by players like any other Dynmap layer
- Marker color follows the same logic already used in-game: green for the Overworld, red for the Nether, purple for the End
- Clicking a marker shows the waystone's name and its description, if it has one (the same description set via
/waystone setdescription) - Zero setup required: if Dynmap isn't installed, this integration does nothing at all โ no error, no extra config, the plugin behaves exactly as before
- New
dynmap-enabled: truesetting inconfig.yml, in case you'd rather keep Dynmap installed for other plugins without exposing waystones on it
New command: per-waystone map visibility
/waystone setmapvisible <name> <enabled|disabled>โ hide a specific waystone from the map without removing it or touching its visibility in the in-game menu (handy for a secret base you don't want shown publicly)- Every waystone is visible on the map by default, matching how every other visibility setting in the plugin defaults to "on"
How it stays in sync
- Markers update instantly on creation, removal, and renaming โ no delay, no periodic refresh task running in the background
- The map is fully populated once at plugin startup from existing waystones, then kept in sync purely through these events from that point on
๐ท๏ธ Naming
- Minor version bump (7.4 โ 7.5) โ a self-contained addition, doesn't touch teleportation, permissions, or existing commands
- Generated jar:
Waystone-Release-7.5-26.2.x.jar - Still 26.2.x only, like every v6.x/v7.x release
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:OHYwSMgX:wrYzLluW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OHYwSMgX:wrYzLluW"
}

