Tags
Creators
Details
Licensed MIT
Published 5 years ago
Updated 3 years ago
All versions
5.0.0+1.19
Release
[1.19.2] Jello - 5.0.03 years ago 143
Uploaded by
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Unavailable version
Any compatible version
Changes
Jello 5.0.0 is a Major release including the separation of the Mods underline API into its own mod to allow for better mod inclusion and implmentation.
Features:
- Rework to DyeBundle with the inclusion of new way of interacting with the contents of the bundle
- Rework to how the new DyeColors are loaded by jello allowing for easier revisions to the list of colors.
- Color Deduplication: This was done due to how many colors (Roughly 500) were only off by 1-5 units away from each other in color space. I have a system inplace to properly remap these colors to the chose alternative meaning there should be no problems upgrading the world. This means that the amount of colors is around 1300 now instead of 1800.
- [NEW] Jello Cups: These exist for a while within the creative screen but were not really finished. They act like stackable potions for Vanilla Status Effects meaning that you can stack them up to 16 but the downside is that you will need eat more often than a potion. Some even slightly better duration depending on the crafting item used. Info about making them can be found using REI.
- [NEW] Dragon Health: Similar to Absorption but are permanent for the Potions duration. You need Condensed Dragons Breath to brew such a potion require both Ghast tear and 4 Dragons breath
Fixes:
- Fix bug with sorting entries within condensed creative
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:Hp38UGFB:mHGmdYEx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hp38UGFB:mHGmdYEx"
}

