Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated 6 months ago
All versions
0.0.30
Release
Vesper Wilds 1.21.11-0.0.307 months ago 24
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Vesper Wilds 0.0.30
IMPORTANT: NEW DEPENDENCY! Starting with 0.0.24, Vesper Wilds requires GeckoLib 5.4.2 or higher to run properly.
New Features & Content
- New Hostile Mob: The Gloom Stalker! A flying, bat-like predator that spawns exclusively within the Vesper Grove (Note: currently using temporary textures and animations while in active development!).
- New Mechanic: Twilight Resonance! The shadows empower you. While in a light level below 7, your mining speed is increased by 20% and your attack damage is increased by 2.
- New Event: Velvet Eclipse! A dangerous new atmospheric event where Gloom Stalkers can spawn outside of the Vesper Grove, crop growth is completely halted, and the Twilight Resonance effect for Vesperite Tools is significantly enhanced.
- New Items: Added the Velvet Cloak and Velvet Fuzz.
- Spawn Eggs: Added spawn eggs for the Velvet Moth and Gloom Stalker to the creative menu.
Changes & Tweaks
- Velvet Moth Overhaul: Velvet Moths now drop the newly added Velvet Fuzz upon death. The old mechanic where they passively dropped string has been removed.
- Creative Menu: Expanded and reorganized the Vesper Wilds Creative Tabs for better accessibility.
- Localization: Added translation for the Vesper Tool Materials.
Bug Fixes
- Fixed a major file structure issue that was preventing Vesper Wells from generating in the world.
- Fixed broken Block Tags associated with the Velvet Wood family.
- Fixed various recipe inconsistencies within the Velvet Wood family.
- Fixed a blast furnace recipe issue regarding Raw Vesperite.
- Fixed an issue preventing the Velvet Fern from dropping its correct loot.
- Fixed a bug where Vesperite Tools were missing their proper tool tags, causing them to interact incorrectly with certain blocks.
- Fixed inconsistent namespacing within the codebase.
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:yhOl5RSV:s6unfk5P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yhOl5RSV:s6unfk5P"
}

