Tags
Creators
Details
1.0.0-alpha5
Compatibility
Required content
Changes
Notice
This version has been founds some severe bugs in script running, use newer version!
Data driven
Entity
Add model support, see the sample.
For bedrock schema is currently only parsable, not completed in loading.
Script
Add events:
- 'PLACE_BLOCK'
- 'PLACED_BLOCK'
- 'USE_BLOCK'
- 'USED_BLOCK'
Dynamic args can get any value from transforming others values now.
For example, even if the event context input has only present 'ItemPlacementContext', if you want get 'ServerWorld':
request(
PLACE_BLOCK,
SERVER_WORLD
).arising { _, world ->
// Actions here.
true
}
you can also get other any value where the transform is supported, even the value are not directly push to context.
Other
- Optimized performances.
Planning
More entity components and Molang, script APIs, first is conium schame entity components and script APIs.
Optional dependencies
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:i7S4uT5P:HLpWh4qB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:i7S4uT5P:HLpWh4qB"
}

