Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 5 months ago
All versions
1.0.11-0.7.1.2b
Release
FrontCore 1.0.11-0.7.1.2b7 months ago 15
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
[1.0.11-0.7.1.2b] - 2026-03-14
Added
- Added a pause-menu Leave Match shortcut that removes the player from their current BlockFront match if needed and teleports them to a configurable x/y/z/yaw/pitch destination from mercfrontcore.json.
- Added /fc admin leaveMatch setHere to save the current player position and rotation as the leave-match destination in config.
- Added overwrite confirmation for /fc admin leaveMatch setHere so an existing saved leave destination is not replaced accidentally by another admin.
- Added a safer in-game config UX through /fc admin config ..., covering common proxy, rewards, XP, class-rank, and leave-match config writes without requiring direct JSON edits.
Fixed
- Dropped stale BlockFront entity interaction packets before they reach vanilla handling, preventing players from being kicked for attacking an invalid entity after rapid kill/death desync cases.
- Reformatted winner skin reward chat announcements to show the rarity first and match the compact [Victory Reward] ... received COAL skin 'black' for ... style.
Notes
- Current /fc admin config ... edits do not all behave the same at runtime:
- Proxy settings, leave-match destination, and reward settings can be used immediately after saving without a restart.
- XP reward values are picked up by future reward events without a restart.
- classRanks currently still need runtime reapplication/client resync work and should be treated as restart-or-reload sensitive for now.
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:hJdxhO57"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YauHU1vm:hJdxhO57"
}

