Links
Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 2 years ago
Updated 3 months ago
All versions
1.0.0+1.21
Release
1.0.0+1.218 months ago 2,336
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Fabric
NeoForge
Quilt
Supported environments
Client-side
Server-side
Client and server
Required content
Unavailable version
Any compatible version
Changes
Surveyor 1.0!
Changes:
- New landmark format
- Landmarks are now uniquely identified by Dimension, Owner UUID, and Landmark ID
- Landmarks no longer have types, but instead contain an arbitrary map of data components
- Landmark component types can be registered by addons, and will persist even if unrecognized
- 0.x landmarks will be migrated to the new format when joining a world
- Landmarks can be created with item stacks (for icons), lore (for tooltips), and sets of chunks (for claims)
- Waypoints from Xaero's Minimap are now migrated when joining a world, if present
- New command interface under
/surveyor,/landmarks, and/waypoints- Commands work across dimensions, respect OP/console permissions, and allow editing group member waypoints.
/waypointscwill be similarly updated in 1.1, to go with client multi-dim support
- Terrain data is now loaded lazily as needed, unloaded on server save, and uses a queue to handle large client updates.
- Mod memory usage will no longer heavily scale with world size, allowing use on large servers.
- Keep track of deleted landmarks to more accurately update (offline) client waypoint state without deleting unknown data.
- Improve player position sharing behaviour, especially on SERVER mode (now default) and showing offline positions.
- Fix a lot of broken behaviour relating to terrain/waypoint restoration and sharing.
Please delete config/surveyor.toml to get the new default settings.
Changelog: https://github.com/sisby-folk/surveyor/releases/tag/v1.0.0+1.20
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:4KjqhPc9:gUODXJZS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4KjqhPc9:gUODXJZS"
}

