Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated 3 weeks ago
All versions
0.8.1
Release
wWaypoints 0.8.13 weeks ago 41
Compatibility
Minecraft: Java Edition
1.20
Platform
Forge
Supported environments
Client-side
Changes
Features
- Added collapsible settings sections for easier navigation.
- Added notifications for waypoint sharing and wUtilities server restrictions.
- Added privacy protection against wWaypoints translation and keybind probes through signs and anvils.
- Added
/wutilityto view current wWaypoints server restrictions.
Fixes and Improvements
- Fixed waypoint sharing issues and improved reliability.
- Fixed waypoints disappearing after reconnecting to Realms (WWP-BR110, WWP-BR111).
- Fixed waypoint flickering, disappearance, and misalignment while moving or falling (WWP-BR106, WWP-BR109).
- Fixed missing death waypoints with immediate respawns and the VanillaTweaks Graves datapack (WWP-BR108).
- Improved waypoint transparency rendering with water and clouds (WWP-BR116).
- Improved label height and positioning to better match waypoint block models.
- Fixed broken enchantment glint (WWP-BR107).
- Improved wUtilities enforcement of server restrictions (WWP-BR113).
- Fixed Tweakeroo flexible block placement and hand restock compatibility (WWP-BR26).
- Fixed Ctrl/Alt shortcuts also triggering ordinary wWaypoints keybinds (WWP-BR93).
- Fixed Toggle Sneak inconsistencies and added support for modifier keys.
- Prevented waypoint shortcuts from triggering while typing in Flashback editor fields.
- Fixed missing or stale waypoint labels with Gnetum (WWP-BR101).
- Reduced unnecessary per-tick Essential compatibility checks (WWP-BR114).
- Reduced stuttering when opening waypoint and settings screens for the first time.
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:eQke7g17:6NWe6xJC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eQke7g17:6NWe6xJC"
}

