All versions
1.2.0
Release
Wisp & Willow 1.2.09 months ago 28
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
🌿 Wisp & Willow – Fluxia & Ritual Update
✨ New Content
🌺 Luxinia’s Flower
- New early–game Fluxia–generating flower.
- Consumes Amethyst Coal items dropped near it.
- While burning, it:
- Generates 10 Fluxia per second, up to 800 Fluxia internal capacity.
- Emits gentle End Rod shimmer particles to show it’s active.
- Acts as a Fluxia machine node, so it can feed directly into:
- Willow Fluxia Pools
- Fluxia Spitters
- Other Fluxia–aware blocks
đź”® Ritual System
- Added a dedicated ritual recipe serializer and datagen builder.
- Ritual recipes now sync correctly to the client:
- Uses a custom
StreamCodecfor grid layout, sigils, inputs, results, and Fluxia cost. - Fixed network encoding order that could previously crash with
update_recipesdecode errors.
- Uses a custom
- Supports:
- Custom sigil patterns in different grid sizes.
- Item or mob results (with configurable count).
- Optional Fluxia requirement per ritual.
🌀 Fluxia Network & Linking
🎯 Directional Flux Linking Wand
- Linking is now directional:
- First click = source node
- Second click = target node
- Behavior:
- Pools as source → distribute Fluxia to the target.
- Spitters as source → fire Fluxia only toward the target.
- Shift + Right–Click on a Fluxia node:
- Clears that block’s outgoing wand links.
- Also clears the wand’s stored source.
đź’§ Fluxia Spitter Rework
- Spitters are now treated as MACHINE nodes in the network:
- Pools prioritize filling Spitters before other pools.
- Links are one-way from Spitter → target:
- No more Spitter/pool “feedback loops”.
- Spitter tick:
- Pulls from its internal storage (respecting caps).
- Transfers Fluxia to its linked node using shared transfer rules.
- Renders a smooth End Rod beam all the way from Spitter to target.
- Spitter auto–rotates to face its current target when linked.
🌊 Pool & Spitter Connectivity Rules
- Pools and Spitters no longer auto–connect by adjacency:
- They only participate in networks via wand links.
- This makes Fluxia routing explicit and predictable:
- If there’s no wand link, there’s no Fluxia flow.
đź› Fixes & Polish
- Fixed ritual recipes causing
DecoderExceptiononupdate_recipesby:- Aligning encode/decode order for mob result count and Fluxia requirement.
- Ensured all Fluxia storages clamp correctly to their configured capacity.
- Added extra block updates and syncing for Fluxia nodes so HUDs and client visuals refresh reliably.
- General network & linking cleanup to avoid ghost links and weird flow behavior.
If you run into odd Fluxia behavior after updating, try:
- Breaking and replacing old Fluxia nodes (Pools, Spitters, Flowers).
- Re-linking them with the Flux Linking Wand using the new directional rules.
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:a6zCFWRP:HLy52FxI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a6zCFWRP:HLy52FxI"
}


