Tags
Creators
Details
1.0.0-alpha6
Compatibility
Required content
Changes
Conium script
Event types
Add events support:
- 'BREAKING_BLOCK'
- 'BROKEN_BLOCK'
- 'ENTITY_DAMAGE'
- 'ENTITY_DAMAGED'
- 'ENTITY_DIE'
- 'ENTITY_DEAD'.
- 'ENTITY_TICK'
- 'ENTITY_TICKED'
- 'ITEM_USED_ON_BLOCK'
- 'SERVER_TICK_TAIL'
- 'FLUID_SCHEDULE_TICK'
- 'FLUID_SCHEDULE_TICKED'
- 'BLOCK_SCHEDULE_TICK'
- 'BLOCK_SCHEDULE_TICKED'
- 'SHULKER_BOX_OPENING'
- 'SHULKER_BOX_OPENED'
- 'SHULKER_BOX_CLOSING'
- 'SHULKER_BOX_CLOSED'
- 'CHEST_OPENING'
- 'CHEST_OPENED'
- 'CHEST_CLOSING'
- 'CHEST_CLOSED'
- 'TRAPPED_CHEST_OPENING'
- 'TRAPPED_CHEST_OPENED'
- 'TRAPPED_CHEST_CLOSING'
- 'TRAPPED_CHEST_CLOSED'
Event context
- The 'identity' of event context that input to 'arising' and 'presaging' have actual type now.
- Add more dynamic args transformer and more arg types
- Add method 'preRequest' in 'ConiumEventContextBuilder', used to make 'presage' trigger.
- Methods 'request' in 'ConiumEventContextBuilder' can input two lambdas now, first is 'arise', seconds is 'presage'.
- Add 'target' and 'targetTo' method in 'ConiumEventContext' used to filter the identity to trigger context.
Data driven interactions
See the samples, the 'glint' key in data define and interaction.kts script.
This sample let an item change glint status in hand, when player is creative mode, use the item on block will make this item be glint, otherwise then be not glint.
Data driven
Supported block templates:
- 'piston_behavior'
- 'walk_velocity'
- 'jump_velocity'
- 'movement_velocity'
- 'replaceable'
- 'instrument'
- 'path_find_through'
Networking
Add networking supports, the server can synchronize registry to client now, but only items, blocks and entities can be synchronized.
Others
Performance optimizations.
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:3H3go31k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:i7S4uT5P:3H3go31k"
}


