Tags
Creators
Details
V1.7
Compatibility
Changes
Atomics Client v1.7
This update begins the migration of Legions-specific features out of Atomics Client and into the new separate Legions Client project.
Atomics Client and Legions Client are compatible, so players who want the general Atomics Client features can keep using Atomics Client, while players who want Legions-specific tools should install Legions Client alongside it.
π Changed
- Updated mod version from
1.6to1.7 - Minecraft target remains
1.21.11 - Began separating Legions-specific features from Atomics Client
- Cleaned up the PvP settings menu by removing the old Legions-specific settings section
- Kept Atomics Client focused on general PvP visuals, overlays, inventory tools, villager utilities, and quality-of-life features
π§© Legions Client Compatibility
- Legions-focused features are being moved into the new Legions Client Modrinth project
- Atomics Client remains compatible with Legions Client
- Players can use both mods together if they want both general Atomics features and Legions-specific tools
ποΈ Removed / Migrated
The following Legions-specific features have been removed from Atomics Client and are intended to be handled by Legions Client instead:
- Legions feature toggle section
- Legions rating nametags
- Automatic Legions foe overlay
- Legions spectator team glow
- Legions team score totals
- Legions End Rod warning particle replacement
- Legions server detection logic
- Legions rating parsing and color handling
π§ Internal Cleanup
- Removed old Legions warning particle rendering code
- Removed outdated Legions particle mixins
- Removed Legions rating helper classes
- Cleaned up unused Legions config fields
- Reduced overlap between Atomics Client and the new Legions Client project
β οΈ Notes
This is not a major feature update for Atomics Client itself. Instead, v1.7 is mainly a cleanup and migration update that prepares Atomics Client to work alongside the new Legions Client project.
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:ugZ2p7tG:Y7SBby7C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ugZ2p7tG:Y7SBby7C"
}

