All versions
1.3.1
Release
Wisp & Willow 1.3.18 months ago 47
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Wisp & Willow — Update Log
Added
-
Snad Block
- Supports configurable growth speed, max scan height, activation chance, and an allowlist (including tag support like
#forge:...) via server config. - Optional “force max age” behavior for age-based crops.
- Supports configurable growth speed, max scan height, activation chance, and an allowlist (including tag support like
-
Terminal System
- Terminal: browse/search items stored in the network with paging + sorting.
- Crafting Terminal: terminal + integrated 3×3 crafting grid + output slot.
- Ghost display stacks now show "real total" counts (internal display-count tagging) while keeping stack rendering consistent.
-
Network Storage Integration
- Network item view / handler utilities to represent storage contents for UI and internal logic.
- Improved snapshot refresh + count syncing behavior for terminal displays.
-
Fluid System (Early Feature Set)
- Initial groundwork for fluid storage + transfer support.
- Early integration points for fluid drive/storage concepts and terminal interaction.
Changed
-
Terminal UI behavior and syncing improvements:
- More reliable snapshot refresh cadence and count synchronization.
- Sorting support expanded/cleaned up (type/name/amount/tag + ascending toggle).
-
Crafting terminal mechanics:
- Improved crafting result updates + slot syncing to reduce desync.
- Refinements to refill behavior after crafting (remainder handling + immediate output refresh).
Fixed
- Reduced/removed behaviors that could cause incorrect "recipe fill" interactions from external recipe-transfer systems.
- Multiple stability fixes around ghost-slot interaction, snapshot refresh, and count display accuracy.
Notes
- Some features (especially fluid storage/terminal interactions) are still actively iterating.
- Server owners can tune Snad behavior via
wispwillow-server.tomlto match desired progression and farm speeds.
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:8HYWsQBZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a6zCFWRP:8HYWsQBZ"
}


