Included content
| Name | |
|---|---|
Minecraft 1.21.11. Same atlas as the 1.21.8 release, nothing added or taken away – this is the port.
Drop roleplayers-atlas-1.0.0+1.21.11.jar into mods/. Requires Fabric Loader 0.19.3 and Fabric API on Minecraft 1.21.11. Cloth Config and Mod Menu are optional and give the nicer settings screen.
Client-side only, as before. The server needs no mod.
Surveyor Map Framework has no 1.21.11 build: its 1.21 line ends at 1.2.1+1.22 for 1.21.8, after which it moved to 26.1. Rather than wait, this jar carries a modified copy of Surveyor, ported to 1.21.11 by hand and versioned 1.2.1+1.21.11-ra.1 so it cannot be mistaken for an official build.
It stays under LGPL-3.0-or-later, and the source is at codeberg.org/Glam_Ardor/surveyor-1.21.11. Anything wrong with that build is this mod's fault, not Sisby folk's – report it here.
The port takes upstream's own 26.1 work as the starting point, since it already carries the 1.21.9-era API changes, and reverts what belongs to 26.1 alone. No behaviour was intentionally altered.
Almost all of it is the 1.21.9 rework of screen input: the raw callbacks became Click, KeyInput and CharInput objects, and the static shift/control/alt helpers were removed outright. The rest is renames – sounds, borders, render layers, keybinding categories, texture samplers.
The one real change is the book held in your hands. 1.21.9 stopped handing the first-person renderer a vertex consumer and defers everything through a command queue instead, so the book is now drawn into a buffer of its own and flushed at the right point in the frame.
Route extension, territory reshape and deleting a layer together with its markers still sit outside undo. Fourteen of sixteen languages remain untranslated; Russian and English are complete.
| Name | |
|---|---|
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.
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:1B6NpZ4C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:P0zBDYta:1B6NpZ4C"
}