Links
Tags
Creators
Details
All versions
1.4.0+1.21.8
Release
Roleplayer's Atlas 1.4.0+1.21.83 days ago 20
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.8
Platforms
Fabric
Quilt
Supported environments
Client-side
Changes
Travelling by map, marks brought over from Xaero's, and a dialog that fits the screen it is on.
- New: travel by map, where the game allows it. Ctrl-click a mark, a bookmark or any spot on the map and the atlas sends you there, reading the height off the survey so a hillside lands on the hillside. It is offered only where the server actually lets you run the command — the atlas asks the command list the server sent your client, so nothing is promised that the server would refuse. Servers that hand travel out through a plugin, or under another name, are covered by two settings under Marks: whether it is offered at all, and what command to send.
- New: bring your waypoints over from Xaero's. Under Import/Export maps, the import side now reads Xaero's minimap waypoints as well as our own scrolls: pick the world, tick the sets to take, and they come in as marks with their names, heights and colours. Xaero's sets become layers of the same name, unless you would rather have everything in your personal layer. The land itself is not carried over — Xaero records neither the survey nor the structures the atlas draws from, so the map still fills in as you walk it.
- Fixed: the mark dialog no longer covers its own buttons. At a large GUI scale the dialog was taller than the screen, and "Готово" and "Отмена" ended up hidden behind the note box. The dialog is now laid out for the height it actually has: it tightens up when it must, and if even that is not enough the middle scrolls while the title and the confirm row stay put.
Settings and saved atlases carry over untouched.
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:P0zBDYta:a6DOg1cz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:P0zBDYta:a6DOg1cz"
}

