Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated 2 months ago
All versions
1.0.5
Release
Custom Waypoints 1.0.5 - 26.22 months ago 92
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Client and server
Changes
- Added NeoForge support: 1.20.1, 1.20.4, 1.21.1, 1.21.4, 1.21.5, 1.21.8, 1.21.11, 26.2
- Added Fabric 26.2 support
- Added a visual editor (M by default, or /waypoint editor) with live preview, sliders, a color wheel and the equivalent command to copy
- Added the Displays tab (N by default) to edit or delete the waypoints around you
- Added undo and redo (Ctrl+Z / Ctrl+Y) and a History of the last 8 saved, overwritten or deleted waypoints
- Added reset buttons to the sliders, and Shift to move them in steps of 5
- The editor works as an overlay: you can keep walking while it is open
- Added figures: /waypoint figure, mission markers on the ground with 19 shapes or any text/number
- Figures support negative height (fade downward), in/out animations, follow rotation, pitch and roll (for walls) and width_x / width_z
- Waypoints are now saved per world and per dimension (old waypoints are moved to the first world you join)
- Added {on_view_radius:N} and {/on_view}: text that only shows when you look at the waypoint
- {distance} now shows whole blocks, and {distance_decimal} shows one decimal
- Added optional fade_out and opacity to set, timer, counter and follow
- Added follow_horizontal and follow_vertical rotations
- Timer and counter sounds accept any sound id (vanilla or resource packs) with autocomplete
- Follow targets autocomplete online players
- Follow waypoints are only removed with remove: they hide while the target is not loaded and come back when it loads again
- Fixed pixelate and glitch animations
- Fixed item icons and CustomModelData on some versions
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:NFyDgHvU:D55ipOYe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NFyDgHvU:D55ipOYe"
}

