Tags
Creators
Details
All versions
0.3.0
Beta
Beta v0.3.02 years ago 55
Compatibility
Minecraft: Java Edition
1.21–1.21.4
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added
- Warp menu contains filters to switch between discovered, favourites, and owned.
- Search can be used to narrow down the list of discovered warps.
- Warp sub-menu can be used to delete, favourite, or point the currently held compass to the direction of the warp.
- Waystones can have their appearance changed by clicking on the base of the block with a valid block.
- Waystones can also have their appearance changed on creation by placing down the lodestone on a valid block type.
- Valid block skins are displayed on the "View Available Skins" submenu of the management menu.
- Waystone skin types can be specified in the config with a required structure.
- Particles are displayed on the waystone depending on personal state. Bright green for owner, dull green for discovered, orange for locked, white for undiscovered.
- Particles are displayed to indicate the player being teleported and arriving at their destination.
- Sounds are played for vault creation and discovery.
- Sounds are played for the player being teleported and arriving at their destination.
- Sounds are played for changing the skin of the waystone.
- Config toggle to enable the functionality of using the compass to open the warp list menu.
- Config toggle to enable the functionality of using the waystone to open the warp list menu, moving the management menu to shift+right click.
- A sample-config.yml file is generated fresh on every launch to ensure that the most update to date base config format is known to administrators.
Changed
- The base of the waystone is now a slab rather than a barrier, making the space above the slab clickable to set the skin.
- Lists of players and warps are sorted alphabetically.
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:YHSL503C:GMJ3myVp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YHSL503C:GMJ3myVp"
}

