Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 3 months ago
All versions
2.0.0-0.8.0.8b
Release
FrontCore 2.0.0-0.8.0.8b4 months ago 29
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
[2.0.0-0.8.0.8b]
Added
- Added BlockFront 0.8.0.8b compatibility as the new FrontCore target version.
- Added support for custom FFA VC 1, FFA VC 2, and shared Infected VC routing in the Discord bot voice system.
- Added a fixed FrontCore GUI-scale path so FrontCore screens can render at a stable scale independent of the player's normal Minecraft GUI scale.
Changed
- Updated FrontCore to run against BlockFront 0.8.0.8b, including the related runtime screen and client hook compatibility work.
- FrontCore GUI screens now force a stable GUI scale while open and restore the player's original GUI scale when leaving FrontCore UI.
- Clan leaderboard output now uses monthly clan XP totals instead of all-time clan XP, matching the monthly reset behavior used elsewhere.
- Discord bot clan leaderboard formatting now uses distinct fallback placement icons for 4th and 5th place so clan rows do not duplicate #4 / #5 text in embeds.
Fixed
- Fixed the offline startup flow on BlockFront 0.8.0.8b so choosing offline now lands on the vanilla menu path instead of being forced back into BlockFront's offline menu screens.
- Fixed FrontCore GUI-scale switching so the first render frame no longer crashes with a null draw context after the temporary scale swap.
- Fixed GUI-scale restoration so the player's original scale is restored reliably when leaving FrontCore screens, even across unusual screen transitions.
- Fixed trading so default skins and default patterns can no longer appear in trade offers or be added through packets.
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:wDssTxWf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YauHU1vm:wDssTxWf"
}


