Blinkstone / Downloads
Downloads
There isn't one Blinkstone jar. There are eleven, one for each Minecraft line from 1.20.1 to 26.3, because the item registration and tooltip code genuinely differs between them. Take the row that matches your game and ignore the rest.
Files are on the CurseForge page, and the installing link takes you there. Pick the file whose + suffix matches your Minecraft version line.
| Minecraft | File | Java | Fabric API |
|---|---|---|---|
| 1.20 – 1.20.1 | blinkstone-1.0.0+1.20.1.jar | 17 | 0.92+ |
| 1.21 – 1.21.1 | blinkstone-1.0.0+1.21.1.jar | 21 | 0.116+ |
| 1.21.2 – 1.21.3 | blinkstone-1.0.0+1.21.3.jar | 21 | 0.114+ |
| 1.21.4 | blinkstone-1.0.0+1.21.4.jar | 21 | 0.119+ |
| 1.21.5 | blinkstone-1.0.0+1.21.5.jar | 21 | 0.128+ |
| 1.21.6 – 1.21.8 | blinkstone-1.0.0+1.21.8.jar | 21 | 0.136+ |
| 1.21.9 – 1.21.10 | blinkstone-1.0.0+1.21.10.jar | 21 | 0.138+ |
| 1.21.11 | blinkstone-1.0.0+1.21.11.jar | 21 | 0.141+ |
| 26.1 – 26.1.2 | blinkstone-1.0.0+26.1.2.jar | 25 | 0.155+ |
| 26.2 | blinkstone-1.0.0+26.2.jar | 25 | 0.161+ |
| 26.3 | blinkstone-1.0.0+26.3.jar | 25 | 0.165+ |
Picking the right one
Open your launcher, look at the version name in the profile, and match it against the left column. If you're on 1.21.7, take the 1.21.8 jar: each file declares a range, so patch releases inside a line are covered by the same build. You don't need one jar per patch number.
Put exactly one Blinkstone jar in mods. Two of them will fight over the same item ids and the game will complain about a duplicate registration, which is an unhelpful error for a self-inflicted problem.
Fabric only, for now
Every jar here is a Fabric mod. There is no Forge or NeoForge build yet, and I'd rather say that plainly than have you download something that won't load. If you need Forge for a pack, the FAQ says where that stands.
Servers
Use the same jar on the server and on every client that joins. There's nothing to configure, and a client without it will see the items as missing entries rather than crash.