All versions
1.16.0
Release
Blockgame Plus 1.16.04 months ago 12
Compatibility
Minecraft: Java Edition
1.21.4
Platform
Fabric
Supported environments
Client-side
Changes
Blockgame+ 1.16.0
A big one — a complete in-game guide & onboarding system, a notifications feed, a privacy switch, and a move to encrypted servers.
✨ New
- In-game Guide — a full, browsable guide documenting every feature. Open with the Open Guide keybind or
/bgplus guide. Nested topic tree, images & gifs, and pages that can be updated without a mod update. - First-time Setup Wizard —
/bgplus guide setupwalks you through enabling features with live previews, then drops you into the HUD Layout Editor. New players get a one-time prompt to run it. - Contextual help — in the HUD Layout Editor, hover a widget and hold [H] to jump straight to its guide page.
- What's New feed — in-game changelogs & announcements (
/bgplus news), with a version checker that flags when you're out of date. - Offline Mode — one switch (Settings ▸ General) that makes the mod completely silent: no network connections at all. A new Privacy & Connections page explains exactly what does and doesn't connect — and that nothing about you is uploaded without opting in.
🔧 Improvements
- Map, guide, and party services moved to a new HTTPS backbone — all connections are now encrypted.
- Friendlier default HUD layout: the Action Bar widget now sits centered over your hotbar, and the XP Tracker moved to the top-middle, clear of the minimap. (Custom positions you've set are kept.)
- Guide images/gifs stream from the server, so the download stays small.
🐛 Fixes
- Blockgame+ screens (guide, map, HUD editor, stats…) are no longer blurred — by either vanilla's menu-background blur or the Blur+ mod.
- Fixed guide text getting clipped at the bottom of long pages when scrolling.
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:GQGaE1pd:zCeC4dpZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GQGaE1pd:zCeC4dpZ"
}

