Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 3 months ago
All versions
2.0.4-0.8.0.8b
Release
FrontCore 2.0.4-0.8.0.8b4 months ago 197
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
[2.0.4-0.8.0.8b]
Added
- Added a dedicated 3D gun inspect screen for gun skin selection, including right-click open from the per-gun skin list, drag-to-rotate controls, and scroll-wheel zoom.
- Added the same 3D inspect flow to the trade screen so traded skins and patterns can be right-click inspected before offering or accepting them.
- Added ReplayMod-compatible BlockFront ADS playback support so recorded in-match replays can now show other players aiming correctly during playback.
- Added Social match-mode labels for in-match friends, party members, and clan members, so the Social tab now shows short mode keys like inf, dom, and tdm.
- Added configurable Discord player-alert cooldown controls so threshold pings can be rate-limited once the server reaches a chosen online-count.
Changed
- Gun inspect rendering now uses a brighter GUI-style presentation with larger default model scale, stronger zoom response, and a cleaner background-free preview area.
- Trade cosmetic rows now support the same live preview-to-inspect workflow used in the owned gun skin selector.
- Replay ADS compatibility now follows BF's real aim-toggle sync and patches both third-person BF aim-render branches used during replay playback.
Fixed
- Fixed gun cosmetic exclusivity so a player can no longer have both a non-default skin and a non-default pattern selected on the same gun at the same time.
- Selecting a real skin now forces that gun's pattern back to default, and selecting a real pattern now forces that gun's skin back to default, while leaving default-on-default selections non-destructive.
- Fixed ReplayMod match recordings so ADS state is no longer lost or overwritten by stale fallback state during playback.
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:fUo1Xx7Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YauHU1vm:fUo1Xx7Y"
}


