Links
Tags
Creators
Details
All versions
1.16.0
Release
CopyCoords 1.16.0 for MC 1.20.66 months ago 19
Compatibility
Minecraft: Java Edition
1.20.6
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
[1.16.0] - 2026-04-13
Added
/coordsbookmark add <name> <coords>and/coordbookmark add <name> <coords>now support explicit coordinates when creating bookmarks.- Accepts space-separated coordinates like
100 64 200. - Accepts bracket coordinates like
[100, 64, 200]. - Accepts
X:100 Y:64 Z:200style coordinates. - Keeps the old
add <name>behavior and still uses your current position when coordinates are omitted.
- Accepts space-separated coordinates like
Fixed
- Fixed the bookmark Xaero export action failing for bookmarks that stored equivalent dimension IDs in legacy or raw forms instead of Xaero's expected Overworld, Nether, or End IDs.
- Fixed incoming chat coordinate detection registration on Minecraft
26.1.2, which could fail at runtime because chat receive compat reflected against Fabric's concrete event implementation instead of the public event interface. - Fixed malformed
/coordsbookmark add <name> <coords>and/coordbookmark add <name> <coords>input falling back to the player's current position instead of reporting an invalid coordinate or dimension error. - Fixed
/convertcoordssilently substituting the player's current coordinates when given invalid coordinate tokens. - Fixed bookmark import crashing or partially importing data when the JSON array contained null or malformed bookmark entries.
- Fixed Windows clipboard writes using the JVM default charset instead of an explicit Unicode-safe encoding.
- Fixed
/msgcoordsfailing without showing the underlying chat command send reason when the send call returnedfalse.
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:GzPkXb2a:NDHrHpei"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GzPkXb2a:NDHrHpei"
}

