Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
All versions
1902.6.0-build.86+fabric
Alpha
KubeJS Fabric 1902.6.0-build.864 years ago 68
Uploaded by
Compatibility
Minecraft: Java Edition
1.19.2
Platforms
Fabric
Quilt
Supported environments
Client-side
Server-side
Client and server
Required content
Changes
- Merge pull request #489 from ChiefArug/safeEffectCallback - Kristiāns Micītis
- Merge pull request #494 from ChiefArug/statsFix - Kristiāns Micītis
- Merge pull request #495 from ChiefArug/registry-custom-objects - Kristiāns Micītis
- Merge remote-tracking branch 'origin/1.19/dev' into 1.19/dev - LatvianModder
- Updated Ingredient API - LatvianModder
- Better event error handling - LatvianModder
- Fix merge error - Max
- Post-release cleanup - Max
- Merge branch '1.18/dev' into 1.19/dev - Max
- Migrate to current script type / console in some places - Max
- Backport ScriptType.getCurrent and ConsoleJS.getCurrent to 1.18 - LatvianModder
- Add Utils.lazy and Utils.expiringLazy for memoized suppliers - Max
- Update to Rhino 1802.2.1 - Max
- Rename custom that takes a BuilderBase to fromBuilder, to avoid potential future ambiguity - ChiefArug
- Allow adding custom objects to registries. This opens up a lot of possibilities with registering things based on other mods classes, including things that do not have a default ('basic') type, such as BlockEntities or Entities. - ChiefArug
- Revert IntelliJ deciding to put a bunch of wildcard imports in - ChiefArug
- Fix https://github.com/KubeJS-Mods/KubeJS/issues/490 Also has side effect of allowing non-rl based stats to be set. - ChiefArug
- Move destroyServer to server stopped event (fixes persistent data issues) - Max
- Add safe callback for mob effect ticking, so it doesn't crash the game. - ChiefArug
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:umyGl7zF:A8sfF3LI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:umyGl7zF:A8sfF3LI"
}



