Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published 4 years ago
Updated 5 days ago
All versions
26.1.11+neoforge
Beta
[NeoForge 26.1.X] 26.1.115 days ago 1,965
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
26.1.11
- fix: shears harvest info is not working (close #810)
- feat: add recipe lookup keybind tooltips
- compat: add support for RRV (#786)
- feat: drag to scroll list
- refactor: abstract SmoothScrollableList
- fix: license path
- feat:tool tier removal api
- improve: vanilla harvest addon
- chore: API javadocs
- Add harvest tool registration API (#772)
- fix: text width calculation (close #791)
- fix: #804
- fix: Seagrass harvestability (close #805)
- fix: item serialization incompatibility with polymer (close #792)
- fix: improve compatibility with Create Aeronautics
- fix: Width of TextElementImpl is miscalculated when Caxton is present
- fix: Looking at a Chest With Certain Content on a Server With ViaFabricPlus May Cause Game Freeze
26.1.10
26.1.9
- fix: CME in registerTagsUpdatedListener
- feat: add
/jadec generate_server_overrides - Update build.gradle for 26.1-neoforge
26.1.8
- #777
- fix: Jade Loot Table Tooltip Crash (Invalid Translatable Argument Type)
- fix: Crash in KeybindOptionButton due to invalid narration argument (StringWidget)
26.1.7
- fix: Only the first element of a MutableComponent is shown in appendTooltip
- feat: add REI integration back
- feat: add JEI integration back (close #774)
26.1.5
Optional dependencies
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Jade-mc26.1-NeoForge-26.1.11-sources.jar | Unknown | 509.38 KiB |
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:nvQzSEkH:5jKeKXwB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nvQzSEkH:5jKeKXwB"
}

