Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 3 months ago
All versions
1.1.2-0.7.1.2b
Release
FrontCore 1.1.2-0.7.1.2b4 months ago 31
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
[1.1.2-0.7.1.2b]
Added
- Added a Reset to BF button in the gun modifier editor so a gun can be restored to BlockFront's original default modifier values without reloading FrontCore's saved override files.
- Added the next Discord bot voice-routing upgrade for verified players, including a global Matchmaking VC, per-match Axis/Allies routing sets, per-set FFA voice channels, and a shared Infected VC.
- Added clan moderators: clan leaders can promote one member to Mod, moderators can invite and kick normal members, and promoting the current moderator again transfers clan leadership while demoting the old leader to moderator.
Changed
- Voice routing is now hybrid instead of brute-force fast polling: FrontCore tracks match/team changes, reacts to managed Discord voice updates, keeps match-slot ownership stable across simultaneous matches, and uses a slower reconciliation pass as repair logic.
- Clan Social UI now shows moderator state directly in the member list and keeps clan ordering aligned with the new role model.
Fixed
- Fixed verified Discord voice routing so players are moved correctly when they switch teams, join matchmaking mid-match, leave a match early, or when only one of multiple active matches ends and returns to map voting.
- Fixed infected Discord voice routing so infected matches also resolve correctly through the same normalized mode keys used elsewhere in FrontCore.
- Added a client-side BF decoration render guard so broken bf:decoration_block null-model cases no longer hard-crash the client under Embeddium/GeckoLib when BlockFront tries to render missing decoration_null_* models.
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:RAqsMyRm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YauHU1vm:RAqsMyRm"
}


