2.1.0
Compatibility
Required content
Changes
BetterCosmic 2.1.0 Changelog
Cosmic Sky support
BetterCosmic now works on Cosmic Sky as well as Cosmic Prisons. It detects which network you're connected to and only shows each server's features there — so nothing new appears while you're on Prisons. Everything below is optional and toggleable from the same in-game config menu (default I).
New on Cosmic Sky
- Tracker HUD — counts what you earn this session by tier (Basic → Mythic), with a running session timer and on-HUD Pause/Reset buttons. A mode toggle switches the view between Quest tracking (Island Quest completions) and Adventure tracking (adventure chests dropped nearby).
- Player List HUD — a compact, alphabetical list of everyone online, laid out in columns with an optional "Players: N" header.
- Damage indicators — floating combat numbers over nearby entities: red for damage taken, green for heals, with configurable range and colors.
- EasyView overlays — read key values straight off the item, in containers and your hotbar:
- Potion trinkets — remaining uses, colored to match the potion.
- Pets — a centered cooldown / active-effect timer.
- Quest-point notes, money notes, and XP bottles — their value shown compactly in the corner.
- Quest-point expiry tooltip — hover a quest-point note to see the time remaining plus the exact expiry in your local timezone.
- Chest search — the same search bar and filter-rule sidebar from Prisons, now in Sky containers.
- Auto-trade — shift-right-click a player to send
/trade <name>.
Improvements
- The config keybind now appears under its own "BetterCosmic" category in the vanilla Controls screen, instead of being buried in Misc.
- The HUD editor now only lists the HUDs for the server you're currently on.
Download in #mod-download in the BetterCosmic Discord: https://discord.gg/vJaH4Yr5Dq
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:VTKts9H2:rf6KSk7h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VTKts9H2:rf6KSk7h"
}

