Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 5 months ago
All versions
2.0.3-0.8.0.8b
Release
FrontCore 2.0.3-0.8.0.8b7 months ago 66
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
[2.0.3-0.8.0.8b]
Added
- Added kill-card frame cosmetics as a permanent FrontCore cosmetic category, including server persistence, client sync, admin selection support, and live kill-card rendering.
- Added an addon-owned Kill Cards cosmetics tab in FrontCore-Cosmetics, including frame preview, rarity support, display-name support, and JSON-driven kill-card frame registration.
- Added permanent gun name tags, including stored per-gun custom names, available-tag tracking, rename application/clear flows, and addon-owned Name Tags cosmetics UI.
- Added kill-card frame rarity support across the cosmetic registry and addon JSON format so frame entries can use the same rarity model as the rest of the cosmetics system.
Changed
- Refactored the cosmetics GUI so addon tabs are registered and opened through a reusable FrontCore cosmetics-tab extension path instead of hardcoding all categories in core.
- Moved kill-card cosmetics screen logic into the cosmetics addon while keeping persistence, sync, and live render hooks in FrontCore.
- Gun name rendering now uses FrontCore's stored gun-nametag state and formats renamed weapons as Gun Name | nickname, colored by the active skin's rarity when applicable.
- Addon cosmetics screens now use the same GUI-scale reconciliation model as core FrontCore screens, with centered side-by-side layouts and per-screen fit limits.
Fixed
- Fixed clan tag rendering in BlockFront UI paths so clan tags now show correctly in the lobby tab, in-match tab, and kill-card identity surfaces without duplicating prefix text.
- Fixed kill-card frame rendering so full-card overlays draw in the correct BF render space, use the correct source texture dimensions, and no longer replace or misplace the base kill card.
- Fixed kill-card cosmetics selection so the selected marker moves on the first click instead of waiting for a second click or server roundtrip.
- Fixed addon cosmetics layout across large GUI scales, including centered side-by-side alignment, footer-safe preview placement, and spacing/paging polish for the Kill Cards and Name Tags tabs.
- Fixed gun skinPlayer tab completion so it only suggests real skins and no longer mixes in gun pattern names.
- Fixed gun name tags so renamed display names now apply to native BlockFront skins as well as addon skins.
- Fixed the Name Tags preview panel so rename preview text, controls, and status lines no longer overlap each other or the global footer controls at larger GUI scales.
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:YauHU1vm:eE003DTM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YauHU1vm:eE003DTM"
}

