Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 months ago
Updated 4 months ago
All versions
1.0.1
Release
FrontCore Cosmetics&Crates 1.0.14 months ago 47
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Unavailable version
Changes
[1.0.1]
Added
- Added an addon-owned Kill Cards cosmetics tab, including kill-card frame browsing, rarity-colored entries, frame preview, and JSON-driven frame registration.
- Added an addon-owned Name Tags cosmetics tab for permanent gun renaming through FrontCore's nametag service.
- Added kill-card frame display-name and rarity support to the addon JSON content format.
- Added addon release documentation through a dedicated README and changelog.
Changed
- Cosmetics addon screens now use the same FrontCore-style GUI-scale fit behavior and screen lifecycle handling as core FrontCore UIs.
- Addon cosmetics layouts now keep the list and preview lanes side-by-side and centered as a single content block instead of left-biasing the usable screen space.
Fixed
- Fixed kill-card frame preview scaling so full-card frame textures render at the correct aspect ratio in the addon preview.
- Fixed kill-card frame preview/layout behavior across larger GUI scales, including centered placement, footer-safe spacing, and preview panel alignment.
- Fixed Name Tags screen layout across larger GUI scales, including preview spacing, button placement, footer overlap, and preview text positioning.
- Fixed Name Tags preview so the final renamed gun-name preview no longer overlaps the text field and the Available Tags readout stays on the preview header line.
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:bzIjUMG9:zH9h0RBp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bzIjUMG9:zH9h0RBp"
}
