Tags
Creators
Details
0.1.2
Compatibility
Required content
Changes
v0.1.2
Club and Minecraft stopped fighting over your keys.
Minecraft hands a key press to exactly one binding. So a Club key that landed on a key the game already used did not share it — one of the two actions silently stopped working, and which one lost depended on your mod list. Bind Freelook to Left Shift and you quietly lost the ability to sneak, with nothing anywhere saying why.
- Club now reads the game's own bindings and names the conflict in the module's popover, the way vanilla's Controls screen paints duplicates red.
- Rebinding Zoom or Freelook in the Club menu changes it in Options → Controls → Club, and the other way round. It is one binding, not two settings that drift apart.
- The menu can no longer be locked away from you. Vanilla's Controls screen lists all three Club binds side by side, and it was possible to take the menu's own key — leaving the bind fixable only from the menu that would no longer open.
- A module key that a hold module (Zoom, Freelook) has taken over now says so, instead of sitting there looking like it still works.
Toggle Sprint could latch the sprint key down forever. If you switched vanilla's "Sprint: Toggle" on while the module was running, its release did nothing and you sprinted for the rest of the session. Fixed.
The HUD is the size you set it.
It used to be laid out in Minecraft's GUI-scale units, so a video setting quietly resized every element — on top of that element's own Size slider, which meant "1.0" was a different physical size on every machine. The HUD now has its own canvas, like the menu:
| GUI Scale | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Chip width, real pixels | 90 | 90 | 90 | 90 |
| Before this release | 45 | 90 | 135 | 180 |
The HUD editor moved with it, so what you drag is the size you get. Saved positions are converted, not reinterpreted — nothing jumps across the screen.
The menu stopped lying.
- Screen Stretch on Auto, and Toggle Sprint while vanilla's own sprint toggle is on, are deliberate no-ops. They used to sit there lit like a working module. They now say why they are idle.
- Turning off Club's Effects HUD left you with no effect display at all — not ours, and not the game's. A replacement only hides the original while it is on screen.
- Screen Stretch's letterbox is drawn again on F1 and behind the pause menu. It masks a world we deliberately over-render; hiding the HUD must not un-mask it.
- A movement key held while walking into the HUD editor and back no longer goes dead.
Licence. Club is MIT now. Source to GitHub shortly.
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:MqdRRPHj:sYJPD90v"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MqdRRPHj:sYJPD90v"
}

