5.7+26.2
Compatibility
Changes
Chest Radar 5.7
So this one covers everything since 3.13, the versions in between were in testing and I never uploaded them. Its a big one honestly, mostly a full redesign.
Everything below is for 26.2 and 26.3. The 1.21.10 version is still there but it doesnt get new stuff anymore.
New look
- The radar screen got redesigned : sort tabs (Name / Quantity / Distance), a search bar that takes the full width and shows you the syntax, and a smaller grid so you see way more items per row.
- Your pinned items now have their own row above the grid. Click on "Pins" to only show those (it replace the ☆ button).
- The details panel on the right is gone, it was only there for the "Take me there" button. Left click a tile does the same thing now.
- The craft planner got the same treatment : a summary card with the status, every ingredient tells you if you have it on you, in chests or if its missing, and a "Collection route" card to plan the trip.
In game
- The preview of the chest you look at is now a small card next to the crosshair.
- The chest highlight uses your accent color.
- When you come back to a chest, the chat tells you what changed since your last visit (removed in coral, added in green).
- The current route step shows in a card above the hotbar.
Settings
- New settings screen, the same one as the other Aeternum mods, with an Appearance page : 4 themes and your own saved ones.
- "Window opacity" actually works again, and cards and tiles follow it too now.
- The Flat style is applied everywhere, some surfaces were still ignoring it.
- "Done" and "Cancel" follow the mod language instead of the game one.
Fixes
- The radar fits in small windows and at every GUI scale.
- Text thats too long ends with "…" and shows in full when you hover it.
- Text fields in the settings dont overlap their description anymore.
- The game font is used everywhere now.
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:4tAcnuIV:OOeTVplh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4tAcnuIV:OOeTVplh"
}

