Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 9 months ago
All versions
0.2.11
Beta
0.2.11-fabric3 years ago 281
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Features
- Added Motes and Mote Nexi! This is a Hex Casting based item storage system which functions similarly to AE2 or Refined Storage, where you can take items from the world and mediafy them into motes on your stack. Each mote is effectively a reference to a record in your bound Mote Nexus, and you can use these motes for sorting, autocrafting, autotrading, and whatever else you need!
- Added an action to get the level of a villager for all your autotrading needs.
- Place Block II can now accept a mote and place a block from that mote.
- Made Running Sum work on lists of vectors.
- Added actions to get whether an entity is marked with a gate, and get how many entities are marked with a gate.
- Added Entity Distillation: Type and Zone Exhaltation: Type/Not-Type to get entity/s at a position/within range of a position that are/are not a specific type.
- Changed the max range of links to be 2 * (linkableA.maxRange + linkableB.maxRange)
- Made OpTypeEntity now return the plain entity type for items; OpTypeBlockItem can now accept item entities and return their item type.
- Added action to get the item type of the item held in the player's non-casting hand (or the type in their casting hand if the offhand is empty).
Bugfixes
- Added protection to Everbook against bringing illegal data interworld (gates and motes currently).
- Fixed Place Block II requiring the item to be in your hotbar.
- Fixed wisps not having any upkeep cost.
- Fixed wisps not removing their rendered links when they were removed.
- Mcuked around with BlockEntitySlipway to hopefully fix slipways making particles in random places.
- Fixed null reference issues with Bound wisps on forge.
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:aBVJ6Q36:LlBv7qji"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aBVJ6Q36:LlBv7qji"
}






