0.1.0+1.21.11
Compatibility
Changes
SkyBook - Summary
SkyBook is a Fabric client-side Minecraft mod for 1.21.11 (Java 21) that brings the Hypixel SkyBlock wiki into the game without ever leaving a container screen.
What it does Middle-click any SkyBlock item (in a chest, your inventory, a REI/JEI entry list, anywhere) and an in-game overlay panel slides in over the current screen, showing that item's page from the Hypixel SkyBlock Fandom wiki. The underlying container stays open and fully interactive behind it.
Feature highlights
- Smart item resolution: reads ExtraAttributes NBT to extract the SkyBlock ID, then looks up the canonical wiki title via the NEU item repo (handles pets, enchanted books, potions, runes, reforges)
- Rich wiki rendering: infoboxes, tables, headings, images, and tab groups (e.g. Wither armor variants), parsed from live Fandom API responses and rendered in MC's GUI
- Link navigation + history: clickable wiki links, mouse-4/5 back/forward, /skybook <query> command
- Caching: disk cache with 24h TTL + lightweight revid revalidation; never hammers the wiki
- REI + JEI integration: intercepts hovered entries in both recipe viewers
- Hypixel-safe: middle-clicks are only consumed, never synthesized; glass-pane clicks pass through untouched; complies with Hypixel's client mod rules
Tech stack Fabric Loader 0.18.5 | Fabric API 0.140.0 | jsoup (bundled) | NEU item repo (ZIP-mounted, no extraction) | Fandom action=parse API | Mojang mappings
Current status v0.1.0 is built and packaged (skybook-0.1.0+1.21.11.jar, 602 KB). All 12 unit tests pass. Smoke-tested in the dev client (boots clean, REI/JEI registered, repo ETag caching works). Awaiting first in-game interactive test.
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:PSp2DiqG:IQmO6LtC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PSp2DiqG:IQmO6LtC"
}

