Tags
Creators
Details
3.0.3
Compatibility
Required content
Changes
Atlas Client 3.0.3
Community cosmetics
- You can now remove skins and capes you uploaded from the Community catalog. Open Cosmetics, choose Skins or Capes, then select Remove on your upload.
- Authorized administrators can remove other players' community capes from the client while their management session is unlocked.
- Removing a community listing leaves existing personal copies and equipped cosmetics intact.
- Uploading an identical file from another account no longer changes the original upload's owner or name.
- Remove controls follow your current Atlas account's permissions. Signing out clears them, and repeated clicks cannot send duplicate removal requests.
Smoother catalog browsing
- Large community cape lists now render only the rows visible on screen, reducing unnecessary work when browsing.
- After a removal, an older catalog response can no longer bring the deleted listing back into the menu.
Clearer announcements
- Community announcements have their own presentation instead of appearing as software updates.
- Update notices include separate Modrinth and CurseForge links.
- Long announcements open in a scrollable reader. Text wrapping, button alignment and background readability have been improved.
- Announcement controls use short hover and opening transitions, with no continuous work when there is no active notice.
Existing settings are preserved. Download the file matching your Minecraft version, and remove your previous Atlas JAR before installing it.
This download: Minecraft 26.1.2, Fabric Loader >=0.19.3, Fabric API. Player Animation Library is required. Rinku is optional.
Optional dependencies
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:6s5eaMHC:H4pQg0i1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6s5eaMHC:H4pQg0i1"
}

