Tags
Creators
Details
0.1.4+mc1.21.11
Compatibility
Required content
Changes
Club runs on 1.21.8 and 1.21.11 now, as well as 1.21.1. Three jars, one for each — pick the one that matches your game. Same modules, same keybinds, same HUD, same menu, same config.
The Minecraft version is in the file name and in the mod's own version string (club-0.1.4+mc1.21.8.jar), and
each jar refuses to load on anything else rather than half-working: a client that starts and then behaves
strangely is worse than one that tells you it is the wrong download.
Item Scroll turns itself off on servers that forbid it. Astrum and Aormio ban item scrolling by rule, and Club respects the rule instead of leaving it to you to remember.
- Join one of those servers and the feature is simply not there — no card in the menu, no hotkey, nothing to toggle. Leave, and it comes back on its own.
- It is one jar. There is no "clean version" to install and no switch to flip, because a switch a player can flip is a bypass we shipped ourselves.
- The list of addresses is compiled into the mod, not stored in your config, for the same reason. Both of that server's doors are covered, including the ones we found rather than were given.
Particles — choose what you see. A new category holding every particle the game has, sorted into groups you can reason about: Combat, Blocks, Ambient, Fire & Light, Water, Explosions and Status.
- Pick a group on the left, flip particles one by one on the right — or use the group's own switch to turn all of it off at once. The search finds a particle across every group at the same time.
- Everything is on by default. Club does not quietly take particles out of your game; the point is that the switches exist. Nothing is protected, either — the potion swirls sitting in your face in a fight are yours to turn off, like the rest of them.
- A hidden particle is never created at all: not ticked, not drawn. This is a visual choice, not a performance feature — it is about what you want to look at. Turning types off does less work, but there is no number here, because the honest one depends entirely on what is on your screen at the time.
The Performance tab is gone, and the work it did simply happens. The two culls it held — particles behind the camera, block entities off-screen inside a visible section — never changed a pixel, so they were never dials worth tuning: they are baked in and always on. Background FPS was the one setting there that is a real choice (it caps the frame rate only while the game sits behind another window — your battery and your fans, zero in-game FPS), so it kept its cap and moved to Misc.
If you ever need to rule Club out of a suspected rendering bug, those culls still have an off switch — it lives
in config/club_settings.json (perf.cullParticles, perf.cullBlockEntities), instead of a menu toggle
pretending to be a quality setting.
Two things Minecraft now does itself, so Club stopped doing them. Where the game does the work, we get out of the way rather than doing it twice:
- Background FPS is not in the 1.21.8 and 1.21.11 builds. Minecraft caps its own frame rate behind another window from 1.21.2 on. Your setting is Minecraft's now, not ours.
- From 1.21.11 the game culls particles behind you, and by a better test than ours — we only ever skipped what sat behind the camera, and it drops everything outside your view. So Club's particle cull is not in that build. Nothing changes for you; the work still doesn't happen.
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:M37Qo0rU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MqdRRPHj:M37Qo0rU"
}

