Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 5 months ago
All versions
1.0.12-0.7.1.2b
Release
FrontCore 1.0.12-0.7.1.2b7 months ago 13
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
[1.0.12-0.7.1.2b] - 2026-03-15
Added
- Colored owned gun skin names in the skin selector and selected-skin list by rarity so IRON, LAPIS, GOLD, and DIAMOND skins are easier to scan in the menu.
- Added small in-button gun previews to the owned-gun skin list so players can identify guns visually without opening each entry.
- Added a unified paged admin config GUI opened through /fc admin config gui, combining general settings, XP settings, and class-rank settings into one screen.
- Added Embeddium compatibility for BlockFront's baked-entity special blocks, restoring the BF placed P/V-style block families that rely on BF's custom chunk compile path.
- Added native profile admin commands for live BlockFront data:
- /fc profile native setXp <target> <xp>
- /fc profile native reset <target>
Fixed
- Disabled BlockFront's client update check loop so the startup/update popup path no longer interrupts FrontCore's offline-flow redirect.
- /fc admin config reload now immediately reapplies configured class-rank requirements and resyncs them to connected clients instead of leaving classRanks stale until a restart.
- Locked/unavailable class attempts no longer wipe the player's current items; FrontCore now restores the last valid class state when a rank-locked or XP-locked selection is rejected.
- Removed the stale BF notification backup mixin from the client updater suppression path, cleaning up the old remap-warning fallback.
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:F57nBmbr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YauHU1vm:F57nBmbr"
}

